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: Motion Version 4.01 process end (Florian Heiser)
2. Re: Motion Version 4.01 process end (Colin Law)
3. Re: Motion Version 4.01 process end (thomas)
4. Re: Motion Version 4.01 process end (Florian H.)
5. Re: Motion Version 4.01 process end (Riccardo Stronati)
----------------------------------------------------------------------
Message: 1
Date: Sat, 5 Nov 2016 23:14:23 -0400
From: Florian Heiser <emailtoflor...@gmail.com>
Subject: Re: [Motion-user] Motion Version 4.01 process end
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID: <6c4420a2-98b1-3dff-8fee-646c55ffa...@gmail.com>
Content-Type: text/plain; charset=windows-1252
On 04.11.2016 19:02, Thomas Drebert wrote:
> Hello,
>
> i start my motion with "sudo motion", i thing you find my config in
> the list archive.
Dear all,
I'd like to understand why apparently many users are using "sudo" to
start motion as root.
Why would that be necessary?
Thanks,
Florian
------------------------------
Message: 2
Date: Sun, 6 Nov 2016 08:45:54 +0000
From: Colin Law <clan...@gmail.com>
Subject: Re: [Motion-user] Motion Version 4.01 process end
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID:
<CAL=0gLtrVfSvM2-ayNrf=i11ouxqgnkugqdffgzwayy+uy8...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On 5 November 2016 at 17:12, Riccardo Stronati <r.stron...@gmail.com> wrote:
> Hi this is the syslog output:
> Nov 5 17:51:22 raspberrypi systemd[1]: Starting Motion daemon...
> Nov 5 17:51:22 raspberrypi systemd[1]: Started Motion daemon.
> Nov 5 17:51:22 raspberrypi motion: [0:motion] [NTC] [ALL] conf_load:
> Processing thread 0 - config file /etc/motion/motion.conf
> Nov 5 17:51:22 raspberrypi motion: [0:motion] [NTC] [ALL] motion_startup:
> Motion 4.0.1 Started
> Nov 5 17:51:22 raspberrypi motion: [0:motion] [NTC] [ALL] motion_startup:
> Logging to file (/tmp/motion.log)
> Nov 5 17:52:52 raspberrypi systemd[1]: motion.service stop-sigterm timed
> out. Killing.
> Nov 5 17:52:52 raspberrypi rsyslogd-2007: action 'action 17' suspended,
> next retry is Sat Nov 5 17:54:22 2016 [try http://www.rsyslog.com/e/2007
> ]
> Nov 5 17:52:52 raspberrypi systemd[1]: Unit motion.service entered failed
> state.
>
It looks as if there may be an error in the systemd service file for motion.
Can you post the syslog output that you get when running just using sudo
please.
Also the output from
which motion
and the contents of the systemd service file motion.service. It will tell
you where that is if you run
sudo systemctl status motion
Colin
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Sun, 6 Nov 2016 17:48:32 +0100
From: thomas <674...@web.de>
Subject: Re: [Motion-user] Motion Version 4.01 process end
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID: <cd7f61a1-e6b0-cd49-124f-6ca8ad18b...@web.de>
Content-Type: text/plain; charset="windows-1252"
It is not necessary.
I start it as user "pi"
@reboot sudo -u pi /usr/bin/motion .....
for that i had to comment out the this line:
<http://192.168.0.111:8078/0/config/set?logfile># process_id_file
/var/run/motion/motion.pid
or setting this file to an accessible folder:
process_id_file /home/pi/motion/motion.pid
Am 06.11.2016 um 04:14 schrieb Florian Heiser:
> hive.
> Dear all,
> I'd like to understand why apparently many users are using "sudo" to
> start motion as root.
> Why would that be necessary?
>
> Thanks,
> Florian
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Sun, 6 Nov 2016 14:03:52 -0500
From: "Florian H." <emailtoflor...@gmail.com>
Subject: Re: [Motion-user] Motion Version 4.01 process end
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID: <8e87a9e7-32d9-4b4d-9b52-473803097...@gmail.com>
Content-Type: text/plain; charset="us-ascii"
> On Nov 6, 2016, at 11:48, thomas <674...@web.de> wrote:
>
> It is not necessary.
> I start it as user "pi"
> @reboot sudo -u pi /usr/bin/motion .....
That's right. I think I've seen in various other post that people use "sudo
motion" to start motion.
> for that i had to comment out the this line:
> # process_id_file /var/run/motion/motion.pid
I just changed permission for /var/run/motion so that the process started by
user pi is allowed to write there (sudo chmod 777 /var/run/motion).
I was rather wondering if there is any other functionality of motion that
requires root access (by default).
Usually I try to avoid running programs with root permissions if not needed.
>
> or setting this file to an accessible folder:
> process_id_file /home/pi/motion/motion.pid
+1.
>
>
>
>
>> Am 06.11.2016 um 04:14 schrieb Florian
>> hive.
>> Dear all,
>> I'd like to understand why apparently many users are using "sudo" to
>> start motion as root.
>> Why would that be necessary?
>>
>> Thanks,
>> Florian
>>
>>
>> -----------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 5
Date: Sun, 6 Nov 2016 21:02:40 +0100
From: Riccardo Stronati <r.stron...@gmail.com>
Subject: Re: [Motion-user] Motion Version 4.01 process end
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID:
<cabhf65ewcfa7u-agrkaozfqv+zyaegdmnzbj6evo+r_vvb1...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I post the logs as requested.
As Colin Law suggested seems to be a problem with systemd.
//starting with sudo motion
/var/log/system.log
Nov 6 20:58:36 raspberrypi motion: [0:motion] [NTC] [ALL] conf_load:
Processing thread 0 - config file /etc/motion/motion.conf
Nov 6 20:58:36 raspberrypi motion: [0:motion] [NTC] [ALL] motion_startup:
Motion 4.0.1 Started
Nov 6 20:58:36 raspberrypi motion: [0:motion] [NTC] [ALL] motion_startup:
Logging to file (/tmp/motion.log)
/tmp/motion.log
[0:motion] [NTC] [ALL] [Nov 06 20:49:13] motion_startup: Using log type
(ALL) log level (NTC)
[0:motion] [NTC] [ALL] [Nov 06 20:49:13] become_daemon: Motion going to
daemon mode
[0:motion] [NTC] [ALL] [Nov 06 20:49:13] become_daemon: Created process id
file /var/run/motion/motion.pid. Process ID is 817
[0:motion] [NTC] [ALL] [Nov 06 20:49:13] motion_startup: Motion running as
daemon process
[0:motion] [NTC] [ENC] [Nov 06 20:49:13] ffmpeg_init: ffmpeg libavcodec
version 56.1.0 libavformat version 56.1.0
[0:motion] [NTC] [ALL] [Nov 06 20:49:13] main: Camera 0 is from
/etc/motion/motion.conf
[0:motion] [NTC] [ALL] [Nov 06 20:49:13] main: Camera 0 is device:
/dev/video0 input -1
[0:motion] [NTC] [ALL] [Nov 06 20:49:13] main: Stream port 8081
[1:ml1] [NTC] [ALL] [Nov 06 20:49:13] motion_init: Camera 0 started: motion
detection Enabled
[0:motion] [NTC] [ALL] [Nov 06 20:49:13] main: Waiting for threads to
finish, pid: 817
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] vid_v4lx_start: Using videodevice
/dev/video0 and input -1
[0:web_control] [NTC] [STR] [Nov 06 20:49:13] http_bindsock: listening on
any IPv4/IPv6 address port 8082
[0:web_control] [NTC] [STR] [Nov 06 20:49:13] httpd_run: Started
motion-httpd server on port 8082 (auth Disabled)
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_get_capability:
------------------------
cap.driver: "uvcvideo"
cap.card: "Trust Webcam"
cap.bus_info: "usb-3f980000.usb-1.3"
cap.capabilities=0x84200001
------------------------
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_get_capability: - VIDEO_CAPTURE
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_get_capability: - STREAMING
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_select_input: name = "Camera 1",
type 0x00000002, status 00000000
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_select_input: - CAMERA
[1:ml1] [WRN] [VID] [Nov 06 20:49:13] v4l2_select_input: Device doesn't
support VIDIOC_G_STD
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_set_pix_format: Config palette
index 17 (YU12) doesn't work.
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_set_pix_format: Supported
palettes:
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_set_pix_format: (0) YUYV (YUYV
4:2:2)
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_set_pix_format: 0 - YUYV 4:2:2
(compressed : 0) (0x56595559)
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_set_pix_format Selected palette
YUYV
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_do_set_pix_format: Testing
palette YUYV (352x288)
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_do_set_pix_format: Using palette
YUYV (352x288) bytesperlines 704 sizeimage 202752 colorspace 00000008
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: found control
0x00980900, "Brightness", range -64,64
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: "Brightness",
default -8193, current -5
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: found control
0x00980901, "Contrast", range 0,64
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: "Contrast",
default 57343, current 36
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: found control
0x00980902, "Saturation", range 1,128
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: "Saturation",
default 57343, current 72
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: found control
0x00980903, "Hue", range -40,40
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: "Hue",
default -8193, current -5
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: found control
0x00980918, "Power Line Frequency", range 0,2
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: "Power Line
Frequency", default 1, current 1
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: found control
0x00980910, "Gamma", range 72,500
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: "Gamma",
default 57343, current 85
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: found control
0x00980913, "Gain", range 0,100
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] v4l2_scan_controls: "Gain",
default 57343, current 0
[1:ml1] [NTC] [VID] [Nov 06 20:49:13] vid_v4lx_start: Using V4L2
[1:ml1] [NTC] [ALL] [Nov 06 20:49:13] image_ring_resize: Resizing
pre_capture buffer to 1 items
[1:ml1] [NTC] [STR] [Nov 06 20:49:14] http_bindsock: listening on any
IPv4/IPv6 address port 8081
[1:ml1] [NTC] [ALL] [Nov 06 20:49:14] motion_init: Started motion-stream
server on port 8081 (auth Enabled)
[1:ml1] [NTC] [ALL] [Nov 06 20:49:14] image_ring_resize: Resizing
pre_capture buffer to 7 items
[1:ml1] [NTC] [EVT] [Nov 06 20:49:15] event_ffmpeg_timelapse: Timelapse
using mpeg4 codec.
[1:ml1] [NTC] [EVT] [Nov 06 20:49:15] event_ffmpeg_timelapse: Events will
be trigger new files
[1:ml1] [NTC] [ENC] [Nov 06 20:49:15] ffmpeg_open Selected Output FPS 2
[1:ml1] [NTC] [EVT] [Nov 06 20:49:15] event_newfile: File of type 32 saved
to: /home/pi/motion/20161106-20-timelapse.avi
//starting with systemctl start motion
/var/log/system.log
Nov 6 20:54:51 raspberrypi systemd[1]: Starting Motion daemon...
Nov 6 20:54:51 raspberrypi systemd[1]: Started Motion daemon.
Nov 6 20:54:51 raspberrypi motion: [0:motion] [NTC] [ALL] conf_load:
Processing thread 0 - config file /etc/motion/motion.conf
Nov 6 20:54:51 raspberrypi motion: [0:motion] [NTC] [ALL] motion_startup:
Motion 4.0.1 Started
Nov 6 20:54:51 raspberrypi motion: [0:motion] [NTC] [ALL] motion_startup:
Logging to file (/tmp/motion.log)
Nov 6 20:56:21 raspberrypi systemd[1]: motion.service stop-sigterm timed
out. Killing.
Nov 6 20:56:21 raspberrypi systemd[1]: Unit motion.service entered failed
state.
/tmp/motion.log
[0:motion] [NTC] [ALL] [Nov 06 20:54:51] motion_startup: Using log type
(ALL) log level (NTC)
[0:motion] [NTC] [ALL] [Nov 06 20:54:51] become_daemon: Motion going to
daemon mode
[0:motion] [NTC] [ALL] [Nov 06 20:54:51] become_daemon: Created process id
file /var/run/motion/motion.pid. Process ID is 908
[0:motion] [NTC] [ALL] [Nov 06 20:54:51] motion_startup: Motion running as
daemon process
[0:motion] [NTC] [ENC] [Nov 06 20:54:51] ffmpeg_init: ffmpeg libavcodec
version 56.1.0 libavformat version 56.1.0
[0:motion] [NTC] [ALL] [Nov 06 20:54:51] main: Camera 0 is from
/etc/motion/motion.conf
[0:motion] [NTC] [ALL] [Nov 06 20:54:51] main: Camera 0 is device:
/dev/video0 input -1
[0:motion] [NTC] [ALL] [Nov 06 20:54:51] main: Stream port 8081
[1:ml1] [NTC] [ALL] [Nov 06 20:54:51] motion_init: Camera 0 started: motion
detection Enabled
[0:motion] [NTC] [ALL] [Nov 06 20:54:51] main: Waiting for threads to
finish, pid: 908
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] vid_v4lx_start: Using videodevice
/dev/video0 and input -1
[0:web_control] [NTC] [STR] [Nov 06 20:54:51] http_bindsock: listening on
any IPv4/IPv6 address port 8082
[0:web_control] [NTC] [STR] [Nov 06 20:54:51] httpd_run: Started
motion-httpd server on port 8082 (auth Disabled)
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_get_capability:
------------------------
cap.driver: "uvcvideo"
cap.card: "Trust Webcam"
cap.bus_info: "usb-3f980000.usb-1.3"
cap.capabilities=0x84200001
------------------------
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_get_capability: - VIDEO_CAPTURE
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_get_capability: - STREAMING
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_select_input: name = "Camera 1",
type 0x00000002, status 00000000
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_select_input: - CAMERA
[1:ml1] [WRN] [VID] [Nov 06 20:54:51] v4l2_select_input: Device doesn't
support VIDIOC_G_STD
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_set_pix_format: Config palette
index 17 (YU12) doesn't work.
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_set_pix_format: Supported
palettes:
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_set_pix_format: (0) YUYV (YUYV
4:2:2)
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_set_pix_format: 0 - YUYV 4:2:2
(compressed : 0) (0x56595559)
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_set_pix_format Selected palette
YUYV
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_do_set_pix_format: Testing
palette YUYV (352x288)
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_do_set_pix_format: Using palette
YUYV (352x288) bytesperlines 704 sizeimage 202752 colorspace 00000008
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: found control
0x00980900, "Brightness", range -64,64
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: "Brightness",
default -8193, current -5
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: found control
0x00980901, "Contrast", range 0,64
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: "Contrast",
default 57343, current 36
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: found control
0x00980902, "Saturation", range 1,128
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: "Saturation",
default 57343, current 72
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: found control
0x00980903, "Hue", range -40,40
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: "Hue",
default -8193, current -5
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: found control
0x00980918, "Power Line Frequency", range 0,2
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: "Power Line
Frequency", default 1, current 1
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: found control
0x00980910, "Gamma", range 72,500
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: "Gamma",
default 57343, current 85
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: found control
0x00980913, "Gain", range 0,100
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] v4l2_scan_controls: "Gain",
default 57343, current 0
[1:ml1] [NTC] [VID] [Nov 06 20:54:51] vid_v4lx_start: Using V4L2
[1:ml1] [NTC] [ALL] [Nov 06 20:54:51] image_ring_resize: Resizing
pre_capture buffer to 1 items
[0:web_control] [NTC] [STR] [Nov 06 20:54:52] httpd_run: motion-httpd -
Finishing
[0:web_control] [NTC] [STR] [Nov 06 20:54:52] httpd_run: motion-httpd
Closing
[0:web_control] [NTC] [STR] [Nov 06 20:54:52] motion_web_control:
motion-httpd thread exit
[1:ml1] [NTC] [STR] [Nov 06 20:54:53] http_bindsock: listening on any
IPv4/IPv6 address port 8081
[1:ml1] [NTC] [ALL] [Nov 06 20:54:53] motion_init: Started motion-stream
server on port 8081 (auth Enabled)
[1:ml1] [NTC] [ALL] [Nov 06 20:54:53] motion_loop: Thread exiting
[1:ml1] [NTC] [STR] [Nov 06 20:54:53] stream_stop: Closing motion-stream
listen socket & active motion-stream sockets
[1:ml1] [NTC] [STR] [Nov 06 20:54:53] stream_stop: Closed motion-stream
listen socket & active motion-stream sockets
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] vid_close: Closing video device
/dev/video0
[0:motion] [NTC] [ALL] [Nov 06 20:54:53] main: Motion thread 1 restart
[1:ml1] [NTC] [ALL] [Nov 06 20:54:53] motion_init: Camera 0 started: motion
detection Enabled
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] vid_v4lx_start: Using videodevice
/dev/video0 and input -1
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_get_capability:
------------------------
cap.driver: "uvcvideo"
cap.card: "Trust Webcam"
cap.bus_info: "usb-3f980000.usb-1.3"
cap.capabilities=0x84200001
------------------------
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_get_capability: - VIDEO_CAPTURE
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_get_capability: - STREAMING
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_select_input: name = "Camera 1",
type 0x00000002, status 00000000
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_select_input: - CAMERA
[1:ml1] [WRN] [VID] [Nov 06 20:54:53] v4l2_select_input: Device doesn't
support VIDIOC_G_STD
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_set_pix_format: Config palette
index 17 (YU12) doesn't work.
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_set_pix_format: Supported
palettes:
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_set_pix_format: (0) YUYV (YUYV
4:2:2)
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_set_pix_format: 0 - YUYV 4:2:2
(compressed : 0) (0x56595559)
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_set_pix_format Selected palette
YUYV
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_do_set_pix_format: Testing
palette YUYV (352x288)
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_do_set_pix_format: Using palette
YUYV (352x288) bytesperlines 704 sizeimage 202752 colorspace 00000008
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: found control
0x00980900, "Brightness", range -64,64
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: "Brightness",
default -8193, current -5
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: found control
0x00980901, "Contrast", range 0,64
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: "Contrast",
default 57343, current 36
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: found control
0x00980902, "Saturation", range 1,128
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: "Saturation",
default 57343, current 72
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: found control
0x00980903, "Hue", range -40,40
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: "Hue",
default -8193, current -5
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: found control
0x00980918, "Power Line Frequency", range 0,2
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: "Power Line
Frequency", default 1, current 1
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: found control
0x00980910, "Gamma", range 72,500
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: "Gamma",
default 57343, current 85
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: found control
0x00980913, "Gain", range 0,100
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] v4l2_scan_controls: "Gain",
default 57343, current 0
[1:ml1] [NTC] [VID] [Nov 06 20:54:53] vid_v4lx_start: Using V4L2
[1:ml1] [NTC] [ALL] [Nov 06 20:54:53] image_ring_resize: Resizing
pre_capture buffer to 1 items
[1:ml1] [NTC] [STR] [Nov 06 20:54:55] http_bindsock: listening on any
IPv4/IPv6 address port 8081
[1:ml1] [NTC] [ALL] [Nov 06 20:54:55] motion_init: Started motion-stream
server on port 8081 (auth Enabled)
[1:ml1] [NTC] [ALL] [Nov 06 20:54:55] image_ring_resize: Resizing
pre_capture buffer to 7 items
[1:ml1] [NTC] [EVT] [Nov 06 20:54:55] event_ffmpeg_timelapse: Timelapse
using mpeg4 codec.
[1:ml1] [NTC] [EVT] [Nov 06 20:54:55] event_ffmpeg_timelapse: Events will
be trigger new files
[1:ml1] [NTC] [ENC] [Nov 06 20:54:55] ffmpeg_open Selected Output FPS 2
[1:ml1] [NTC] [EVT] [Nov 06 20:54:55] event_newfile: File of type 32 saved
to: /home/pi/motion/20161106-20-timelapse.avi
this is the motion.service
[Unit]
Description=Motion daemon
After=local-fs.target network.target
[Service]
PIDFile=/var/run/motion.pid
ExecStart=/usr/bin/motion
Type=simple
StandardError=null
[Install]
WantedBy=multi-user.target
2016-11-06 9:45 GMT+01:00 Colin Law <clan...@gmail.com>:
> On 5 November 2016 at 17:12, Riccardo Stronati <r.stron...@gmail.com>
> wrote:
>
>> Hi this is the syslog output:
>> Nov 5 17:51:22 raspberrypi systemd[1]: Starting Motion daemon...
>> Nov 5 17:51:22 raspberrypi systemd[1]: Started Motion daemon.
>> Nov 5 17:51:22 raspberrypi motion: [0:motion] [NTC] [ALL] conf_load:
>> Processing thread 0 - config file /etc/motion/motion.conf
>> Nov 5 17:51:22 raspberrypi motion: [0:motion] [NTC] [ALL]
>> motion_startup: Motion 4.0.1 Started
>> Nov 5 17:51:22 raspberrypi motion: [0:motion] [NTC] [ALL]
>> motion_startup: Logging to file (/tmp/motion.log)
>> Nov 5 17:52:52 raspberrypi systemd[1]: motion.service stop-sigterm timed
>> out. Killing.
>> Nov 5 17:52:52 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Sat Nov 5 17:54:22 2016 [try http://www.rsyslog.com/e/2007
>> ]
>> Nov 5 17:52:52 raspberrypi systemd[1]: Unit motion.service entered
>> failed state.
>>
>
>
> It looks as if there may be an error in the systemd service file for
> motion.
> Can you post the syslog output that you get when running just using sudo
> please.
> Also the output from
> which motion
> and the contents of the systemd service file motion.service. It will tell
> you where that is if you run
> sudo systemctl status motion
>
> Colin
>
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
------------------------------
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 126, Issue 8
*******************************************
