Sockets not created on 1.26.3 on Fedora 19

[blackpot]

I'm running Fedora 19 with ZoneMinder 1.26.3, built from source with dependencies from various rpm sources. I have my test camera configured, and it appears okay (orange when in monitor mode, green in other modes), but when I try to view it live, nothing comes up other than the image frame.

Looking at the logs (and filtering out the pconnect warnings and redacting so the forum will let me post), I found this:

Code: Select all

$ grep -v pconnect /var/log/zm/apache-error.log | head
[Thu Sep 26 15:35:55.946229 2013] [suexec:notice] [pid 4153] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Sep 26 15:35:56.019718 2013] [auth_digest:notice] [pid 4153] AH01757: generating secret for digest authentication ...
[Thu Sep 26 15:35:56.020450 2013] [lbmethod_heartbeat:notice] [pid 4153] AH02282: No slotmem from mod_heartmonitor
[Thu Sep 26 15:35:56.098856 2013] [mpm_prefork:notice] [pid 4153] AH00163: Apache/2.4.6 (Fedora) OpenSSL/1.0.1e-fips PHP/5.5.3 mod_perl/2.0.8-dev Perl/v5.16.3 configured -- resuming normal operations
[Thu Sep 26 15:35:56.098923 2013] [core:notice] [pid 4153] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Thu Sep 26 15:36:47.819222 2013] [:error] [pid 4380] [client 192.168.254.53:63113] ERR [socket_sendto( /tmp/zm/zms-454765s.sock ) failed: No such file or directory], referer: <REDACTED>/index.php?view=watch&mid=2
[Thu Sep 26 15:36:53.850089 2013] [:error] [pid 4380] [client 192.168.254.53:63113] ERR [socket_sendto( /tmp/zm/zms-454765s.sock ) failed: No such file or directory], referer: <REDACTED>/index.php?view=watch&mid=2
[Thu Sep 26 15:36:59.922730 2013] [:error] [pid 4380] [client 192.168.254.53:63113] ERR [socket_sendto( /tmp/zm/zms-454765s.sock ) failed: No such file or directory], referer: <REDACTED>/index.php?view=watch&mid=2
...

...followed by many more similar socket errors. Earlier I had similar problems but it ended up being related to a ScriptAlias configuration line in the default Apache config on Fedora. I commented out that line (which was preventing access to the ZoneMinder binaries), but the socket errors still persist. I looked in /tmp/zm/, but the only socket I ever see created there is "zmdc.sock"--never anything else. Permissions on the directory are 774 apache:apache.

Any ideas?

Edit: I think I may have found the issue. Looking at the internal logs via the web, I get repeated "Error while decoding frame 0" in zm_remote_camera_rtsp.cpp. Still searching for a solution for this now...

[blackpot]

Just an update. I did verify that ffmpeg itself has no problems streaming from this camera (either MPEG4 or H.264), by testing with `ffmpeg -i rtsp://cam/live.sdp -c:v libx264 -preset ultrafast -crf 28 out.mkv' and verifying the output file (also tested with a different stream for H.264). So, I believe the issue lies with ZoneMinder and not ffmpeg.

I'm going to downgrade to an older version of ZoneMinder and see if it will work.

Edit: Nevermind, I got it working.

What was wrong? Well, I didn't realize that using a source type of "remote" and then selecting rtp/rtsp does not use ffmpeg's implementation of rtsp. It instead uses some internal implementation..or possibly some rtsp lib directly. Either way, it wasn't working--but ffmpeg's rtsp was (at least from the command line). Almost accidentally I realized that I should be using a "source type: ffmpeg" and then just typing in the ffmpeg URL that was working, and voilà, things were working as expected.

This is a bit confusing as I thought the "remote" source type for RTSP was just a front end for ffmpeg, but it's not (or it's not working correctly).

[chriswiggins]

Hey blackpot,

You're right in your discovery. Someone has actually written a few patches to the RTSP library to make it work with newer cameras. I've never understood why we have both the RTSP and FFMPEG source options but I would say this goes back to when FFMPEG's RTSP support was crappy.

Don't worry, we are working on all these weird things

Chris

[blackpot]

Ah, thanks for the update. I was mostly confused due to the previous install of Zoneminder I tried (it was 1.25.something--installed from a Fedora RPM IIRC) was not compiled with ffmpeg support, and said that RTSP support required ffmpeg, leading me to believe that it was just a front end or wrapper for ffmpeg when "remote" was selected (and using rtp/rtsp). And, maybe that was true with 1.25, but I decided to try 1.26 (which is what I'm sticking with) as getting 1.25 to compile with a modern ffmpeg was difficult to say the least.

Glad to hear you guys are working on it, and I want to thank all of you for the work you have done.