Recording interrupted

evostream.934.1516631840791 One occurrence e.g. was between 1516633580 and 1516633583

Hello, Can you specify what local streamname was involved in the problematic record process?

Usually, record process gets interrupted whenever the stream gets disconnected from EMS. Based from my initial analysis in the logs you’ve sent, whenever the record command continues.. its corresponding streamname is said to be not yet available. This means that either the corresponding stream is not yet present in EMS or it got disconnected. Another thing I’ve noticed is that there are streams which get unregistered from EMS every time “removeconfig” command gets called. Note that if what your removing that time is also a stream, it also means that that stream gets disconnected from EMS.  

Hi, For example the stream “D8-49-2F-A4-AB-02_52-54-00-30-43-7B_1280x720_15_22_2048_45”. But the strange thing is all streams from all (ca. 8) cameras are disconnected about at the same time. Good point that it says “stream is not available yet”. We also thought it might have to do with the network being overloaded. On the other hand, why is it in such a regular interval… We will also check what might cause the removeconfig command… Thanks Silvan

I think the root cause of it is somewhere in our system. So, thanks anyway for your time… Silvan