Motion - Bug Report 2008x 02x 18x 222143
You are here: Foswiki>Motion Web>BugReports>BugReport2008x02x18x222143 (20 Feb 2008, DanielHolm)Edit Attach

BUG: Stop answering.

After an hour or so, Motion stop answering. The HTTP daemon doesnt work, no more motion pictures or snapshots are taken. Then when I kill the process I have to reboot the computer beacause "that cam is used by another process".

This is what happens:

1. I start the motion process:

daniel@holmen-server:~$ sudo motion -n
[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Motion 3.2.9 Started
[0] ffmpeg LIBAVCODEC_BUILD 3352064 LIBAVFORMAT_BUILD 3344896
[0] Thread 1 is from /etc/motion/motion.conf
[1] Thread 1 started
[0] motion-httpd/3.2.9 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 9000
[1] Not a V4L2 device?
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] Started stream webcam server in port 9001

2. It takes a few pictures:

[1] File of type 2 saved to: /var/www/cam/01-20080220162500-snapshot.jpg
[1] File of type 8 saved to: /var/www/cam/01-20080220162525.avi
[1] File of type 1 saved to: /var/www/cam/01-20080220162525-02.jpg
[1] File of type 1 saved to: /var/www/cam/01-20080220162526-00.jpg
[1] File of type 1 saved to: /var/www/cam/01-20080220162529-02.jpg
[1] File of type 1 saved to: /var/www/cam/01-20080220162530-01.jpg

3. And then, nothing more.

My Config is attached.

Thanks.

 *Webcam:*
daniel@holmen-server:~$ lsusb | grep -i cam
Bus 001 Device 002: ID 046d:0921 Logitech, Inc. Labtec WebCam
 
*dmesg*
[   39.200000] /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-server/media/gspcav1/gspca_core.c: USB SPCA5xx camera found. (TV8532)
[   39.290000] usbcore: registered new interface driver gspca
[   39.290000] /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-server/media/gspcav1/gspca_core.c: gspca driver 01.00.12 registered
 
*
After a kill:*
daniel@holmen-server:~$ sudo motion -n
[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Processing config file /etc/motion/thread0.conf
[1] Thread is from /etc/motion/thread0.conf
[1] Thread started
[1] Failed to open video device /dev/video0: Device or resource busy
[1] Motion Exits
*
The last two rows of output from Motions when it freezes or stop answering:*
[1] File of type 2 saved to: /home/daniel/cam/06-20080218225500-snapshot.jpg
[1] File of type 2 saved to: /home/daniel/cam/06-20080218230000-snapshot.jpg

Environment

Motion version: 3.2.9
ffmpeg version:  
Shared libraries: ffmpeg, mysql,
Server OS: Ubuntu 7.10 Gutsy Gibbon

-- DanielHolm - 18 Feb 2008

Follow up

Why do you use such an old version of Motion? Noone will try to fix or persue a bug in a version which is several years old. First thing you should have done is to upgrade.

-- KennethLavrsen - 19 Feb 2008

Upgraded to 3.2.9 - same problem.

-- Main.Daniel Holm - 20 Feb 2008


Daniel please very hard to guess your problem without any information , no logs files , no message from syslog , no config file that you are using , no

device you are using to capture from , no version driver ... :-/

Please give us some clue ... or nobody will be able to figure out what's your problem .

-- AngelCarpintero - 20 Feb 2008

Edited the text a bit more ad attached my config file. Addes the cam.

-- DanielHolm - 20 Feb 2008


Daniel that really bring some lights to me ... the problem seems related to your webcam driver :
gspca

It should support V4L2 , but i think that it doesn't or have some bug , maybe you need to load your module with some parameter.

-- AngelCarpintero - 20 Feb 2008


But why does it work an hour, and nothing more? It work flawlessly when it does.

-- DanielHolm - 20 Feb 2008.

Fix record

Topic revision: r7 - 20 Feb 2008, DanielHolm
Copyright © 1999-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Please do not email Kenneth for support questions (read why). Use the Support Requests page or join the Mailing List.
This website only use harmless session cookies. See Cookie Policy for details. By using this website you accept the use of these cookies.