socket_sendto failed: No such file or directory

[rodeored]

I'm seeing this error in my logs:
socket_sendto( /var/lib/zoneminder/sock/zms-441571s.sock ) failed: No such file or directory]

The internet says I should edit /etc/httpd/conf/httpd.conf
and comment out the line that reads:
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"

I did that but I'm still seeing the same error.
What is causing this problem and how do I fix it?

[TheKorn]

Are you getting that after viewing a monitor then immediately closing the browser tab while the stream is running? If so, that's normal. (Found out from experience that's why there is a close link on those tabs... closes things gracefully rather than abruptly, so that error message doesn't happen.)

[rodeored]

If I just leave the monitor open and click on "log" it shows that error every 40 seconds at 00 seconds then 20 then 40 then 00 etc
I adding the maximum debugging and now after every "Starting Capture"
After that is always "invalid response status 404 not found"
This is not a common error in zoneminder if google is any indication.
After that is always "unable to get response"

[TheKorn]

Let me guess... you're trying to view the output of a monitor that's not working yet in zoneminder?

[rodeored]

Yes. Sorry, I thought that was obvious. The monitor has a black box without any image. When I look at the logs, those are the errors I'm getting.

[TheKorn]

C'mon man, first things first. There is no data to send to display, which is normally an error but in your case is accurate because the monitor itself isn't functional!

[rodeored]

Code: Select all

monitor itself isn't functional

Can you be more specific?
I don't know what that means.

What's the difference between a monitor that's working and a monitor that's not working? I mean besides the fact that the image is not there.

[TheKorn]

What's the difference between a monitor that's working and a monitor that's not working? I mean besides the fact that the image is not there.

That is the difference! You're asking zm to display a picture (video) that doesn't exist as it was never collected in the first place. "What's on page 12?" isn't a valid question if the book hasn't been written.

The way to tell is to look at the color of the monitor line. Red indicates an error condition. For example, my patio camera is on the fritz so I have it turned off in zoneminder, and that line is red.

Untitled-1.png (47.53 KiB) Viewed 4769 times

If I had simply unplugged it without turning it off in zoneminder, it'd still be red and I could attempt to view a live image. In that case I'd get similar errors as you.

In short, don't worry about those messages until/unless you get the camera working in zoneminder first. You're chasing a symptom, not a cause.

[rodeored]

Well ok, thanks. But I am completely stumped as to how to get the camera working in zoneminder. What else can I check?

[rodeored]

I just wanted to add what I've seen about this particular error to this thread.
It happens whenever is in the host path field cannot be reached.
You may see this error occasionally even when the camera is working if it returns nothing or a bad frame.
If the host path is wrong, you will see this message over and over again.
Here is a page that shows the protocols and host paths for each camera which I found very usefull.
http://www.ispyconnect.com/sources.aspx