NxServer Server stopped unexpectedly
Answered
I'm sorry not to speak ENGLISH fluently
7 servers of version 4.2.0.32840 are integrated and operated.
About 27 dahua PTZ cameras are connected to each server and recorded for one year.
This system has been in operation for over a year.
Recently, 5 out of 7 servers have experienced a server failure called "Reason: Server stopped unexpectedly".
Please let me know if there is any workaround.
In addition, there was a problem that data was lost in the previous version 4.1, and there is a history of version upgrade to version 4.2 half a year ago.
-
Hi mutou takafumi,
When the message:
"Reason: Server stopped unexpectedly".
occurs, it typically means that the VMS closed outside its control, like a power outage, server crash, etc.
It is important to investigate the cause of these crashes.
Furthermore, it is recommended to update to the latest release of Nx Witness, v5.0.0.35745. This is mandatory for support.
0 -
Thank you for your reply.
However, it is not possible to upgrade to the latest version at this time.
That is, v4.1.0.32045 has a problem that recorded data is lost, and v4.2.0.34860 has a problem that PTZ cannot be operated and the server freezes, so there is hesitation in v5.0. It's from
（150 cameras,The camera is DH-SD22204UE-GN made by dahua,
6 servers, 25 registered per server, 1 year of recording time, camera settings of HD 5fps 700kbps）The current version, v4.2.0.32840, has only the problem of "The server stopped unexpectedly", so I think it's better than the previous problems, and I'm afraid that further problems will occur by upgrading the version. I am concerned
We have a plan to respond to the customer's site soon, and we plan to lower the bps of the camera in order to reduce the load on the server.
Since there were other articles like the following, is it possible to check if you copy and share the dump file?
0 -
Dear mutou takafumi,
We would like to remind you that in order for us to provide the best support possible, it is mandatory to use the latest available release of our software. This ensures that any bugs that were present in previous builds have been resolved and that the latest patches have been implemented to address any issues that may have arisen in the previous release.
In the event of a server outage, it is important to determine the cause first. For example, if the outage was caused by a power outage, there may be nothing to investigate in the crash dumps. Investigating crash dumps is a very time-consuming task, and we hope you understand that it is not always the first action we take.
We also want to address the issue you reported occurring on 5 out of 7 servers, which happened for the first time in a year. We recommend looking into the affected servers, as it is possible that the issue was caused by a forced restart to apply updates.
We appreciate your understanding and cooperation as we work to ensure the smooth functioning of your systems. Please do not hesitate to contact us if you have any further questions or concerns.
Best regards.
0 -
Thank you for your reply.
I will ask the customer about the version upgrade.
Are there any countermeasures against unexpected server outages? (I can't do the version upgrade because I didn't ask for it this time.)
I am considering the following measures, but if there are any other measures, please let me know
・lower the bitrate（H.264 700kbps→H.265 400kbps）
・server restart
・Archive reindex
0 -
Dear mutou takafumi,
I hope this message finds you well. I would like to share my thoughts on the matter at hand.
Regarding the countermeasures that were mentioned, I believe they should only be taken if the hardware does not meet the recommended specifications.
In my opinion, it is essential to identify the root cause of any issue before taking any preventive measures. When the logs report 'Server stopped unexpectedly' it is usually due to an external cause, such as a power outage, hard reset, bad update restarts, and so on. Therefore, finding the root cause should be the first step in resolving the issue.
A memory leak also could cause the issue, but I understand that it happened just once after a year of no problems. It is unlikely that a memory leak caused this problem, as it would typically cause a crash much sooner and continuously.
Thank you for considering my input, and please let me know if you have any questions or concerns.
Best regards.
0
Post is closed for comments.
Comments
5 comments