Socket does not exist error but can view live stream
Posted: Thu Nov 22, 2018 6:48 am
Just upgraded from 1.30.4 to 1.32.2 to take advantage of H264 passthrough for IP cameras.
When viewing live stream either by each camera or montage, it takes a few seconds to display live stream. In the log, we get the following(FIRST ERROR) 3-4 times per camera: "Socket /var/run/zm/zms-063049s.sock does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit. Please go to http://zoneminder.readthedocs.io/en/lat ... window-etc for more information."
Then, SECOND error "No data to read from socket" a couple of times and THIRD Error "Timed out waiting for msg /var/run/zm/zms-063049s.sock"
Then a few seconds later (5sec?), live stream appears. Since live stream eventually appears, we presume CGI apache is setup properly.
Question: What can we do to eliminate these error messages?
When viewing live stream either by each camera or montage, it takes a few seconds to display live stream. In the log, we get the following(FIRST ERROR) 3-4 times per camera: "Socket /var/run/zm/zms-063049s.sock does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit. Please go to http://zoneminder.readthedocs.io/en/lat ... window-etc for more information."
Then, SECOND error "No data to read from socket" a couple of times and THIRD Error "Timed out waiting for msg /var/run/zm/zms-063049s.sock"
Then a few seconds later (5sec?), live stream appears. Since live stream eventually appears, we presume CGI apache is setup properly.
Question: What can we do to eliminate these error messages?