BUG: accept(): Socket operation on non-socket

Motion Restart Mon Aug 1 09:14:33 EDT 2005
Motion running as daemon process
Thread 1 is from thread1.conf
Thread 2 is from thread2.conf
Thread 1 started
Thread 2 started
Thread 3 is the camera handler for thread 1
Thread 4 is the camera handler for thread 2
[1] accept(): Socket operation on non-socket
[2] accept(): Socket operation on non-socket
[1] accept(): Socket operation on non-socket
[2] accept(): Socket operation on non-socket

It says the 2 accept() lines forever until I kill it.

I have an Axis 2400 camera server and motion is looking at 2 cameras using mjpeg streaming.

Please let me know what other information you need and I will get it to you.

Test case

Environment

Motion version:	3.2.2_snap8
ffmpeg version:	0.4.9-0.lvn.0.17.20050427.4
Shared libraries:	ffmpeg
Server OS:	Fedora Core 4, kernel 2.6.12-1.1398_FC4

-- TWikiGuest - 01 Aug 2005

Follow up

Them problem seems to come from webcam.c: http_acceptsock().

How did you restart motion ?

from http web interface ? from console sending a signal ?

Because i think that could be the problem , but i would like to be sure.

-- AngelCarpintero - 01 Aug 2005

---

More Info

I have just upgraded to motion-3.2.2-snap8 (I was running motion-3.2.2-snap4) and I am getting the same socket opperation messages issued although with slighlty different accompanying messages.

Processing thead 0 - config file /usr/local/etc/motion.conf
Processing config file /usr/local/etc/thread1.conf
Processing config file /usr/local/etc/thread2.conf
Motion running as daemon process
Thread 1 is from /usr/local/etc/thread1.conf
Thread 2 is from /usr/local/etc/thread2.conf
Thread 1 started
Thread 2 started
motion-hhtpd/3.2.2 running, accepting connections
[2] accept(): Socket operation on non-socket
[1] accept(): Socket operation on non-socket
[2] accept(): Socket operation on non-socket
[1] accept(): Socket operation on non-socket
[2] accept(): Socket operation on non-socket
.
.

I am running two Axis 205 cameras on a LinuxFromScratch installation. motion was started with the same config files that I was running for v3.2.2-snap4. motion was not running when the new version was started. motion was started from the command line by just typing "motion"

Everything was running smoothly on snap 4.

While the messages are being issued motion can still be detected and jpgs are output.

If there's something more I can tell you let me know.

(I've had to regress back to snap 4 for the time being since I don't want to fill me little disk. However I'd be happy run a newer version or debug version under controlled conditions should you require it).

-- TheSpike 01 Aug 2005

---

Strange that error for both ... could you attach the motion.conf , thread1.conf and thread2.conf ?

I've tried to reproduce the error but i can't.

-- AngelCarpintero - 01 Aug 2005

---

Your problem is not related to netcam.

You probably have the same webcam port defined for the two cameras. And you may even have chosen both to be the same as the control port.

All 3 must be unique.

Motion is supposed to run with the webcam disabled but this seems to fail so there is a bug to be fixed.

Fix record

I have found the bug that makes Motion try to accept a non existing socket.

It is fixed and fix will be in 3.2.2_snap9

-- KennethLavrsen - 02 Aug 2005