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. Re: Unit motion.service entered failed state (tosiara)
2. Re: Unit motion.service entered failed state (Harlan Daneker)
3. Re: Unit motion.service entered failed state (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Mon, 19 Jan 2015 18:23:42 +0200
From: tosiara <[email protected]>
Subject: Re: [Motion-user] Unit motion.service entered failed state
To: Motion discussion list <[email protected]>
Message-ID:
<CACHTdwSxsMXWhi=-tb=cy5c5rgbmfxievr5zrodn6jocgfn...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Well, your motion crashed. Where did you get "Motion 3.3.0" from?
On Mon, Jan 19, 2015 at 6:20 PM, Harlan Daneker <[email protected]> wrote:
> 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.
>>
>
>
>
> ------------------------------------------------------------------------------
> 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: 2
Date: Mon, 19 Jan 2015 12:21:31 -0500
From: Harlan Daneker <[email protected]>
Subject: Re: [Motion-user] Unit motion.service entered failed state
To: Motion discussion list <[email protected]>
Message-ID:
<CAC1WkiSMe+HCcWPR=sgywm0taedfcinsvbh4742wlr+mjr6...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
rpmfusion.org
On Mon, Jan 19, 2015 at 11:23 AM, tosiara <[email protected]> wrote:
> Well, your motion crashed. Where did you get "Motion 3.3.0" from?
>
> On Mon, Jan 19, 2015 at 6:20 PM, Harlan Daneker <[email protected]>
> wrote:
>
>> 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.
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>
>
> ------------------------------------------------------------------------------
> 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 19:41:37 +0200
From: tosiara <[email protected]>
Subject: Re: [Motion-user] Unit motion.service entered failed state
To: Motion discussion list <[email protected]>
Message-ID:
<CACHTdwT9G0vJW2BdFA50-gz_n04Lu=w0idpfoahwyp0bnuw...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
So it seems to be trunk rev 557. Pretty outdated
Would you mind building the latest? With ffmpeg also built from sources
The most recent development version is Mr-Dave (called "unofficial fork"
now). Link is provided on Download page
On Mon, Jan 19, 2015 at 7:21 PM, Harlan Daneker <[email protected]> wrote:
> rpmfusion.org
>
> On Mon, Jan 19, 2015 at 11:23 AM, tosiara <[email protected]> wrote:
>
>> Well, your motion crashed. Where did you get "Motion 3.3.0" from?
>>
>> On Mon, Jan 19, 2015 at 6:20 PM, Harlan Daneker <[email protected]>
>> wrote:
>>
>>> 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.
>>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>
>
> ------------------------------------------------------------------------------
> 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...
------------------------------
------------------------------------------------------------------------------
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 3
*******************************************
