No video & socket_send_to failed: no such file or directory

[TylerSchwend]

Attempting to combine reports so these are more easily found.

http://www.zoneminder.com/forums/viewto ... 29&t=19246
http://www.zoneminder.com/forums/viewto ... 29&t=19222
http://www.zoneminder.com/forums/viewto ... 29&t=19172
http://www.zoneminder.com/forums/viewto ... 29&t=19200

Please include the following information in your replies:

• OS: Debian unstable
  Kernel (uname -r): 3.2.0-2-686-pae
  Zoneminder install format: Package, maintainer "Peter Howard"
  Zoneminder ver: 1.25.0-1
  Apache install format: Package, maintainer "Debian Apache Maintainers"
  Apache ver: 2.2.22-5
  Perl install format: Package, maintainer "Niko Tyni"
  Perl ver: 5.10.1-17squeeze2
  # cameras: 6
  # zones: 10
  Any changes: Applied upgrades to Zoneminder and system components...
  Any other errors: No

Other observations: The exact error is "socket_sendto( /tmp/zms-140122s.sock ) failed: No such file or directory" and of course the socket file name changes. If I run "ls ; sleep 1" repeatedly while launching a camera view:
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock zms-081287w.sock
lost+found root zm zmdc.sock zms-081287w.sock

The error in the ZM log (repeated) is:
2012-05-17 11:05:08.772879 web_php 6591 ERR socket_sendto( /tmp/zms-081287s.sock ) failed: No such file or directory /usr/share/zoneminder/includes/functions.php 2322

And /var/log/apache2/error.log is:
[Thu May 17 11:06:06 2012] [error] [client 192.168.0.101] ERR [socket_sendto( /tmp/zms-081287s.sock ) failed: No such file or directory], referer: https://???/zm/index.php?view=watch&mid=9

[TylerSchwend]

Downgrading PHP and Apache to Debian testing levels did not correct this for me.

[TylerSchwend]

Another user:

http://www.zoneminder.com/forums/viewto ... 29&t=19268

[TylerSchwend]

A development! I uninstalled and purged my zoneminder installation. I added one monitor back...

With the default settings, ZoneMinder doesn't use Cambozola, and instead tries to just return JPG in the video view... Well, it was returning a broken image. Which I saved... When I looked at the file, I noticed it had an ELF header... When I run this as an executable, I get:

self@slipgate:/home/self# ./nph-zms.jpg
HTTP/1.0 200 OK
Server: ZoneMinder Video Server/1.25.0
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Last-Modified: Tue, 12 Jun 2012 18:13:54 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache

So... something in zoneminder is passing through the contents of the actual executable, rather than fetching what the executable is returning... I'm looking into this...

[TylerSchwend]

So far... The image stream for a single image is supposed to be:

https://myserver/cgi-bin/nph-zms?mode=s ... 9525437903

But calling that cgi-bin is actually returning the contents of the file, Apache isn't running anything, it's just passing it along. In my case this is because, for some reason, it's because my Apache2 config did not have the cgi-bin folder defined in the ScriptAlias directive.

This fixed all of my problems. I don't know if this got broke because of something I did or the last wave of Debian updates that I applied. But, voila.