Send Motion-user mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Motion only at night? (David Powell)
2. Re: Motion only at night? (tosiara)
3. Unit motion.service entered failed state (Harlan Daneker)
4. Re: Unit motion.service entered failed state (Harlan Daneker)
----------------------------------------------------------------------
Message: 1
Date: Sat, 17 Jan 2015 22:43:55 -0600
From: David Powell <[email protected]>
Subject: [Motion-user] Motion only at night?
To: Motion discussion list <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
I have motion running on a PogoPlug, monitoring 9 cameras. All of this has
been working swimmingly except for one camera. This camera was added to the
collection recently, so I just copied one of the other thread's
configuration files and changed the relevant information. It works fine,
but it only records motion at night! Videos of all manner of animals are
recorded all night long, but as soon as the sun comes up, all motion is
ignored, even though the live image from the camera is excellent. What
could possibly cause this odd behavior? Below is the entire configuration
file for that camera (some comment blocks removed for brevity). None of the
other cameras in this collection have this problem.
# This config file was generated by motion 3.2.12
netcam_url?http://bc5560.myfoscam.org/snapshot.cgi?user=?visitor&pwd=?
# Threshold for number of changed pixels in an image that
# triggers motion detection (default: 1500)
threshold 500
# Dynamically create a mask file during operation (default: 0)
# Adjust speed of mask changes from 0 (off) to 10 (fast)
smart_mask_speed 0
# Draw a user defined text on the images using same options as C function
strftime(3)
# Default: Not defined = no text
# Text is placed in lower left corner
text_left Magic Mountain West
# Target base directory for pictures and films
# Recommended to use absolute path. (Default: current working directory)
target_dir /srv/http/cams/mmwest
# The mini-http server listens to this port for requests (default: 0 =
disabled)
webcam_port 1810
sql_query INSERT INTO cameras.events
(server_number,camera_number,event_number,event_date,video_length,filename)
VALUES (0,10,%v,{ts '%C'},null,'%v-%Y%m%d%H%M%S');
?
?
?
Sent with AquaMail for Android
http://www.aqua-mail.com
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Sun, 18 Jan 2015 09:12:45 +0200
From: tosiara <[email protected]>
Subject: Re: [Motion-user] Motion only at night?
To: [email protected], Motion discussion list
<[email protected]>
Message-ID:
<CACHTdwQ1Bh4SXka66qEFroc=Zm=k3JBGB8=97_sevgtre9s...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Can you collect motion's log for at least 24 hours?
On Sun, Jan 18, 2015 at 6:43 AM, David Powell <[email protected]> wrote:
>
> I have motion running on a PogoPlug, monitoring 9 cameras. All of this has
> been working swimmingly except for one camera. This camera was added to the
> collection recently, so I just copied one of the other thread's
> configuration files and changed the relevant information. It works fine,
> but it only records motion at night! Videos of all manner of animals are
> recorded all night long, but as soon as the sun comes up, all motion is
> ignored, even though the live image from the camera is excellent. What
> could possibly cause this odd behavior? Below is the entire configuration
> file for that camera (some comment blocks removed for brevity). None of the
> other cameras in this collection have this problem.
>
> # This config file was generated by motion 3.2.12
>
> netcam_url http://bc5560.myfoscam.org/snapshot.cgi?user=?visitor&pwd=?
> <http://bc5560.myfoscam.org/snapshot.cgi?user=visitor&pwd=>
>
> # Threshold for number of changed pixels in an image that
> # triggers motion detection (default: 1500)
> threshold 500
>
> # Dynamically create a mask file during operation (default: 0)
> # Adjust speed of mask changes from 0 (off) to 10 (fast)
> smart_mask_speed 0
>
> # Draw a user defined text on the images using same options as C function
> strftime(3)
> # Default: Not defined = no text
> # Text is placed in lower left corner
> text_left Magic Mountain West
>
> # Target base directory for pictures and films
> # Recommended to use absolute path. (Default: current working directory)
> target_dir /srv/http/cams/mmwest
>
> # The mini-http server listens to this port for requests (default: 0 =
> disabled)
> webcam_port 1810
>
> sql_query INSERT INTO cameras.events
> (server_number,camera_number,event_number,event_date,video_length,filename)
> VALUES (0,10,%v,{ts '%C'},null,'%v-%Y%m%d%H%M%S');
>
>
>
>
>
> Sent with AquaMail for Android
> http://www.aqua-mail.com
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Motion-user mailing list
> [email protected]
> 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: 3
Date: Mon, 19 Jan 2015 11:09:21 -0500
From: Harlan Daneker <[email protected]>
Subject: [Motion-user] Unit motion.service entered failed state
To: Motion discussion list <[email protected]>
Message-ID:
<CAC1WkiRCVGoO-Y3bGsuc1gSgr=t8y7axywmms7ml7psvhvg...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
*Anybody have an idea why motion died at 03:29?* This is all there was in
the motion.log file for Jan 19, I don't understand why nothing else was
logged or why motion was restarting at this time, I was sleeping.
*/var/log/motion.log*
0] [NTC] [ALL] [Jan 19 03:29:09] motion_startup: Using log type (ALL) log
level (NTC)
[0] [WRN] [ALL] [Jan 19 03:29:09] main: Motion restarted
[0] [NTC] [ALL] [Jan 19 03:29:09] main: Thread 1 is from
/etc/motion/thread1.conf
[0] [NTC] [ALL] [Jan 19 03:29:09] main: Thread 1 is device: /dev/video0
input 0
[0] [NTC] [ALL] [Jan 19 03:29:09] main: Stream port 8081
[0] [NTC] [ALL] [Jan 19 03:29:09] main: Thread 2 is from
/etc/motion/thread2.conf
[1] [NTC] [ALL] [Jan 19 03:29:09] motion_init: Thread 1 started , motion
detection Enabled
[0] [NTC] [ALL] [Jan 19 03:29:09] main: Thread 2 is device: /dev/video2
input 0
*/var/log/messages*
Jan 19 03:29:01 htd systemd: Reloading motion detection system.
Jan 19 03:29:01 htd systemd: Reloaded motion detection system.
Jan 19 03:29:09 htd kernel: [130857.512109] motion[22102]: segfault at 0 ip
00000037a713bffa sp 0000
7fe64957ead8 error 4 in libc-2.18.so[37a7000000+1b4000]
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] conf_load: Processing thread 0
- config file /etc/motion
/motion.conf
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
config file /etc/motion/thread
1.conf
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
config file /etc/motion/thread
2.conf
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
config file /etc/motion/thread
3.conf
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] motion_startup: Motion 3.3.0
Started
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] motion_startup: Logging to file
(/var/log/motion.log)
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] conf_load: Processing thread 0
- config file /etc/motion
/motion.conf
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
config file /etc/motion/thread
1.conf
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
config file /etc/motion/thread
2.conf
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
config file /etc/motion/thread
3.conf
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] motion_startup: Motion 3.3.0
Started
Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] motion_startup: Logging to file
(/var/log/motion.log)
Jan 19 03:29:09 htd kernel: motion[22102]: segfault at 0 ip
00000037a713bffa sp 00007fe64957ead8 err
or 4 in libc-2.18.so[37a7000000+1b4000]
Jan 19 03:29:10 htd abrt-hook-ccpp: Saved core dump of pid 664
(/usr/bin/motion) to /var/tmp/abrt/cc
pp-2015-01-19-03:29:09-664 (77930496 bytes)
Jan 19 03:29:10 htd systemd: motion.service: main process exited,
code=killed, status=11/SEGV
Jan 19 03:29:10 htd systemd: Unit motion.service entered failed state.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Mon, 19 Jan 2015 11:20:23 -0500
From: Harlan Daneker <[email protected]>
Subject: Re: [Motion-user] Unit motion.service entered failed state
To: Motion discussion list <[email protected]>
Message-ID:
<CAC1WkiQo_ZdjctzCr=mwjaov+2nuhbfm7ql6v5hlb0woohk...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
The last thing recorded was at 03:21 Jan 19.
I looked for this, but it doesn't seem to be there.
Saved core dump of pid 664 (/usr/bin/motion) to /var/tmp/abrt/cc
pp-2015-01-19-03:29:09-664 (77930496 bytes)
On Mon, Jan 19, 2015 at 11:09 AM, Harlan Daneker <[email protected]> wrote:
> *Anybody have an idea why motion died at 03:29?* This is all there was in
> the motion.log file for Jan 19, I don't understand why nothing else was
> logged or why motion was restarting at this time, I was sleeping.
>
>
> */var/log/motion.log*
> 0] [NTC] [ALL] [Jan 19 03:29:09] motion_startup: Using log type (ALL) log
> level (NTC)
> [0] [WRN] [ALL] [Jan 19 03:29:09] main: Motion restarted
> [0] [NTC] [ALL] [Jan 19 03:29:09] main: Thread 1 is from
> /etc/motion/thread1.conf
> [0] [NTC] [ALL] [Jan 19 03:29:09] main: Thread 1 is device: /dev/video0
> input 0
> [0] [NTC] [ALL] [Jan 19 03:29:09] main: Stream port 8081
> [0] [NTC] [ALL] [Jan 19 03:29:09] main: Thread 2 is from
> /etc/motion/thread2.conf
> [1] [NTC] [ALL] [Jan 19 03:29:09] motion_init: Thread 1 started , motion
> detection Enabled
> [0] [NTC] [ALL] [Jan 19 03:29:09] main: Thread 2 is device: /dev/video2
> input 0
>
>
> */var/log/messages*
> Jan 19 03:29:01 htd systemd: Reloading motion detection system.
> Jan 19 03:29:01 htd systemd: Reloaded motion detection system.
> Jan 19 03:29:09 htd kernel: [130857.512109] motion[22102]: segfault at 0
> ip 00000037a713bffa sp 0000
> 7fe64957ead8 error 4 in libc-2.18.so[37a7000000+1b4000]
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] conf_load: Processing thread 0
> - config file /etc/motion
> /motion.conf
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
> config file /etc/motion/thread
> 1.conf
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
> config file /etc/motion/thread
> 2.conf
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
> config file /etc/motion/thread
> 3.conf
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] motion_startup: Motion 3.3.0
> Started
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] motion_startup: Logging to
> file (/var/log/motion.log)
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] conf_load: Processing thread 0
> - config file /etc/motion
> /motion.conf
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
> config file /etc/motion/thread
> 1.conf
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
> config file /etc/motion/thread
> 2.conf
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] config_thread: Processing
> config file /etc/motion/thread
> 3.conf
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] motion_startup: Motion 3.3.0
> Started
> Jan 19 03:29:09 htd motion: [0] [NTC] [ALL] motion_startup: Logging to
> file (/var/log/motion.log)
> Jan 19 03:29:09 htd kernel: motion[22102]: segfault at 0 ip
> 00000037a713bffa sp 00007fe64957ead8 err
> or 4 in libc-2.18.so[37a7000000+1b4000]
> Jan 19 03:29:10 htd abrt-hook-ccpp: Saved core dump of pid 664
> (/usr/bin/motion) to /var/tmp/abrt/cc
> pp-2015-01-19-03:29:09-664 (77930496 bytes)
> Jan 19 03:29:10 htd systemd: motion.service: main process exited,
> code=killed, status=11/SEGV
> Jan 19 03:29:10 htd systemd: Unit motion.service entered failed state.
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 104, Issue 2
*******************************************
