Re: Update from 1.29 to 1.30 but blank ZM webpage
Posted: Wed May 03, 2017 6:10 am
I'm experiencing the same issue where streaming from a Hikvision camera does not appear to work, however alarms and stills are viewable.
Ubuntu 1404 running ZM v1.30.3.
I have fixed the cgi-bin path issues which others have also experienced. I do not get any script errors in /var/log/apache2/error.log after the fix.
It appears to be a problem with the .sock file which is not found.
I have check the permissions on the /var/run/zm directory which are correct:
I have also tried using /tmp/zm instead and I get the same error:
The sock file name in the error is Socket /tmp/zm/zms-711362s.sock yet I only ever see the sock file shown above, zmdc.sock.
During my research I read something about the .sock file names being incorrect, maybe a bug? Has anyone resolved this issue?
Any help is greatly appreciated.
Ubuntu 1404 running ZM v1.30.3.
I have fixed the cgi-bin path issues which others have also experienced. I do not get any script errors in /var/log/apache2/error.log after the fix.
It appears to be a problem with the .sock file which is not found.
Code: Select all
[Wed May 03 15:36:24.057586 2017] [:error] [pid 1899] [client 192.168.43.18:56672] ERR [Socket /tmp/zm/zms-711362s.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/latest/faq.html#why-can-t-i-see-streamed-images-when-i-can-see-stills-in-the-zone-window-etc for more information.], referer: http://192.168.43.209/zm/index.php?view=watch&mid=1
Code: Select all
drwxrwxrwx 2 www-data www-data 60 May 3 15:28 zm
Code: Select all
srwxr-xr-x 1 www-data www-data 0 May 3 15:28 zmdc.sock
During my research I read something about the .sock file names being incorrect, maybe a bug? Has anyone resolved this issue?
Any help is greatly appreciated.