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. motion crashing or stops working (S Andreason)
----------------------------------------------------------------------
Message: 1
Date: Tue, 8 Dec 2020 12:57:13 -0800
From: S Andreason <sandrea...@gmail.com>
To: Motion-user <motion-user@lists.sourceforge.net>
Subject: [Motion-user] motion crashing or stops working
Message-ID: <dc2a1bb7-e010-893d-54a1-09deb31f6...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi everyone,
I have been seeing motion both fail to start up at power up, and crash
after successfully running. This morning it did both.
It also runs perfectly for days, without any change to config files. The
only clue I have so far, is it only happens to the config/setup with 2
cameras. The other Pi with identical software, is only monitoring one
netcam.
So do you see anything about my config files that's not quite perfect?
Hardware is Pi 4B
Linux version 5.4.72-v7l+ (Ubuntu 9.3.0-17ubuntu1~20.04)
Motion-4.3.2
config files are unchanged from my last share of them, here they are again:
http://seahorsecorral.org/videos/tests/motion.conf
http://seahorsecorral.org/videos/tests/camera203.conf
http://seahorsecorral.org/videos/tests/camera204.conf
Today was unusually broken, so I've captured the log files and what I did:
This morning it booted up at 06:05, the clock (21:30) got updated 8
seconds later.
There was 3 motion events, the mp4 files look good, then at 06:49 the
screenshot.jpg file was updated, configured for every 60 seconds.
Then there was no further activity.
I noticed at 07:20 it had stopped working, so logged in to investigate.
Log files looked normal. All indications are the program is running,
except not in the process list, and not responding to calls to port 8080.
$ sudo service motion status
? motion.service - LSB: Start Motion detection
Loaded: loaded (/etc/init.d/motion; generated)
Active: active (exited) since Mon 2020-12-07 21:30:06 PST; 9h ago
Docs: man:systemd-sysv-generator(8)
Process: 304 ExecStart=/etc/init.d/motion start (code=exited,
status=0/SUCCESS)
Dec 07 21:30:05 raspberrypi1 systemd[1]: Starting LSB: Start Motion
detection...
Dec 07 21:30:06 raspberrypi1 motion[304]: Starting motion detection
daemon: motion.
Dec 07 21:30:06 raspberrypi1 systemd[1]: Started LSB: Start Motion
detection.
Dec 07 21:30:08 raspberrypi1 motion[461]: [0:motion] [NTC] [ALL]
conf_load: Processing thread 0 - config file /etc/motion/motion.conf
Dec 07 21:30:08 raspberrypi1 motion[461]: [0:motion] [NTC] [ALL]
config_camera: Processing camera config file /etc/motion/camera203.conf
Dec 07 21:30:08 raspberrypi1 motion[461]: [0:motion] [NTC] [ALL]
config_camera: Processing camera config file /etc/motion/camera204.conf
Dec 07 21:30:08 raspberrypi1 motion[461]: [0:motion] [NTC] [ALL]
motion_startup: Logging to file (/var/log/motion/motion.log)
$ cat /var/log/motion/motion.log saved for you at:
http://seahorsecorral.org/videos/tests/motion.log.20201208.txt
See at 07:21:05 I attempted the first restart
$ sudo service motion restart
I was not satisfied with the result, so I edited motion.conf to up the
log level back up to 7
$ sudo service motion restart
See it starts at 07:21:28
and all indications are that it is working, but it is not. motion is not
in the process list, and I can't see any indications of how it crashed
(again).
I have seen this before, where a straight restart does not work, but
separating into stop and start does.
$ sudo service motion stop
$ sudo service motion start
07:22:56
This time it is working. I included some events to show that.
The log file lines look the same to me, with one exception:
image_ring_resize: Resizing pre_capture buffer
Any ideas?
Stewart
------------------------------
------------------------------
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 174, Issue 2
*******************************************
