NX Witness server keeps disconnecting from cloud
Completed
hello
on one of customer site, Nx witness keeps to be disconnected to cloud (and I can get access to server via anydesk/teamviewer)
during investigation, i found this on logs, what that mean ?
I checked user id, cannot find on users allowed
2023-05-11 02:16:15.255 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:26:15.216 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:26:15.235 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:26:15.276 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:26:15.283 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:26:15.290 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:26:15.296 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:26:15.302 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:36:15.188 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:36:15.212 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:36:15.231 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:36:15.234 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:36:15.235 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:36:15.238 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:36:15.240 853 WARNING QnServerDb(0x7feca404ef50): Sessions limit (5000) for user { id same user } is reached: 5000 sessions
2023-05-11 02:46:03.172 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): OS CPU usage 7.88%
2023-05-11 02:46:03.172 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): Process CPU usage 4.35%
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): OS memory usage 20.41%
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): Process memory usage 4.64%
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): HDD usage:
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): loop1: 0.00%
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): nvme0n1: 0.60%
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): sda: 4.19%
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): File handles:
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor: Opened FDs: 188
2023-05-11 02:46:03.173 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): Network usage:
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): br-9757292ec5ce. in 0KBps, out 0KBps
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): br-c2731f1df506. in 0KBps, out 0KBps
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): docker0. in 0KBps, out 0KBps
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): enp2s0. in 3571KBps, out 56KBps
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): enp3s0. in 0KBps, out 0KBps
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): lo. in 0KBps, out 0KBps
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): veth4d2c1b8. in 0KBps, out 0KBps
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): veth5da6a63. in 0KBps, out 0KBps
2023-05-11 02:46:03.174 832 INFO nx::vms::server::GlobalMonitor(0x7feca403bcf0): vetha685721. in 0KBps, out 0KBps-
Dear Julien ROMANO,
I hope this message finds you well. To ensure accurate information, I have consulted one of my colleagues, who is currently asleep and will be reviewing the matter later. Rest assured, I will promptly inform you as soon as I receive further details.
In order to gain a better understanding of the situation, I have a few initial inquiries for clarification:
-
When you mention the system being 'disconnected,' are you referring to the system being physically disconnected from the cloud, necessitating the system owner to reconfigure its connection to Nx Cloud? Or do you mean that the system is simply unavailable at the moment?
-
Is it possible that API calls are being directed through the cloud using the vmsproxy.com option?
Thank you, should you have any additional questions or concerns in the meantime, please feel free to let us know.
Best regards.
0 -
-
hi Norman
1 - the VMS isn't available (through cloud) to connect for remote NxWitness client. 70% of time, the VMS location is greyed (for me, and all customers of this site)
2 - what do you mean ?
I note that when i connect to server with anydesk/teamviewer (because NxCloud doesn't work, so i check server), the Nxcloud connection changed to be available within 10sec. (no powersaving is activated or lockscreen)
We work under Ubuntu 20.04.5 LTS
0 -
Hi Julien ROMANO,
I hope this message finds you well. I wanted to inform you that I have moved the topic into a support ticket. This will allow us to conduct further investigations in a more organized and efficient manner.
0 -
Made some manual changes on the cloud side for this specific system. Fixed.
0
Please sign in to leave a comment.
Comments
4 comments