Connection with NxCloud is interrupted
Completed
Hello
13 network cameras are connected, and 1 client PC is connected locally and 1 client PC is connected via the cloud.
On October 7th, a communication error occurred on the monitor connected to the client PC.
When I checked the server log, various logs remained on October 7th. Is it possible to check this log and see where the problem is?
The local client PC is always displayed on the screen and connected, and the client PC via the cloud is always connected on weekdays (it is shut down on Saturday and Sunday).
2024-10-07 13:33:08.616 1b44 INFO MediaServerProcess(0x263fc8ddc20): Network Optix Media Server version: 5.1.3.38363, revision: e4d0848daafa
2024-10-07 13:33:08.616 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): OS CPU usage 0.00%
2024-10-07 13:33:08.616 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): Process CPU usage 0.00%
2024-10-07 13:33:08.616 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): OS memory usage 34.48%
2024-10-07 13:33:08.616 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): Process memory usage 3.63%
2024-10-07 13:33:08.616 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): HDD usage:
2024-10-07 13:33:08.616 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): HDD0: 3.53%
2024-10-07 13:33:08.616 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): HDD1: 0.01%
2024-10-07 13:33:08.616 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): File handles:
2024-10-07 13:33:08.617 1b44 INFO nx::vms::server::GlobalMonitor: Disk files: 54
2024-10-07 13:33:08.617 1b44 INFO nx::vms::server::GlobalMonitor: Sockets, pipes: 107
2024-10-07 13:33:08.617 1b44 INFO nx::vms::server::GlobalMonitor: Character devices: 0
2024-10-07 13:33:08.617 1b44 INFO nx::vms::server::GlobalMonitor: Unknown: 9
2024-10-07 13:33:08.617 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): Network usage:
2024-10-07 13:33:08.617 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): Intel(R) Gigabit CT Desktop Adapter. in 2670KBps, out 1603KBps
2024-10-07 13:33:08.617 1b44 INFO nx::vms::server::GlobalMonitor(0x263fcacd750): Intel(R) Ethernet Controller (3) I225-V. in 48KBps, out 2361KBps
2024-10-07 13:33:19.551 878 INFO nx::vms::server::QnStorageManager: removeEmptyDirs: Finished. 12ms elapsed
2024-10-07 13:33:46.866 1514 ERROR nx::network::upnp::AsyncClient(0x263fe9c5820): Could not parse message from //192.168.24.1:6506/ctl/f251ccdd11
2024-10-07 13:33:46.866 1514 ERROR nx::network::upnp::AsyncClient(0x263fe9c5820): Could not parse message from //192.168.24.1:6506/ctl/f251ccdd11
2024-10-07 13:33:49.885 1514 ERROR nx::network::upnp::AsyncClient(0x263fe9c5820): Could not parse message from //192.168.24.1:6506/ctl/f251ccdd11
2024-10-07 13:33:52.901 1514 ERROR nx::network::upnp::AsyncClient(0x263fe9c5820): Could not parse message from //192.168.24.1:6506/ctl/f251ccdd11
2024-10-07 13:33:55.918 1514 ERROR nx::network::upnp::AsyncClient(0x263fe9c5820): Could not parse message from //192.168.24.1:6506/ctl/f251ccdd11
2024-10-07 13:33:58.936 1514 ERROR nx::network::upnp::AsyncClient(0x263fe9c5820): Could not parse message from //192.168.24.1:6506/ctl/f251ccdd11
2024-10-07 13:34:01.938 1514 ERROR nx::network::upnp::AsyncClient(0x263fe9c5820): Could not parse message from //192.168.24.1:6506/ctl/f251ccdd11
2024-10-07 13:39:58.802 1518 WARNING nx::network::cloud::IncomingTunnelPool(0x26381b51aa0): sockets queue overflow: 128
2024-10-07 13:40:03.279 1518 WARNING nx::network::cloud::IncomingTunnelPool(0x26381b51aa0): sockets queue overflow: 128
2024-10-07 13:40:03.925 1518 WARNING nx::network::cloud::IncomingTunnelPool(0x26381b51aa0): sockets queue overflow: 128
2024-10-07 13:40:03.929 1518 WARNING nx::network::cloud::IncomingTunnelPool(0x26381b51aa0): sockets queue overflow: 128
2024-10-07 13:40:05.227 1518 WARNING nx::network::cloud::IncomingTunnelPool(0x26381b51aa0): sockets queue overflow: 128
2024-10-07 13:40:05.228 1518 WARNING nx::network::cloud::IncomingTunnelPool(0x26381b51aa0): sockets queue overflow: 128
2024-10-07 13:40:05.232 1518 WARNING nx::network::cloud::IncomingTunnelPool(0x26381b51aa0): sockets queue overflow: 128
-
Hi mutou takafumi,
I hope you’re doing well! I noticed that this topic hasn’t received any engagement from the community yet, and I wanted to check in with you. Is the issue you mentioned still relevant or something you’re looking to resolve?
Best regards.
-
Thank you for your reply
This is a problem that has not yet been resolved.
I have learned a little about the cause of the problem, and a problem occurs on the server when the [sockets queue overflow: 128] log occurs.
The problem can be resolved by restarting the server itself or restarting the server application.
If you know when this log occurs and how to deal with it, please let me know.
This may be unrelated, but security software is installed on the client PC and is always running.
-
Hi mutou takafumi.
Upon analyzing the logs, it appears that the socket queue overflow warnings are likely caused by a large volume of incoming requests generated by the security software. This software might be actively monitoring or interfering with communication, which restricts the server's ability to process requests efficiently.
To address this, we recommend the following actions:
-
Add Exceptions in the Security Software:
Please configure your security software to add exceptions for the following applications and devices:- MediaServer Application
- Desktop Client Application
- Peripheral Devices (e.g., IP Cameras)
-
Verify the Configuration:
Once exceptions are added, please verify that communication between the MediaServer, desktop client, and IP cameras is seamless. This step ensures the security software does not interfere with normal operations.
These changes should resolve the socket queue overflow warnings and improve overall system performance.
Best regards.
-
Post is closed for comments.
Comments
4 comments