https://github.com/osquery/osquery logo
Join Slack
Powered by
What migration steps need to take place from Kolid...
# fleet
t
What migration steps need to take place from Kolide Fleet v3.13 to Fleetdm v4.17.0?
Copy code
$ mysqldump --all-databases > all_databases_$(date +%Y%m).sql
$ systemctl stop fleet.service
$ unzip -C fleet.zip -d fleet-4.17.0
$ cp fleet-4.17.0/linux/fleet* /usr/local/bin/
$ systemctl start fleet.service
$ fleet prepare db --mysql_adddress="localhost:3306" --mysql_database="kolide" --mysql_username=:kolide" --mysql_password=$FLEET_PASS
Migrations completed
^This worked from v3.11 to v3.13. Running 
fleetctl version
or 
fleet --version
shows v3.13 now, but not v4.17.0.
👀 1
k
What do you get if you check the file path for Fleet 
which -a fleet
?
t
/usr/local/bin/fleet
k
Where did 
fleet.zip
come from?
It's not the name of any of the downloads currently in`releases`, so I want to make sure you've got the right file there.
t
Apologies, I was copying the "base" instructions from a Notepad document and forgot to change that 
fleet.zip
in my original post. It should say 
fleet_v4.0.0_linux.tar.gz
not 
fleet.zip
k
I've done that myself one too many times!
Two questions now: 1. Did you also update 
fleetctl
? (either using 
npm
or by downloading from 
releases
? 2. When you're checking the Fleet version, are you doing that in terminal or through 
/version
t
Good questions, I did not. I actually just saw there were both 
fleet
and 
fleetctl
packages under Releases. I'm going to try again next week!
k
Sounds good! If you run into trouble, let me know.
3 Views
Open in Slack
PreviousNext
Powered by