problems with timelaps

Question

strange problems with timelaps feature (which worked, I don't know which changes caused the problems). At exactly 00:00 I have the following syslog entry:

Mar  8 23:59:01 wormhole2 /usr/sbin/cron[13412]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Mar  9 00:00:00 wormhole2 motion: [3] avcodec_open - could not open codec: Connection reset by peer
Mar  9 00:00:00 wormhole2 motion: [2] avcodec_open - could not open codec: Connection reset by peer
Mar  9 00:00:00 wormhole2 motion: [2] ffopen_open error creating file [/home/vipsysteme/deployment/Amthor/etc/WebCam/Events/2006/03/09/cam1-timelapse.mpg]: Connection reset by peer
Mar  9 00:00:00 wormhole2 motion: [1] avcodec_open - could not open codec: File exists
Mar  9 00:00:00 wormhole2 motion: [1] ffopen_open error creating file [/home/vipsysteme/deployment/Amthor/etc/WebCam/Events/2006/03/09/cam0-timelapse.mpg]: File exists

and motion crashes/stops. The access rights on the dirs are o.k. and the dirs are all there! What is the "connection reset by peer" ?

Environment

Motion version:	3.2.4
ffmpeg version:	0.4.9pre1
Libraries:	ffmpeg, mysql, postgresql
Server OS:	SuSE 9 Linix

-- AxelAmthor - 09 Mar 2006

Answer

Please post your motion.conf

Just attach it

-- KennethLavrsen - 09 Mar 2006

Answer

• list.htm: motion conf

• list0.htm: thread 1 conf

• list1.htm: thread 2 conf

• list2.htm: thread 3 conf

-- AxelAmthor - 09 Mar 2006

Looks OK.

Can you perhaps try the latest daily snap release MotionDailySourceSnap

-- KennethLavrsen - 09 Mar 2006

Comment

I was seeing something like this, it was then i found out about the keyword change from ffmpeg to movie _filename!

-- TheOtherBug - 10 Mar 2006

So did upgrading work?

-- KennethLavrsen - 10 Mar 2006

I think the last question is for Axel ?

I am still running with a old snapshot of 20051224 becaurse the latest version don't seem to like a single frame error , http://www.lavrsen.dk/twiki/bin/view/Motion/BugReport2006x03x10x000151

In my chase for find out where that bug begin i have noticed that this error will/can be seen when switching between versions where keyword changes between ffmpeg_filename and movie_filename, not sure why as this keyword should not have to do with the timelapse_filename, maybe it only happen when i forget to correct the keyword - i don't know what motion does when it get down to the 'unknown keyword'.

-- TheOtherBug - 14 Mar 2006

Please try to reproduce your problem with lastest stable version 3.2.7 , reopen the support question if problem still remains.

-- AngelCarpintero - 22 Nov 2006