BUG: Netcam reconnects floods syslog
Filed by Kenneth Lavrsen for Dick Middleton
I run a couple of network cameras which I switch off at night. Every 10s or so I get messages like this in syslog:
Apr 8 00:08:43 motion: [2] connect returned error
Apr 8 00:08:43 motion: [2] re-opening camera (non-streaming)
I suppose that's understandable although not ideal. I think if the connection fails only the first failed message is interesting.
However when the cameras are started or if the network is distrupted I get these messages a gazillion times per second ( 1 gazillion ~= 20
) - like motion is just looping on the open call.
Is there some way to suppress these messages?
Dick
Test case
Environment
Motion version: |
3.2.6 |
ffmpeg version: |
|
Shared libraries: |
ffmpeg, mysql, postgresql |
Server OS: |
|
--
KennethLavrsen - 11 Apr 2006
Follow up
Comment:
I have just seen this in my test of
http://www.lavrsen.dk/twiki/bin/view/Motion/BugReport2006x03x10x000151 .
Still not knowing much of the 'heart' of motion i think a solution could be to set set a flag efter the message 'Video signal lost - Adding grey image' and the not sending more messages to the log from that thread until clearing the flag and writing the 'Video signal re-acquired'.
--
TheOtherBug - 16 Apr 2006
Fix record
I added a little code to reduce the excessive log messages (log when connection is first lost, then log again when connection is re-established). The changes (netcam.c) have been committed to the svn repository, and will show up in the next daily snapshot.
--
BillBrack - 16 Apr 2006
That looks allright to me, just testet it.
--
TheOtherBug - 17 Apr 2006
In 3.2.7
--
KennethLavrsen - 20 Oct 2006