Skip to content
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

failed to waitForNotification: callbackNumber does not exist in callbackMap #2367

Open
jkroepke opened this issue Jan 29, 2025 · 0 comments
Open

Comments

@jkroepke
Copy link

jkroepke commented Jan 29, 2025

Hi,

xref:

a EKS user recently reports a issue with the windows_exporter.

[...]
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1095
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1096
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1097
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1098
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1099
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1100
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1102
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1103
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1104
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1105
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1106
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1109
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1108
[...]

After a quick research, the messages are coming from

log.G(ctx).WithField("callbackNumber", callbackNumber).Error("failed to waitForNotification: callbackNumber does not exist in callbackMap")

As maintainer of windows_exporter, I would like to ask how I can identify the root cause? Or do I implement hcsshim wrongly?

  • Windows: Server 2019
  • hcsshim version: github.com/Microsoft/hcsshim v0.12.7

It is noticeable, that the same error appears with v0.12.5 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant