BUG: Loop at Motion start

What could be the reason, for a loop in motion whenever started by "/etc/init.d/motion start" ?

Actually I have done a several motion installations so far with very few problems. This time it seems different. Although I use only one single Axis 206 camera, which is described and handled within a thread file, it looks as if there is a loop in the start routine of motion. I have included an excerpt of the error messages taken from the /var/log/messages file below. The loop cycle time is quite short - approximately one per second or so. No vids have been recorded by motion yet.

Has somebody already experienced this or discovered a similar occurrence?

tail -f /var/log/messages
Nov  5 10:44:25 sosobserve-desktop motion: [0] Motion thread 1 restart
Nov  5 10:44:25 sosobserve-desktop motion: [1] Resizing pre_capture buffer to 1 items
Nov  5 10:44:25 sosobserve-desktop motion: [1] netcam camera handler: finish set, exiting
Nov  5 10:44:26 sosobserve-desktop motion: [0] Motion thread 1 restart
Nov  5 10:44:26 sosobserve-desktop motion: [1] Resizing pre_capture buffer to 1 items
Nov  5 10:44:26 sosobserve-desktop motion: [1] netcam camera handler: finish set, exiting
Nov  5 10:44:27 sosobserve-desktop motion: [0] Motion thread 1 restart
Nov  5 10:44:27 sosobserve-desktop motion: [1] Resizing pre_capture buffer to 1 items
Nov  5 10:44:27 sosobserve-desktop motion: [1] netcam camera handler: finish set, exiting
Nov  5 10:44:28 sosobserve-desktop motion: [0] Motion thread 1 restart
Nov  5 10:44:28 sosobserve-desktop motion: [1] Resizing pre_capture buffer to 1 items
Nov  5 10:44:28 sosobserve-desktop motion: [1] netcam camera handler: finish set, exiting
Nov  5 10:44:29 sosobserve-desktop motion: [0] Motion thread 1 restart
Nov  5 10:44:29 sosobserve-desktop motion: [1] Resizing pre_capture buffer to 1 items
Nov  5 10:44:29 sosobserve-desktop motion: [1] netcam camera handler: finish set, exiting
Nov  5 10:44:30 sosobserve-desktop motion: [0] Motion thread 1 restart
^C

Environment

Motion version:	3.2.11
ffmpeg version:	0.4.8
Shared libraries:	ffmpeg, postgresql
Server OS:	ubuntu (Easy Peasy)

-- SosobserveFranzGrubinger - 05 Nov 2010

Follow up

Fix record

********************************** Important Notice ************************************* After deeper analyses I was able to isolate the problem: reason for the loop was a wrong parameter in the PostgreSQL Client Authentication Configuration File /etc/postgresql/8.4/main/pg_hba.conf. After setting the METHOD parameters from "md5" to "trust" motion was starting as usual.

---

If you run motion with verbose mode for logs , are you able to see that DB problem !?

I think this kind of errors are logged at least in latest released version 3.2.12.

Cheers !

-- AngelCarpintero - 07 Nov 2010