Title
#kolide
defensivedepth

defensivedepth

10/19/2020, 8:44 PM
Windows Server 2019, Launcher + autoupdate stable. Trying to enroll in Fleet, seeing the folllowing:
caller=level.go:63 level=info caller=extension.go:136 msg="extension interrupted" err="enrolling host: query enrollment details, (even with retries): done trying: query enrollment details: could not query the extension manager client: write field stop error: The pipe is being closed."
Any ideas?
Jason Green

Jason Green

10/21/2020, 7:45 PM
Started getting this, figure it out yet?
defensivedepth

defensivedepth

10/21/2020, 9:01 PM
Not yet - is yours from a fresh install? Stock Launcher / Fleet?
Jason Green

Jason Green

10/21/2020, 9:06 PM
Mine is from so-launcher in SO 2.3.0, same msi worked on other hosts.
defensivedepth

defensivedepth

10/22/2020, 12:06 PM
@seph Have you seen this before?
s

seph

10/22/2020, 12:09 PM
no, I don’t think I’ve seen that
12:11 PM
I think that’s laucher saying it can’t talk to osquery. More logs might help. Are you running this in the foreground? It’s easier to get debug logs.
12:12 PM
Or… A new launcher flag is
debug_log_file
which will mirror the logs to a file. Handy for debugging windows services. Note that there’s no rotation, and it’s a noisy debug log.
Jason Green

Jason Green

10/22/2020, 6:31 PM
Here's a pastebin with debug on: https://pastebin.com/b3DQ9xdU
1:24 PM
Could it be a problem with osquery-extension.exe not properly launching or connecting to the named pipe?
10:37 PM
@seph I posted some debug logs, does that give you any more clues?
defensivedepth

defensivedepth

05/04/2021, 11:16 AM
Seeing this error again... Seems to be very intermittent
m

MarkMurdock

05/24/2021, 9:18 PM
I am also seeing this error on some Server 2019 VMs. Anyone figure out what was going on?
defensivedepth

defensivedepth

05/24/2021, 11:35 PM
@MarkMurdock Is that with Security Onion?
m

MarkMurdock

05/25/2021, 12:25 AM
No in my case it's FleetDM on Ubuntu 20.04
12:26 AM
And Server 2019 with Launcher + autoupdate
s

seph

05/25/2021, 1:56 AM
The error quote here just says launcher couldn’t talk to osquery. But it doesn’t say anything about why. Gotta dig through the prior logs to see what the error might be