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: cammera recconected and position changed (Joel Avery)
   2. Re: Unit motion.service entered failed state (Harlan Daneker)


----------------------------------------------------------------------

Message: 1
Date: Fri, 23 Jan 2015 12:27:16 +0000 (UTC)
From: Joel Avery <[email protected]>
Subject: Re: [Motion-user] cammera recconected and position changed
To: Motion discussion list <[email protected]>
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="utf-8"

My cameras go back to preset position 1.?


 

     On Thursday, January 22, 2015 1:31 PM, Javier Marcon 
<[email protected]> wrote:
   
 

  Thanks. It seems exactly what happens to me, and I also have a low cost 
chinese cammera. Is there any way to preset the starting position so it gets to 
the same position when it reboots?
 
 Thanks,
 
 Javier.
 
 El 22/01/15 a las 14:47, Artur Pinheiro escibi?:
  
 
 Hi.
 
 I have this happening in one of my IP cameras. It is a low cost Chinese? IP 
camera.
 
 It reboot for it self, and the position some times changes, just like yours...
 
 I think this is a camera fault!
 
 Artur
 
 On 21-01-2015 21:47, Javier Marcon wrote:
  
 
Thanks. I didn rebooted the cammera and never disconnected the power. Does this 
kind of cammera's have a log file or web request to know if it rebooted  
automatically? Is it possible to avoid pan and tilt reset on cammera reboot?
 
 Thanks,
 
 Javier.
 
 El 21/01/15 a las 18:38, Mike Wilson escibi?:
  
Is the camera rebooting by any chance? I know my pan and tilt camera will reset 
it's position when it reboots.
 
 On Wed Jan 21 2015 at 3:26:23 PM Javier Marcon <[email protected]> wrote:
 
Hello, I am using motion and randomly y see this in motion log:
 
 [1] Unrecognized image header (1)
 [1] connect() failed (106): Transport endpoint is already connected
 [1] re-opening camera (streaming)
 [1] Unrecognized image header (1)
 [1] Unrecognized image header (1)
 [1] camera re-connected
 
 When that happens, I see that the cammera is pointing to another
 position. Every time that this happens, the cammera moves to the same
 position.
 
 The cammera is a generic chinese ip cammera listening on port 81.
 
 Is there any way to solve this or does anybody know a fix to it?
 
 The file .motion/motion.conf contains this parameters:
 
 daemon off
 process_id_file /var/run/motion/motion.pid
 setup_mode off
 width 640
 height 480
 framerate 24
 minimum_frame_time 0
 netcam_url http://192.168.1.220:81/videostream.cgi
 netcam_userpass admin:password
 netcam_http keep_alive
 netcam_tolerant_check on
 auto_brightness off
 brightness 0
 contrast 0
 saturation 0
 hue 0
 roundrobin_frames 1
 roundrobin_skip 1
 switchfilter off
 threshold 1000
 threshold_tune off
 noise_level 32
 noise_tune on
 despeckle EedDl
 mask_file /home/javier/.motion/mapa_camara1.pgm
 smart_mask_speed 3
 lightswitch 3
 minimum_motion_frames 2
 pre_capture 3
 post_capture 5
 gap 60
 max_mpeg_time 0
 output_all off
 output_normal off
 output_motion off
 quality 75
 ppm off
 ffmpeg_cap_new on
 ffmpeg_cap_motion off
 ffmpeg_timelapse 0
 ffmpeg_timelapse_mode daily
 ffmpeg_bps 500000
 ffmpeg_variable_bitrate 0
 ffmpeg_video_codec mpeg4
 ffmpeg_deinterlace off
 snapshot_interval 0
 locate off
 text_right %Y-%m-%d\n%T-%q
 text_changes on
 text_event %Y%m%d%H%M%S
 text_double on
 target_dir /home/javier/images
 snapshot_filename %v-%Y%m%d%H%M%S-snapshot
 jpeg_filename %v-%Y%m%d%H%M%S-%q
 movie_filename %v-%Y%m%d%H%M%S
 timelapse_filename %Y%m%d-timelapse
 webcam_port 8090
 webcam_quality 75
 webcam_motion on
 webcam_maxrate 24
 webcam_localhost on
 webcam_limit 0
 control_port 8091
 control_localhost on
 control_html_output on
 track_type 0
 track_auto off
 track_motorx 0
 track_motory 0
 track_maxx 0
 track_maxy 0
 track_iomojo_id 0
 track_step_angle_x 10
 track_step_angle_y 10
 track_move_wait 10
 track_speed 255
 track_stepsize 40
 quiet on
 sql_log_image on
 sql_log_snapshot on
 sql_log_mpeg off
 sql_log_timelapse off
 sql_query insert into security(camera, filename, frame, file_type,
 time_stamp, event_time_stamp) values('%t', '%f', '%q', '%n', '%Y-%m-%d
 %T', '%C')
 
 
 Thanks,
 
 Javier.
 
 
------------------------------------------------------------------------------
 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
 
 
  
 ------------------------------------------------------------------------------
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: 2
Date: Fri, 23 Jan 2015 13:25:11 -0500
From: Harlan Daneker <[email protected]>
Subject: Re: [Motion-user] Unit motion.service entered failed state
To: Motion discussion list <[email protected]>
Message-ID:
        <cac1wkithh8wtt3g3tufwap9q6xo9r6x5fnqra8dzx6knjfm...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

*./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]> 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 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]>
> 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]>
>> 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[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 
>>> [email protected]https://lists.sourceforge.net/lists/listinfo/motion-userhttp://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
>>
>>
>
>
> ------------------------------------------------------------------------------
> 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 8
*******************************************

Reply via email to