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 (Javier Marcon)
----------------------------------------------------------------------
Message: 1
Date: Fri, 23 Jan 2015 16:39:33 -0300
From: Javier Marcon <[email protected]>
Subject: Re: [Motion-user] Unit motion.service entered failed state
To: Motion discussion list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Have you tried the solutions posted in
http://stackoverflow.com/questions/23932247/ffmpeg-seems-to-be-version-conflict
and in
http://stackoverflow.com/questions/24876022/how-to-correctly-link-ffmpeg-to-static-build-g-static
?
Regards,
Javier.
El 23/01/15 a las 15:25, Harlan Daneker escibi?:
> *./configure --with-ffmpeg=/usr/local/lib
> --with-ffmpeg-headers=/opt/FFmpeg*
>
> **************************
> Configure status
> motion 3.4.0-Git-78ba2da
> **************************
>
> OS : Linux
> pthread support: Yes
> jpeg support: Yes
> V4L support: Yes
> V4L2 support: Yes
> SDL support: No
> FFmpeg support: Yes
> SQLite3 support: No
> MYSQL support: No
> PostgreSQL support: No
>
>
> *make*
>
> Linking Motion...
> --------------------------------------------------------------------------------
> gcc -L/usr/local/lib -o motion motion.o logger.o conf.o draw.o
> jpegutils.o vloopback_motion.o video.o video2.o video_common.o
> netcam.o netcam_ftp.o netcam_jpeg.o netcam_wget.o track.o alg.o
> event.o picture.o rotate.o webhttpd.o stream.o md5.o netcam_rtsp.o
> ffmpeg.o -lm -lpthread -ljpeg -L/usr/local/lib -lavformat -lavcodec
> -lavutil -lm -lz -lswscale
> /usr/local/lib/libavcodec.a(opusdec.o): In function
> `opus_decode_subpacket':
> /opt/FFmpeg/libavcodec/opusdec.c:376: undefined reference to
> `swr_is_initialized'
> /usr/local/lib/libavcodec.a(opusdec.o): In function `opus_decode_frame':
> /opt/FFmpeg/libavcodec/opusdec.c:222: undefined reference to
> `swr_is_initialized'
> /usr/local/lib/libavcodec.a(opusdec.o): In function `opus_init_resample':
> /opt/FFmpeg/libavcodec/opusdec.c:163: undefined reference to `swr_init'
> /opt/FFmpeg/libavcodec/opusdec.c:169: undefined reference to `swr_convert'
> /usr/local/lib/libavcodec.a(opusdec.o): In function `opus_decode_frame':
> /opt/FFmpeg/libavcodec/opusdec.c:236: undefined reference to `swr_convert'
> /usr/local/lib/libavcodec.a(opusdec.o): In function `opus_flush_resample':
> /opt/FFmpeg/libavcodec/opusdec.c:117: undefined reference to `swr_convert'
> /usr/local/lib/libavcodec.a(opusdec.o): In function
> `opus_decode_subpacket':
> /opt/FFmpeg/libavcodec/opusdec.c:408: undefined reference to `swr_close'
> /usr/local/lib/libavcodec.a(opusdec.o): In function `opus_decode_flush':
> /opt/FFmpeg/libavcodec/opusdec.c:563: undefined reference to `swr_close'
> /usr/local/lib/libavcodec.a(opusdec.o): In function `opus_decode_close':
> /opt/FFmpeg/libavcodec/opusdec.c:585: undefined reference to `swr_free'
> /usr/local/lib/libavcodec.a(opusdec.o): In function `opus_decode_init':
> /opt/FFmpeg/libavcodec/opusdec.c:638: undefined reference to `swr_alloc'
> collect2: error: ld returned 1 exit status
> make: *** [motion] Error 1
>
>
> On Tue, Jan 20, 2015 at 12:52 AM, tosiara <[email protected]
> <mailto:[email protected]>> wrote:
>
> This is the "unofficial fork" I mentioned:
> https://github.com/Mr-Dave/motion
> It is also provided on downloads page
> http://www.lavrsen.dk/foswiki/bin/view/Motion/DownloadFiles
> (scroll to the bottom)
>
> The build process is straight forward. Like this:
>
> git clone git://source.ffmpeg.org/ffmpeg.git
> <http://source.ffmpeg.org/ffmpeg.git> ffmpeg
> cd ffmpeg
> ./configure --prefix=/full/path/to/ffmpeg/source/out
> make
> make install
>
> cd ..
> git clone https://github.com/Mr-Dave/motion.git
> cd motion
> ./configure --with-ffmpeg=/full/path/to/ffmpeg/source/out
> make
>
> If you get error linking motion, like this
> https://github.com/sackmotion/motion/issues/33, just follow
> provided workaround and modify Makefile
>
>
>
> On Mon, Jan 19, 2015 at 10:33 PM, Harlan Daneker
> <[email protected] <mailto:[email protected]>> wrote:
>
> No, I have a UPS. I'm just not sure where to find the source
> downloads that Tosiara is talking about. I'm supposed to be
> running _3.3.0_ and the current source at
>
> http://www.lavrsen.dk/foswiki/bin/view/Motion/DownloadFiles
>
> is _3.2.12_
>
> I'm not sure which source versions of motion and ffmpeg to
> get. When I used to compile motion I know that was important.
> If there is something newer that may work better I'll try it.
>
> Thanks,
>
> Harlan
>
>
>
> On Mon, Jan 19, 2015 at 2:35 PM, Nigel Heasman
> <[email protected] <mailto:[email protected]>> wrote:
>
> Maybe you had a power cut ??
> Nigel
>
>
> On 19/01/15 18:09, Harlan Daneker 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
>> <http://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 <http://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]
>> <mailto:[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]
> <mailto:[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]
> <mailto:[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]
> <mailto:[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 9
*******************************************
