Security token retrieval failure from the Recording Server when the driver is loaded

Hi!

We have a driver that works, but only for a while. The Recording Server seems to not be able to retrieve security tokens after about a day, day and a half, and that disconnects the server from the Management Server, disconnecting that from the Smart Clients, which causes frustration.

Is it at all possible it is our fault by e.g. memory use or network overloading, or is it more likely an IT issue? I do not do anything strange in the driver, I cache about 7GB in memory and the server has 64, with most of it free, but maybe there are usage spikes that I do not know about.

Kind regards,

Peter

I find it difficult to see how. If you haven’t seen excessive memory consumption or the server go into 100% CPU, which could potentially be caused by the driver, I don’t see how.

Would it be possible to test the Recording Server without your driver, just with cameras using ‘ordinary’ drivers, and in that way show or reject that your drivers are the cause of the issue?

If you would like to test it might be an idea to temporarily lower the Token timeout, there is a description how to do that here - https://supportcommunity.milestonesys.com/KBRedir?art=000032987&lang=en_US

Thank you for the feedback!

If I run the Recording Server without the driver, it keeps on running for days, and the moment I load the driver it breaks within about 15 hours.

I have gathered some logs from two files in the recording server logs, does this shed any light? I am at a bit of a loss how this happens. The device is setup as a hardware device with channels, it shows live and recorded video and audio. I pull the footage from the device as connectivity is intermittent and footage gets stored after the fact, not immediately.

I set it up by first developing the video live view, then playback, then live audio, and playback audio is still outstanding.

The audio streams were added after the fact and I did “update hardware” to load the audio playback ability after I changed it to on-board storage of audio.

Security token file:

2025-07-18 06:37:39.758+02:00 [ 523] WARNING - Token verify failed: Unavailable

2025-07-18 06:37:39.877+02:00 [ 39] INFO - Requested token from server

2025-07-18 06:37:39.877+02:00 [ 39] WARNING - Token requested from server is unavailable

2025-07-18 06:37:39.877+02:00 [ 39] INFO - Token added (6)

2025-07-18 06:37:39.877+02:00 [ 603] WARNING - Token verify failed: Unavailable

2025-07-18 06:37:39.898+02:00 [ 39] INFO - Requested token from server

2025-07-18 06:37:39.898+02:00 [ 39] WARNING - Token requested from server is unavailable

2025-07-18 06:37:39.898+02:00 [ 39] INFO - Token added (6)

And the other log file:

2025-07-18 06:47:35.468+02:00 [ 39] INFO - GetSecurityToken Token

2025-07-18 06:47:35.488+02:00 [ 39] INFO - GetSecurityToken Token

2025-07-18 06:47:37.802+02:00 [ 374] ERROR - HttpRequestException - The SendAsync request message failed: An error occurred while sending the request.

It seems I was hogging too many network resources. Fixed!