BUG: device stolen
I havent't modified a single element of my system in the last hours days(updated the wxwidget two days ago) and running motion for 11 days straight uninterrupted when, all of a sudden, today at 10 in the morning (i can tell from the logs) the process..... poofed all of a sudden
tried to restart it a few times (even rebooted the whole system fearing an usb issue) but that's it, it doesn't start.
Test case
[0] Motion running in setup mode.
[0] Thread device: /dev/video0 input 8
[0] Thread is from /usr/local/etc/motion.conf
[0] Waiting for threads to finish, pid: 1926
[1] Thread started
[1] Raw changes: 299 - changes after 'EedDl': 0 - labels: 0 - noise level: 19
[1] mcapture error in proc 1928: Connection timed out
[1] Video device fatal error - terminating camera thread
[1] Thread exiting
[1] Somebody stole the video device, lets hope we got his picture: Connection timed out
[0] Threads finished
[0] Motion terminating
Environment
Motion version: |
3.2.5.1 |
ffmpeg version: |
|
Shared libraries: |
ffmpeg, |
Server OS: |
slackware 10.2 |
--
AndreaDelPriore - 19 Mar 2006
Follow up
If you did not change anything then there is only one reason left. Your hardware is broken.
Happened to me too with cheap USB camera. Some of them are just too cheap.
I assume you cannot make the same camera work with any other program?
I am rejecting this. Reopen if my conclusions were wrong
Fix record