User avatar
phbcanada
Posts: 16
Joined: Tue Dec 11, 2012 1:16 pm

segmentation fault running motion

Sun Feb 23, 2020 2:50 pm

Been trying to setup motion to monitor IP cameras. Have the config all setup according to various instructions but at some point the process just stops and the daemon is no longer running. Tried turning off daemon mode and running from shell and it shows:

Code: Select all

[23651976:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[23651976:motion] [NTC] [ALL] motion_startup: Motion 4.1.1 Started
[23651976:motion] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion/motion.log)
Segmentation fault
The tail end of the log file has:

Code: Select all

[0:motion] [NTC] [ALL] [Feb 23 09:37:34] main: Camera ID: 0 is from /etc/motion/motion.conf
[0:motion] [NTC] [ALL] [Feb 23 09:37:34] main: Camera ID: 0 Camera Name: (null) Service: rtsp:
[0:motion] [NTC] [ALL] [Feb 23 09:37:34] main: Stream port 8081
[0:motion] [NTC] [ALL] [Feb 23 09:37:34] main: Waiting for threads to finish, pid: 1155
[1:ml1] [NTC] [ALL] [Feb 23 09:37:34] motion_init: Camera 0 started: motion detection Enabled
[1:ml1] [NTC] [VID] [Feb 23 09:37:34] vid_start: Opening Netcam RTSP
[0:wc0] [NTC] [STR] [Feb 23 09:37:34] http_bindsock: listening on any IPv4 address port 8080
[0:wc0] [NTC] [STR] [Feb 23 09:37:34] httpd_run: Started motion-httpd server on port 8080 (auth Disabled)
Any suggestions? I saw one post somewhere that motion is not reliable anyway. Perhaps I should just find an alternative?

sora03
Posts: 250
Joined: Mon Dec 29, 2014 4:11 pm
Location: Philippines
Contact: Website YouTube

Re: segmentation fault running motion

Wed Feb 26, 2020 2:58 am

phbcanada wrote:
Sun Feb 23, 2020 2:50 pm
Been trying to setup motion to monitor IP cameras. Have the config all setup according to various instructions but at some point the process just stops and the daemon is no longer running. Tried turning off daemon mode and running from shell and it shows:

Code: Select all

[23651976:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[23651976:motion] [NTC] [ALL] motion_startup: Motion 4.1.1 Started
[23651976:motion] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion/motion.log)
Segmentation fault
The tail end of the log file has:

Code: Select all

[0:motion] [NTC] [ALL] [Feb 23 09:37:34] main: Camera ID: 0 is from /etc/motion/motion.conf
[0:motion] [NTC] [ALL] [Feb 23 09:37:34] main: Camera ID: 0 Camera Name: (null) Service: rtsp:
[0:motion] [NTC] [ALL] [Feb 23 09:37:34] main: Stream port 8081
[0:motion] [NTC] [ALL] [Feb 23 09:37:34] main: Waiting for threads to finish, pid: 1155
[1:ml1] [NTC] [ALL] [Feb 23 09:37:34] motion_init: Camera 0 started: motion detection Enabled
[1:ml1] [NTC] [VID] [Feb 23 09:37:34] vid_start: Opening Netcam RTSP
[0:wc0] [NTC] [STR] [Feb 23 09:37:34] http_bindsock: listening on any IPv4 address port 8080
[0:wc0] [NTC] [STR] [Feb 23 09:37:34] httpd_run: Started motion-httpd server on port 8080 (auth Disabled)
Any suggestions? I saw one post somewhere that motion is not reliable anyway. Perhaps I should just find an alternative?
where did you get the motion? is it in the debian packages?
I used the one from the official motion's git releases for it to work.
Just download the deb package from motion's github account: https://github.com/Motion-Project/motion/releases

If you are using the latest raspbian select the buster package.
You can install it using

Code: Select all

 $ sudo dpkg -i ./motion-buster.deb
Be sure to remove the currently installed motion:

Code: Select all

$ sudo apt remove motion
Mastodon: https://mastodon.social/@ssora

Return to “Advanced users”