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. Question on file rollover (Erick Muis)
2. config file not being read on restart/reload? (somebody)
3. Re: config file not being read on restart/reload? (MrDave)
----------------------------------------------------------------------
Message: 1
Date: Wed, 3 Oct 2018 14:15:54 -0400
From: Erick Muis <erickm...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] Question on file rollover
Message-ID:
<CAKAwbFxHyqbB4C9cWnb2qjko=ucqo0y+z0u-i8_zlaxvdh7...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I've setup motion successfully and things are working great so far.
I did have a question on file rollover though. The problem I have is that
there does not appear to be a limit on how many files/images will be
created. So if I wanted to configure motion to start to remove older files
after say 24hours or a week for example. The ultimate goal being not
filling up my dropbox space with tons of picts when all I really want are
the last X amount of time.
It sounds like timelapse_mode has a feature for file rollover, however
based on the option name it sounds like timelapse_mode is mutually
exclusive to the motion detection. Am I reading that wrong? or is there
another option that I could possibly use?
Thanks,
Erick
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Wed, 3 Oct 2018 13:49:58 -0600
From: somebody <for...@n0sq.tech>
To: Motion-user@lists.sourceforge.net
Subject: [Motion-user] config file not being read on restart/reload?
Message-ID: <e6481f7e-1780-2af6-812e-c27fee6b7...@n0sq.tech>
Content-Type: text/plain; charset=utf-8
According to my screen, the restart or reload appears to be successful
but the config changes don't take effect. Only on a reboot do they take
effect. I can't see a problem with the reload or restart but the new
config doesn't get implemented. There are warnings and errors in syslog
but if these are a problem then why does a reboot work?
user@server1:~$ motion reload
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
/home/user/.motion/motion.conf
[0:motion] [NTC] [ALL] config_camera: Processing camera config file
.motion/camera1.conf
[0:motion] [NTC] [ALL] config_camera: Processing camera config file
.motion/camera2.conf
[0:motion] [NTC] [ALL] motion_startup: Logging to syslog
[0:motion] [NTC] [ALL] motion_startup: Motion 4.1.1+gitUNKNOWN Started
[0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
[0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
[0:motion] [NTC] [ALL] become_daemon: Motion going to daemon mode
Partial syslog output:
user@server1:~$ cat /var/log/syslog | grep motion | grep WRN
Oct? 3 13:43:30 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:30 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:30 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:40 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:40 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:40 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:40 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:50 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:50 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:50 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
Oct? 3 13:43:50 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
Retrying until successful connection with camera
user@server1:~$ cat /var/log/syslog | grep motion | grep ERR
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
v4l2_pixfmt_set: Error setting pixel format.#012VIDIOC_S_FMT: : Device
or resource busy
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
v4l2_pixfmt_select: Palette selection failed for format JPEG
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
v4l2_pixfmt_select: Unable to find a compatible palette format.
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID] vid_start:
V4L2 device failed to open
Oct? 3 13:45:50 server1 motion: [1:ml1:$$$$$] [ERR] [VID]
v4l2_input_select: Error selecting input 0 VIDIOC_S_INPUT: Device or
resource busy
Oct? 3 13:45:50 server1 motion: [1:ml1:$$$$$] [ERR] [VID] vid_start:
V4L2 device failed to open
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
v4l2_pixfmt_set: Error setting pixel format.#012VIDIOC_S_FMT: : Device
or resource busy
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
v4l2_pixfmt_set: Error setting pixel format.#012VIDIOC_S_FMT: : Device
or resource busy
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
v4l2_pixfmt_select: Palette selection failed for format JPEG
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
v4l2_pixfmt_select: Unable to find a compatible palette format.
Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID] vid_start:
V4L2 device failed to open
------------------------------
Message: 3
Date: Wed, 3 Oct 2018 18:57:05 -0600
From: MrDave <motionmrd...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] config file not being read on
restart/reload?
Message-ID: <fa90135d-6389-85f0-fbd3-0b595425a...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
I suspect the issue is with the first command of 'motion reload' There
is not any option of 'reload' so that command will just start another
process.? The syslog messages are indicating that the second process can
not open devices.? Presumably because the original process still has
control of them.
If you have the webcontrol interface active, you can restart via a web
browser or via a command line tool such as curl.? e.g.
curl {IP}:{port}/{camid}/action/restart
It is common to use a camid of zero to indicate to restart everything
rather than just restarting a particular camera.? If you do not have the
webcontrol activated, then you would need to kill any currently running
motion process and then just start motion again.
Additional information on the webcontrol / API options is in the guide.
https://rawgit.com/Motion-Project/motion/master/motion_config.html#OptDetail_Webcontrol
On 10/3/2018 1:49 PM, somebody wrote:
> According to my screen, the restart or reload appears to be successful
> but the config changes don't take effect. Only on a reboot do they take
> effect. I can't see a problem with the reload or restart but the new
> config doesn't get implemented. There are warnings and errors in syslog
> but if these are a problem then why does a reboot work?
>
> user@server1:~$ motion reload
> [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
> /home/user/.motion/motion.conf
> [0:motion] [NTC] [ALL] config_camera: Processing camera config file
> .motion/camera1.conf
> [0:motion] [NTC] [ALL] config_camera: Processing camera config file
> .motion/camera2.conf
> [0:motion] [NTC] [ALL] motion_startup: Logging to syslog
> [0:motion] [NTC] [ALL] motion_startup: Motion 4.1.1+gitUNKNOWN Started
> [0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
> [0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
> [0:motion] [NTC] [ALL] become_daemon: Motion going to daemon mode
>
>
> Partial syslog output:
>
> user@server1:~$ cat /var/log/syslog | grep motion | grep WRN
>
> Oct? 3 13:43:30 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:30 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:30 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:40 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:40 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:40 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:40 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:50 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:50 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:50 server1 motion: [1:ml1:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
> Oct? 3 13:43:50 server1 motion: [2:ml2:$$$$$] [WRN] [ALL] mlp_retry:
> Retrying until successful connection with camera
>
> user@server1:~$ cat /var/log/syslog | grep motion | grep ERR
>
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
> v4l2_pixfmt_set: Error setting pixel format.#012VIDIOC_S_FMT: : Device
> or resource busy
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
> v4l2_pixfmt_select: Palette selection failed for format JPEG
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
> v4l2_pixfmt_select: Unable to find a compatible palette format.
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID] vid_start:
> V4L2 device failed to open
> Oct? 3 13:45:50 server1 motion: [1:ml1:$$$$$] [ERR] [VID]
> v4l2_input_select: Error selecting input 0 VIDIOC_S_INPUT: Device or
> resource busy
> Oct? 3 13:45:50 server1 motion: [1:ml1:$$$$$] [ERR] [VID] vid_start:
> V4L2 device failed to open
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
> v4l2_pixfmt_set: Error setting pixel format.#012VIDIOC_S_FMT: : Device
> or resource busy
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
> v4l2_pixfmt_set: Error setting pixel format.#012VIDIOC_S_FMT: : Device
> or resource busy
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
> v4l2_pixfmt_select: Palette selection failed for format JPEG
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID]
> v4l2_pixfmt_select: Unable to find a compatible palette format.
> Oct? 3 13:45:50 server1 motion: [2:ml2:$$$$$] [ERR] [VID] vid_start:
> V4L2 device failed to open
>
>
>
>
> _______________________________________________
> 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
------------------------------
------------------------------
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 148, Issue 5
*******************************************
