Page 1 of 1

socket_bind( /tmp/zm/zms-931145w.sock ) failed: No such file

Posted: Mon Oct 08, 2012 9:20 am
by hk_niko
socket_bind( /tmp/zm/zms-931145w.sock ) failed: No such file or directory

this is the WAR in the log into my zm system...

can someone help me?

Regards

Re: socket_bind( /tmp/zm/zms-931145w.sock ) failed: No such

Posted: Mon Oct 15, 2012 5:51 pm
by monex
Hi,

in many cases this is a subsequent error. You should look at you logs before this warning/error occurs. I could remember that this error occurred when authentication didn't work (wrong time zone in php5.ini). maybe here it is something similar.

Hope this helps

Re: socket_bind( /tmp/zm/zms-931145w.sock ) failed: No such

Posted: Tue Oct 16, 2012 1:38 pm
by SpikeyGG
hk_niko wrote:socket_bind( /tmp/zm/zms-931145w.sock ) failed: No such file or directory
I have this same problem on my setup, along with other failures.

Subscribed...

Re: socket_bind( /tmp/zm/zms-931145w.sock ) failed: No such

Posted: Tue Oct 16, 2012 9:17 pm
by danno
hk_niko did you get past this? i have a similar error

Code: Select all

2012-10-17 07:23:59.919517	web_php	10552	ERR	socket_sendto( /tmp/zm/zms-244077s.sock ) failed: No such file or directory	/usr/share/zoneminder/includes/functions.php	2322
the error is accurate... there is no file named zms-244077s.sock at that location, only zmdc.sock.

I don't think it is a timezone issue, the system tzdata is correctly configured and php.ini uses the defaults (system?).

I do have one warning in the logs that looks ominous

Code: Select all

2012-10-17 07:11:39.790377	zmu	10113	WAR	Shared data not initialised by capture daemon, some query functions may not be available or produce invalid results	zm_monitor.cpp	439
I have set up 2 cameras (AXIS M3004) for testing with the same config in both, the first works as expected, the second does not show an image when mpeg is selected as stream type, works with jpeg.

My system is debian wheezy - zm 1.25.03 from repository

for what its worth the machine is an openVZ container running on the proxmox hypervisor allocated 2 cores and 4G ram.