FreeBSD 5.3-STABLE + Netcam 3x Axion 2110 = Motion Crash
Question
Hello
I've got problem with Motion.
I've got 3 netcameras Axion 2110.
It breaks after few minutes. It looks like this:
1) For a first ~60 sec all is ok:lock
File of type 1 saved to: /home/camera/files/cam3/02-20050324143446-01.jpg
File of type 1 saved to: /home/camera/files/cam2/02-20050324143514-00.jpg
2) After that time:
File of type 1 saved to: /home/camera/files/cam2/02-20050324143516-01.jpg
Thread 1 Condiction timeout
File of type 1 saved to: /home/camera/files/cam2/02-20050324143517-00.jpg
File of type 1 saved to: /home/camera/files/cam3/03-20050324143520-01.jpg
Thread 1 Condiction timeout
File of type 1 saved to: /home/camera/files/cam3/03-20050324143524-00.jpg
3) And at last (in this case you can see that thread 2 is alive but sometimes survives other one):
Thread 3 Condiction timeout
Thread 1 Condiction timeout
Thread 3 Condiction timeout
Thread 1 Condiction timeout
Thread 3 Condiction timeout
Thread 1 Condiction timeout
Thread 3 Condiction timeout
4) When I try to stop it looks like this:
^CThread 2 exiting
Netcam: thread 2: Exiting
Thread 1 exiting
Thread 3 exiting
... and it whant to stop at all.
I need to do "kill -9 PID"
During this short run of Motion file motion.core (size ~24 MB) is created.
Should I use version 3.2.XX ??
Environment
Motion version: |
3.1.19 |
ffmpeg version: |
0.4.8_5 |
Libraries: |
curl, ffmpeg, mysql |
Server OS: |
FreeBSD 5.3-STABLE |
--
TWikiGuest - 24 Mar 2005
Answer
The netcam stability seems to be much better in the 3.2.1 development release, particularly after 3.2.1-snap5 when the new netcam patches went in. I believe there are a couple race conditions when closing motion that I will have to deal with, but the cleanup code is now unified and simpler to debug.
If you don't mind trying a development version, I'd strongly suggest at least giving
MotionRelease3x2x1snap7 a try and post any issues you have with the netcam driver at
NetcamStabilityPatch. Personally, I've been running with my latest patches as they are developed and have only had a single lockup in the last week. Of course, YMMV.
Note that I do plan on backporting the patches to the 3.1.19 released version (possibly for inclusion in a 3.1.20 bugfix version), but my priority is to get 3.2.1 more stable first. Patches may be available as early as this weekend.
--
ChristopherPrice - 24 Mar 2005
The 3.2.1_snap7 may not run well on
FreeBSD. The setup mode code may have broken some
FreeBSD code. Since
AngelCarpintero is the only active developer that has
FreeBSD and wrote the
FreeBSD part of the Motion code, we are waiting for him to come to our rescue and hopefully fix things. Other are welcome to give a hand also.
--
KennethLavrsen - 24 Mar 2005