-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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: timeout during CPU fingerprinting #4439
Comments
I experienced the same situation in 0.8.3 and resolved it with 0.8.4 because of #4265 for the log line and #4268 to extend the timeout for queries to 10 seconds. It is interesting that you are seeing 17 second WMI queries, this will cause the newly extended timeout to still fail for you. However, you could use the same technique used in #4268 and extend that timeout constant. This would at least keep your modified code to the Nomad project. |
Nice! Thanks for info. 10 seconds is too short for our case, clearly. |
Hello, Below are testing results on real windows 2012 R2 servers in production environment. Numbers are seconds of execution. Tests were repeated 20 times for each of four servers.
|
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
v0.8.3
Operating system and Environment details
Windows
Nomad Client logs (if appropriate)
Issue
Nomad client crashes at start after CPU fingerprinting failes. I have enhanced logging and able to obtain proper error message:
We see this problem on small set of windows boxes. On those boxes request to WMI take a lot of time (17 seconds). It clearly depend on environment, can't say any specific reason for this behavior.
I am attaching my patch which solved the issue for us. I am not opening pull request because the fix was done in external library.
0001-increased-timeout-during-CPU-fingerprinting.patch.txt
The text was updated successfully, but these errors were encountered: