Send Motion-user mailing list submissions to
        motion-user@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
        motion-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
        motion-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Re: Camera stops and needs a reset (craig bowser)


----------------------------------------------------------------------

Message: 1
Date: Thu, 21 Jan 2021 18:44:43 -0500
From: craig bowser <reswo...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Camera stops and needs a reset
Message-ID:
        <CADq7+KAMJ840S7EcK+1mBiGyB6+2u_Dc7tav31EDpCEd4H=z...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I posted here and this ended up being the solution:

https://raspberrypi.stackexchange.com/questions/120411/raspberry-pi-crontab-wont-restart-service/120417#120417

Craig L Bowser
____________________________

This email is measured by size.  Bits and bytes may have settled during
transport.


On Tue, Jan 19, 2021 at 7:55 PM craig bowser <reswo...@gmail.com> wrote:

> OK, crontab should be 0 */2 * * *
>
> Trying that
>
> Craig L Bowser
> ____________________________
>
> This email is measured by size.  Bits and bytes may have settled during
> transport.
>
>
> On Tue, Jan 19, 2021 at 7:50 PM craig bowser <reswo...@gmail.com> wrote:
>
>> OK, answers inline
>>
>> Could it be the camera?  The log seems to indicate the video stream stops
>> and this triggers motion's shutdown. Can you swap cameras with the working
>> system and the problem system and see if the random shutdowns move to the
>> other system.  ------ Unfortunately, this is a fix of last resort.  The
>> outdoor camera is sealed so I can't get to the pi or the camera.  It's only
>> caulk so it won't be horrible to remove, but want to try other things first.
>>
>> Is the camera and or Pi's power supply stable? Brownouts maybe affecting
>> either or both components.  --- power is stable.  power is plugged into an
>> outlet using approved power cable.
>>
>> Does a motion daemon restart postpone the crash ? If so a cronjob to
>> restart the camera at an appropriate time may help.  I need to troubleshoot
>> the cronjob I set up.  It doesn't seem to be running * */2 * * * should be
>> running every two hours, but is not.  configured using crontab -e as
>> root.
>>
>> So I'm troubleshooting that....  Will post update soon....
>>
>> Craig L Bowser
>> ____________________________
>>
>> This email is measured by size.  Bits and bytes may have settled during
>> transport.
>>
>>
>> On Sun, Jan 17, 2021 at 1:16 PM John Vaccaro <jvacc...@gmail.com> wrote:
>>
>>> Could it be the camera?  The log seems to indicate the video stream
>>> stops and this triggers motion's shutdown. Can you swap cameras with the
>>> working system and the problem system and see if the random shutdowns move
>>> to the other system.
>>>
>>> Is the camera and or Pi's power supply stable? Brownouts maybe affecting
>>> either or both components.
>>>
>>> Does a motion daemon restart postpone the crash ? If so a cronjob to
>>> restart the camera at an appropriate time may help.
>>>
>>> Regards....
>>>
>>> John Vaccaro
>>> ----------------------
>>> You are the product of four billion years of evolutionary  success. Act
>>> like it!
>>>
>>> On Sat, Jan 16, 2021, 8:14 PM craig bowser <reswo...@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> I've got a raspberry pi 3 running motion.  It's in a waterproof case
>>>> watching the front door.  Most of the time it works just fine, but every
>>>> once in a while the camera just stops.
>>>> simply restarting the service gets things going again, but not sure
>>>> what is happening.
>>>>
>>>> The set up is the same as the one I have in the garage and that one has
>>>> no problems and never stops.
>>>>
>>>> Here is a sample from the log of the one that stops:
>>>>
>>>> [1:ml1] [NTC] [ALL] [Jan 16 16:47:41] motion_detected: Motion detected
>>>> - starting event 64
>>>> [1:ml1] [NTC] [ALL] [Jan 16 16:48:40] preview_save: different filename
>>>> or picture only!
>>>> [1:ml1] [NTC] [EVT] [Jan 16 16:48:40] event_newfile: File of type 1
>>>> saved to: /media/cctv/Camera1-FrontDoor/64-20210116164741-00.jpg
>>>> [1:ml1] [NTC] [ALL] [Jan 16 16:48:40] motion_loop: End of event 64
>>>> [1:ml1] [NTC] [EVT] [Jan 16 16:53:40] event_new_video Source FPS 2
>>>> [1:ml1] [NTC] [ENC] [Jan 16 16:53:40] ffmpeg_open Selected Output FPS 2
>>>> [1:ml1] [NTC] [ENC] [Jan 16 16:53:40] ffmpeg_avcodec_log: Using
>>>> AVStream.codec to pass codec parameters to muxers is deprecated, use
>>>> AVStream.codecpar instead.
>>>> [1:ml1] [NTC] [EVT] [Jan 16 16:53:40] event_newfile: File of type 8
>>>> saved to: /media/cctv/Camera1-FrontDoor/65-20210116165339.avi
>>>> [1:ml1] [NTC] [ALL] [Jan 16 16:53:40] motion_detected: Motion detected
>>>> - starting event 65
>>>> [1:ml1] [NTC] [ALL] [Jan 16 16:54:39] preview_save: different filename
>>>> or picture only!
>>>> [1:ml1] [NTC] [EVT] [Jan 16 16:54:39] event_newfile: File of type 1
>>>> saved to: /media/cctv/Camera1-FrontDoor/65-20210116165339-01.jpg
>>>> [1:ml1] [NTC] [ALL] [Jan 16 16:54:39] motion_loop: End of event 65
>>>> [1:ml1] [NTC] [EVT] [Jan 16 16:55:32] event_new_video Source FPS 2
>>>> [1:ml1] [NTC] [ENC] [Jan 16 16:55:32] ffmpeg_open Selected Output FPS 2
>>>> [1:ml1] [NTC] [ENC] [Jan 16 16:55:32] ffmpeg_avcodec_log: Using
>>>> AVStream.codec to pass codec parameters to muxers is deprecated, use
>>>> AVStream.codecpar instead.
>>>> [1:ml1] [NTC] [EVT] [Jan 16 16:55:32] event_newfile: File of type 8
>>>> saved to: /media/cctv/Camera1-FrontDoor/66-20210116165531.avi
>>>> [1:ml1] [NTC] [ALL] [Jan 16 16:55:32] motion_detected: Motion detected
>>>> - starting event 66
>>>> [1:ml1] [NTC] [ALL] [Jan 16 16:56:31] preview_save: different filename
>>>> or picture only!
>>>> [1:ml1] [NTC] [EVT] [Jan 16 16:56:31] event_newfile: File of type 1
>>>> saved to: /media/cctv/Camera1-FrontDoor/66-20210116165532-00.jpg
>>>>
>>>> *[1:ml1] [NTC] [ALL] [Jan 16 16:56:31] motion_loop: End of event
>>>> 66[1:ml1] [NTC] [ALL] [Jan 16 19:54:57] motion_loop: End of event 67*
>>>> [0:web_control] [NTC] [STR] [Jan 16 19:54:57] httpd_run: motion-httpd -
>>>> Finishing
>>>> [0:web_control] [NTC] [STR] [Jan 16 19:54:57] httpd_run: motion-httpd
>>>> Closing
>>>> [0:web_control] [NTC] [STR] [Jan 16 19:54:57] motion_web_control:
>>>> motion-httpd thread exit
>>>> [1:ml1] [NTC] [ALL] [Jan 16 19:54:57] motion_loop: Thread exiting
>>>> [1:ml1] [NTC] [STR] [Jan 16 19:54:57] stream_stop: Closing
>>>> motion-stream listen socket & active motion-stream sockets
>>>> [1:ml1] [NTC] [STR] [Jan 16 19:54:57] stream_stop: Closed motion-stream
>>>> listen socket & active motion-stream sockets
>>>> [1:ml1] [NTC] [VID] [Jan 16 19:54:57] vid_close: Closing video device
>>>> /dev/video0
>>>> [0:motion] [NTC] [ALL] [Jan 16 19:54:58] main: Threads finished
>>>> [0:motion] [NTC] [ALL] [Jan 16 19:54:59] main: Motion terminating
>>>> [0:motion] [NTC] [ALL] [Jan 16 19:54:59] motion_remove_pid: Closing
>>>> logfile (/var/log/motion/motion.log).
>>>> [0:motion] [NTC] [ALL] [Jan 16 19:54:59] motion_startup: Using log type
>>>> (ALL) log level (NTC)
>>>> [0:motion] [NTC] [ENC] [Jan 16 19:54:59] ffmpeg_init: ffmpeg libavcodec
>>>> version 57.48.101 libavformat version 57.41.100
>>>> [0:motion] [NTC] [ALL] [Jan 16 19:54:59] main: Camera 0 is from
>>>> /etc/motion/motion.conf
>>>> [0:motion] [NTC] [ALL] [Jan 16 19:54:59] main: Camera 0 is device:
>>>> /dev/video0 input -1
>>>> [0:motion] [NTC] [ALL] [Jan 16 19:54:59] main: Stream port 8081
>>>> [0:motion] [NTC] [ALL] [Jan 16 19:54:59] main: Waiting for threads to
>>>> finish, pid: 31236
>>>> [1:ml1] [NTC] [ALL] [Jan 16 19:54:59] motion_init: Camera 0 started:
>>>> motion detection Enabled
>>>> [0:web_control] [NTC] [STR] [Jan 16 19:54:59] http_bindsock: listening
>>>> on 127.0.0.1 port 8080
>>>> [1:ml1] [NTC] [VID] [Jan 16 19:54:59] vid_v4lx_start: Using videodevice
>>>> /dev/video0 and input -1
>>>> [0:web_control] [NTC] [STR] [Jan 16 19:54:59] httpd_run: Started
>>>> motion-httpd server on port 8080 (auth Disabled)
>>>> ...... <restart sequence continues as normal>
>>>>
>>>> and from ealier
>>>>
>>>> [1:ml1] [NTC] [ALL] [Jan 16 09:52:06] motion_detected: Motion detected
>>>> - starting event 52
>>>> [1:ml1] [NTC] [ALL] [Jan 16 09:53:06] preview_save: different filename
>>>> or picture only!
>>>> [1:ml1] [NTC] [EVT] [Jan 16 09:53:06] event_newfile: File of type 1
>>>> saved to: /media/cctv/Camera1-FrontDoor/52-20210116095206-01.jpg
>>>> [1:ml1] [NTC] [ALL] [Jan 16 09:53:06] motion_loop: End of event 52
>>>> [1:ml1] [NTC] [EVT] [Jan 16 09:53:56] event_new_video Source FPS 2
>>>> [1:ml1] [NTC] [ENC] [Jan 16 09:53:56] ffmpeg_open Selected Output FPS 2
>>>> [1:ml1] [NTC] [ENC] [Jan 16 09:53:56] ffmpeg_avcodec_log: Using
>>>> AVStream.codec to pass codec parameters to muxers is deprecated, use
>>>> AVStream.codecpar instead.
>>>> [1:ml1] [NTC] [EVT] [Jan 16 09:53:56] event_newfile: File of type 8
>>>> saved to: /media/cctv/Camera1-FrontDoor/53-20210116095356.avi
>>>> [1:ml1] [NTC] [ALL] [Jan 16 09:53:56] motion_detected: Motion detected
>>>> - starting event 53
>>>> [1:ml1] [NTC] [ALL] [Jan 16 09:54:56] preview_save: different filename
>>>> or picture only!
>>>> [1:ml1] [NTC] [EVT] [Jan 16 09:54:56] event_newfile: File of type 1
>>>> saved to: /media/cctv/Camera1-FrontDoor/53-20210116095356-01.jpg
>>>>
>>>> *[1:ml1] [NTC] [ALL] [Jan 16 09:54:56] motion_loop: End of event
>>>> 53[1:ml1] [NTC] [ALL] [Jan 16 10:59:20] motion_loop: End of event 54*
>>>> [0:web_control] [NTC] [STR] [Jan 16 10:59:21] httpd_run: motion-httpd -
>>>> Finishing
>>>> [0:web_control] [NTC] [STR] [Jan 16 10:59:21] httpd_run: motion-httpd
>>>> Closing
>>>> [0:web_control] [NTC] [STR] [Jan 16 10:59:21] motion_web_control:
>>>> motion-httpd thread exit
>>>> [1:ml1] [NTC] [ALL] [Jan 16 10:59:21] motion_loop: Thread exiting
>>>> [1:ml1] [NTC] [STR] [Jan 16 10:59:21] stream_stop: Closing
>>>> motion-stream listen socket & active motion-stream sockets
>>>> [1:ml1] [NTC] [STR] [Jan 16 10:59:21] stream_stop: Closed motion-stream
>>>> listen socket & active motion-stream sockets
>>>> [1:ml1] [NTC] [VID] [Jan 16 10:59:21] vid_close: Closing video device
>>>> /dev/video0
>>>> [0:motion] [NTC] [ALL] [Jan 16 10:59:21] main: Threads finished
>>>> [0:motion] [NTC] [ALL] [Jan 16 10:59:22] main: Motion terminating
>>>> [0:motion] [NTC] [ALL] [Jan 16 10:59:22] motion_remove_pid: Closing
>>>> logfile (/var/log/motion/motion.log).
>>>> [0:motion] [NTC] [ALL] [Jan 16 10:59:23] motion_startup: Using log type
>>>> (ALL) log level (NTC)
>>>> [0:motion] [NTC] [ENC] [Jan 16 10:59:23] ffmpeg_init: ffmpeg libavcodec
>>>> version 57.48.101 libavformat version 57.41.100
>>>> [0:motion] [NTC] [ALL] [Jan 16 10:59:23] main: Camera 0 is from
>>>> /etc/motion/motion.conf
>>>> [0:motion] [NTC] [ALL] [Jan 16 10:59:23] main: Camera 0 is device:
>>>> /dev/video0 input -1
>>>> [0:motion] [NTC] [ALL] [Jan 16 10:59:23] main: Stream port 8081
>>>> [0:motion] [NTC] [ALL] [Jan 16 10:59:23] main: Waiting for threads to
>>>> finish, pid: 28603
>>>> [1:ml1] [NTC] [ALL] [Jan 16 10:59:23] motion_init: Camera 0 started:
>>>> motion detection Enabled
>>>> [0:web_control] [NTC] [STR] [Jan 16 10:59:23] http_bindsock: listening
>>>> on 127.0.0.1 port 8080
>>>> [1:ml1] [NTC] [VID] [Jan 16 10:59:23] vid_v4lx_start: Using videodevice
>>>> /dev/video0 and input -1
>>>> [0:web_control] [NTC] [STR] [Jan 16 10:59:23] httpd_run: Started
>>>> motion-httpd server on port 8080 (auth Disabled)
>>>>
>>>>
>>>> For some reason, when it stops, there are two End of Event entries
>>>> without a Starting event.  Are there any other troubleshooting tips to
>>>> figure out why this is happening?
>>>>
>>>> Thanks
>>>>
>>>> Craig L Bowser
>>>> ____________________________
>>>>
>>>> This email is measured by size.  Bits and bytes may have settled during
>>>> transport.
>>>> _______________________________________________
>>>> Motion-user mailing list
>>>> Motion-user@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>> https://motion-project.github.io/
>>>>
>>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>>
>>> _______________________________________________
>>> Motion-user mailing list
>>> Motion-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> https://motion-project.github.io/
>>>
>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 175, Issue 16
********************************************

Reply via email to