Closed reg1oDATA closed 2 years ago
I think you are running into the 30 second timeout. There is already an issue to make that more flexible: Graylog2/collector-sidecar#431
hi @patrickmann, we also suspect that the problem is related to the timeout. when we start winlogbeat manually everything works as well.
Problem description
When applying a Filebeat or Winlogbeat configuration to a Graylog Sidecar running on Windows Server 2012, the sidecar throws this error message:
time="2022-07-28T08:00:29+02:00" level=error msg="[winlogbeat] Unable to validate configuration, timeout reached."
Sometimes, the above error will not occur. The following error will occur instead:
Could not start service: The service did not respond to the start or control request in a timely fashion.
Environment