2.0-M4 request timed out issues
-
Since upgrading to 2.0-M4 (directly from 1.2.17), I'm having issues with my NetXMS server on Windows. It now finds some extra ethernet interfaces on the server node (e.g. a loopback pseudo-interface and a Teredo Tunneling pseudo-interface), and immediately raises alarms for them being down. I can change the interface expected state to ignore, but if I try to Terminate the alarms, it just sits there for ages before saying "Terminate alarms has encountered a problem. Cannot terminate alarm: request timed out."
After this, almost nothing works in the console - I can't even open the DCI config for a node (you get the same timed out errors). Restarting the service on the server is the only way to fix it, at which point the extra interfaces get found again (they aren't shown when the console first loads after a server restart), and the cycle begins again.Also, when restarting the service on the server, even after a fresh reboot of the server, the NetXMS Core service will not stop without giving an error 1053 - "the service did not respond to the start or control request in a timely fashion". It does then stop, and seems to start again OK, but it's very annoying when trying to fix the above issue, or even change server config or anything.
If it matters, servers is Windows 2008 R2 SP1.
-
-
Hi,
please set server logging to file and set debug level to 6, then try to reproduce issue with timeout and sen us debug logs.
Best regards,
Victor
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login