Server Logs

Answered

Gord V.

July 21, 2020 04:13

On one of our servers I have a variety of Arecont cameras, a Mobotix, and 2 Hikvision DS-2CD2042WD-I among others.

On the server log I see a great many of these records:

2020-07-20 20:06:32.405 1424 WARNING nx::vms::server::analytics::MetadataHandler(0x2468f6f4168): Unable to find descriptor for nx.hikvision.videoloss
2020-07-20 20:06:32.701 1424 WARNING nx::vms::server::analytics::MetadataHandler(0x2468f6f4168): Unable to find descriptor for nx.hikvision.videoloss
2020-07-20 20:06:42.310 1424 WARNING nx::vms::server::analytics::MetadataHandler(0x2468f6f4168): Unable to find descriptor for nx.hikvision.videoloss

sometimes followed by....
2020-07-20 20:03:54.216 1424 WARNING nx::vms::server::analytics::MetadataHandler(0x2468f6f4168): TOO MANY SIMILAR MESSAGES: Unable to find descriptor for nx.hikvision.videoloss

So much so that I have even had storage errors like this: "Not enough HDD/SSD speed for recording to %drive_name%" (BTW I know your article on https://support.networkoptix.com/hc/en-us/articles/360003462293-Nx-Storage-Errors)

These are obviously attributed to the 2 Hikvision cameras, because when I discontinue motion and recording those cameras, then the those particular log records are no longer being created.

I have other Hikvision products (newer) on other servers with no issues like this.

What is the reason and a solution?

Thanks,
Gord

0

• 

  Norman

  • Network Optix team

  July 21, 2020 10:02

  Hi Gord V.

  These entries are intended for our developers and are nothing to worry. WARNING is not something that requires immediate action, I just was made this way to bring it to the attention in the logs. 

  We understand that this might cause confusing and therefore, from version 4.1, we moved such entries to the DEBUG logging level instead of the INFO logging level, which is the default for the server application. 

  Regarding the `Not enough HDD/SSD speed` events, it is highly unlikely these log entries cause these events, since the file size of the logs is very limited, it should not cause such issues.  

  You could try this by changing the log level temporary from INFO to ERROR.  If your assumption is correct, this should resolve the HDD/SSD events.  

   

  0

Please sign in to leave a comment.