seph
Brandon
09/04/2019, 3:25 PMlauncher --version
launcher - version 0.10.3
branch: master
revision: c0115f999046a62ca43889c743d18826c5c4c53c
build date: 2019-07-24
build user: seph (seph)
go version: go1.12.5
seph
Brandon
09/04/2019, 3:30 PMlauncher
binary on another server without autoupdate
in the flag and confirmed it was the same version, 0.10.3
seph
Brandon
09/04/2019, 3:35 PMlauncher --version
?
FWIW, starting launcher with:
exec /usr/bin/launcher --hostname=hostname-redacted:443 --enroll_secret_path=/var/kolide-fleet/enroll --root_directory=/var/kolide-fleet --osqueryd_path=/usr/bin/osqueryd --autoupdate
seph
dpkg -l | grep launcher
Brandon
09/04/2019, 3:38 PM/usr/bin
after I build it and bake in a base AMI. Is that not preferred? This is for 14.04 so that's the approach I was taking since it appears there's only support for the launcher package for systemd systems?seph
Brandon
09/04/2019, 3:56 PMpackage-builder
and installed via dpkg -i launcher...deb
. But I was running into issues with 14.04. It's been a few weeks, but if I recall correctly it was because the launcher by default was starting the process via systemd and not supported via 14.04. I could be wrong on the memory recall however simple smile.seph
package-builder
defaults to building a systemd package. But you can build init, upstart, or nothing packagesBrandon
09/04/2019, 3:57 PMseph
Brandon
09/04/2019, 4:01 PMseph
Brandon
09/04/2019, 4:02 PMseph
Brandon
09/04/2019, 4:02 PMseph
Brandon
09/04/2019, 10:15 PMlauncher
and still receiving the error that's fixed by a service restart. Glad to post a followup if I find out any more info that might be helpful and add to the issue.