https://github.com/osquery/osquery logo
Join Slack
Powered by
<@UB2083719> What platform? Issue 164 wasn’t well ...
# kolide
s
@brandon What platform? Issue 164 wasn’t well formed.
b
This was on Ubuntu 14.04 and using an upstart script for launcher
Copy code
launcher --version
launcher - version 0.10.3
  branch: 	master
  revision: 	c0115f999046a62ca43889c743d18826c5c4c53c
  build date: 	2019-07-24
  build user: 	seph (seph)
  go version: 	go1.12.5
s
0.10.3 is the stable release. Do you know what version you started with? You shouldn’t see an upgrade from that version
b
I just verified the 
launcher
binary on another server without 
autoupdate
in the flag and confirmed it was the same version, 
0.10.3
s
What version of the launcher package is installed?
b
Sorry for the dumb question, but what's the best way to verify that besides 
launcher --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
s
dpkg -l | grep launcher
So… What I’m trying to tell is whether it updated. So if you started with something older than 0.10.3, and it updated, but you got an error. Vs, starting with 0.10.3, and somehow hitting that code
b
Ah thought that's what you meant, apologies for confusion. So I'm not installing launcher as a package, just copying the binary to 
/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?
s
Not using a package is fine. I make pacakges, but I have no expectations about what you might be doing. the packaging supports many things. See https://github.com/kolide/launcher/blob/master/docs/package-builder.md Building it yourself, and using autoupdate is interesting. What led you to that?
b
Initially I tried building the package on 14.04 using 
package-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.
s
On linux, 
package-builder
defaults to building a systemd package. But you can build init, upstart, or nothing packages
b
That is something I missed in the documentation then! Apologies.
s
No worries! It’s not directly related here.
So… Using autoupdate implies you trust the binaries I build. So why build your own and not use the released ones?
Anyhow, I agree this all smells like weird code around auto update. Feel free to comment in that issue.
b
Total oversight on my part that you had releases already for the binary. Just in testing stage now to deploy across all environment, so I think it's worth trying your pre-built binaries. I'm guessing the pre-built binary is optimized for systemd?
s
no. Launcher is launcher, there is no difference. It’s a static go binary.
👍 1
The only differences between the init scripts is the init scripts.
👍 1
b
I'll stick with the pre-built releases from now on
s
I mean… I ❤️ that people build their own. But I’d advise against autoupdate if you’re doing that.
b
Thank you for the advice and information 🙇
s
Still no idea how you hit that error. But this is all a side step to avoid it for a bit.
b
FWIW, I used the published release, including replacing the version of 
launcher
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.
2 Views
Open in Slack
PreviousNext
Powered by