Record keepAlive Problem (v1.7.1)

Record keepAlive Problem (v1.7.1)

Support ForumCategory: Usage and FeaturesRecord keepAlive Problem (v1.7.1)
bbischan asked 4 years ago
My post on this item is very similar to a previous post referenced below.https://evostream.com/question/record-keepalive1-record-doesnt-resume/I am encountering the same problem with v1.7.1 record keepAlive. We have 20 EMS v1.6.6 servers running 5000+ streams with 24×7 chunked (30 min) recording and we have not seen this problem before. It appears to be an intermittent problem, as we have successfully tested rebooting / disconnecting cameras running v1.7.1 and everything works as expected. We have not been able to determine what conditions lead to this problem, but it appears to be internal to the application.A few notes on what we have observed during testing:Platform: Ubuntu 14.04- When we detect this condition we find that recording is no longer working. Inbound pullStream is worrking and all outbound rtmp streams remain alive.- Confirmed that pushPullSetup.xml still has 2 configs (pullStream and record).- Running listConfig we find both records also exist.- listConfig record is reporting \”Disconnected\”- Using removeConfig followed by pullStream/record in an attempt to restore recording returns success using API- After attempting to restore recording pushPullSetup.xml contains only the pullStream config. Record config is missing.- The only thing that seems to correct the problem is a restart of evostream.When comparing v1.6.6 to v1.7.1 config.lua I find the `streamsExpireTimer` parameter is the same default value of 10 seconds. I have not attempted to change this default value since v1.6.6 works as expected using this value.



Offcanvas

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.