-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Windows] Service startup failing on CI with otel dependencies linked #4976
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
@leehinman after I spent all my timboxed time and talked to Julien and Pierre I'll let you to take over |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Note to self https://pkg.go.dev/runtime the |
So I'm not entirely sure it is Version before 4908This took 406ms to get through init
And one package took up over half that time, the
Version with 4908 but remove the windows build contraintsThis only took 206ms in init
And this time it was
Version 4908 with windows constraintsThis went through init much faster, only 48ms.
With
So #4908 actually made |
Next directions to look at golang/go#23479, specifically https://go-review.googlesource.com/c/sys/+/246317/3/windows/svc/sys_amd64.s and shirou/gopsutil#570. These seem to suggest that DLL initialization may be an issue for us. |
this is a really nice finding. not sure what we can do about that at this point though. i don't think we can optimize for DLL load time, especially in dependencies. |
At the moment, Agent is unable to run in OTel mode on Windows — support for Windows was explicitly removed by adding build constraints as part of #4908. If we remove these constraints we see failures in CI like so:
failed to start service (Elastic Agent): The service did not respond to the start or control request in a timely fashion.
One of the reason may be late reaction to the control events from a service manager and invocation of
service.ProcessWindowsControlEvents
as described in #4971Failures are present even if we move this to init function of alphabetically very early dependencies in main.
Timing here is also tricky, as dependencies get initialized before package linking them. so calling something in init does not mean it's being called first.
Event Log for elastic agent seems empty. Occasionally in linked draft above we see
24304 Jun 21 05:05 Error Elastic Agent 1 The description for Event ID '1' in Source 'Ela...
that could uncover some failures, but this is not present everywhere. But as i had this timeboxed i stopped here
https://techcommunity.microsoft.com/t5/iis-support-blog/the-description-for-event-id-1-from-source-getaccess-iis-runtime/ba-p/3744637
The text was updated successfully, but these errors were encountered: