Socket /run/zm/zms-XXXXXXs.sock does not exist.

[jason0x21]

I've recently upgraded Ubuntu from 20.04 to 22.04, and then Zoneminder from 1.34.x to 1.36.24. Almost everything in ZM appears to be working now, except for live view (and viewing events.) I get the following message...

Code: Select all

Socket /run/zm/zms-628960s.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.

Looking in /run/zm/, I see that zms-628960w.sock does exist, but that's apparently not enough? Looking in the apache access logs it looks like zms is getting called successfully....

Code: Select all

127.0.0.1 - - [14/Aug/2022:08:50:55 -0400] "GET /zm/cgi-bin/zms?scale=100&mode=jpeg&maxfps=30&buffer=1000&monitor=1&connkey=628960&rand=1660481454 HTTP/1.1" 200 661224 "http://localhost/zm/index.php?view=watch&mid=1" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0"
127.0.0.1 - - [14/Aug/2022:08:50:56 -0400] "GET /zm/index.php?view=request&request=stream&connkey=628960&command=99 HTTP/1.1" 200 923 "http://localhost/zm/index.php?view=watch&mid=1" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0"

So it looks like everything the FAQ says is in order, and I'm not sure how to get more debug data out of zms to see where things are going awry. Any ideas?

[haus]

I get this when I don't access my server using https, if that helps at all. My console is filled with 400 Bad Request responses, but the apache logs show 200 like yours do. If I switch to https, it works fine.

[justanotherguy]

Are the events that you are trying to view have the codec H265?

[jason0x21]

I get this when I don't access my server using https, if that helps at all. My console is filled with 400 Bad Request responses, but the apache logs show 200 like yours do. If I switch to https, it works fine.

I'm not getting any 400 bad request, it looks like all the errors are coming from the streamer. Thanks though!

[jason0x21]

Are the events that you are trying to view have the codec H265?

How would I know? I've got Foscam FI9853EP set up with FFMPEG and RTSP. I don't think the cameras are new enough to do H265. These are the same settings from before I upgraded zoneminder. (Which worked before). Thanks!

[iconnor]

They key here is that you don't get it when accessing via http. There is a difference in your cgi path between the http and https config.

So take a close look at your apache config in terms of ScriptAlias etc and your https config.

[haus]

They key here is that you don't get it when accessing via http. There is a difference in your cgi path between the http and https config.

So take a close look at your apache config in terms of ScriptAlias etc and your https config.

I think that might be referring to my post (not OP)?

For my case it was an SSL error indeed. I realized that since I'm using multiport, requests to https://mydomain/zm would always work since my Apache VHost listed all the ports (30000, etc.) and my SSL cert is set up. If I access using https://IP/zm, as long as I have an SSL exception stored in the browser, it works (otherwise it fails on SSL error).

If I access http://IP/zm, (no https), as soon as ZM tries to load a stream via http on an SSL-only port (e.g., 30000) then streaming doesn't work and I get the error "socket does not exist". In the browser I have "bad request" errors due to the mismatched protocol.

From the first post, OP's log shows "http" access only so I wonder if he's not using SSL and the source of his socket error is different?

[aayushkm52]

I have an ezviz db1 which is the same hardware, I just have rtsp://admin:xxxxxx@192.168.1.194 as the source and I can view the stream. Try something like that?
https://routerlogin.ltd/
https://pikashow.ltd/

[jason0x21]

I ended up reinstalling from scratch and redoing the configuration and that seems to have solved the problem.