Title
#kolide
z

Zach Zeid

09/02/2020, 2:48 PM
👋 I'm seeing some behavior with kolide fleet on ECS. I'm running a task definition that is supposed to start up kolide fleet with
fleet serve
. After
fleet serve
is running, nothing from stdout is getting logged. Is this expected, if so is there a way around this?
sundsta

sundsta

09/02/2020, 4:09 PM
Fleet doesn’t generate a ton of logs, but you should at least see something like this on startup.
{ "msg": "listening", "address": "0.0.0.0:8080", "transport": "http", "ts": "2020-09-02T16:02:55.480404453Z" }
z

Zach Zeid

09/02/2020, 4:09 PM
I do see that actually, the problem I'm seeing in the script I'm running is everything after
fleet serve
doesn't show up
4:10 PM
so things like
echo "hello world"
doesn't seem to get to stdout
sundsta

sundsta

09/02/2020, 4:11 PM
What do you mean after?
fleet serve
never exits until you stop the process, so nothing after that command in a script would run
z

Zach Zeid

09/02/2020, 4:11 PM
I see.
4:16 PM
Is there a way to load queries and packs via
fleet serve
? My understanding is
--config
is only for fleet configuration, not packs
sundsta

sundsta

09/02/2020, 5:11 PM
No. You load them via fleetctl or similar. They persist in the database so you only need to do it once (per environment)