I’ve run into an issue on two different Windows servers running 2016 and 2019 where the sidecar service will start, but the collectors won’t. The logs just state that a configuration change was detected and rewrites the file, but times out when trying to validate the configuration. If I start the collector from within Graylog, it starts without any issues. I’m running Sidecar 1.1.0 with Graylog 4.2.4 on Windows Server 2016 and 2019.
Has anyone else seen anything like this?
time=“2022-01-06T12:16:55-05:00” level=info msg=“Starting signal distributor”
time=“2022-01-06T12:17:05-05:00” level=info msg=“Adding process runner for: winlogbeat”
time=“2022-01-06T12:17:05-05:00” level=info msg="[winlogbeat] Configuration change detected, rewriting configuration file."
time=“2022-01-06T12:17:35-05:00” level=error msg="[winlogbeat] Unable to validate configuration, timeout reached."