EMS hanging up

1. When testing a trial version of Evostream with our cameras, due to the time limit of 2 hours, no problems were observed. 2. After buying the license, during the development of the service, Evostream’s rare hangups were observed when interacting with cameras, once a week, a month, two months. 3. Hangs do not happen systematically. 4. If you connect more cameras to the service, during the test operation, the hangs will happen much more often. 5. Observe the following symptoms: 5.1. Freeze the HTTP API Evostream. The EMS web service stops responding, while video from the cameras can be written further. 5.2. After stopping the service with the stop command, we observe one or several hanging processes with the capture of the evo-avconv video. Typically, all processes are unloaded when the service is stopped. 5.3. If in this situation, without restart ing the evostreamms service, stop the hung evo-avconv process, then the Evostream HTTP API resume operation, the service responds to requests again. 5.4. In very rare cases, if one or more evo-avconv processes hang, the Evostream HTTP API is available, but the events on the web server are no longer sent by the evostream (EMS Notification System). 5.5. In fairly rare cases, one of the hung processes can consume up to 99% of the CPU.