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: Possible bug in Motion (Zan Thorn)
2. Can't get motion to work as before (Roman)
3. Re: Possible bug in Motion (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Wed, 20 Feb 2019 07:20:39 -0700
From: Zan Thorn <zanth...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Possible bug in Motion
Message-ID:
<CAAfdRzZDzwP_WbHj0+gMt9wBNkikuEqPzdXGWXAzrs26=op...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
You can report the bug/issue on the Github page:
https://github.com/Motion-Project/motion/issues
On Wed, Feb 20, 2019 at 7:18 AM David Powell <da...@depowell.com> wrote:
> Oh yes, the version I'm running is Motion 4.2.1+gitUNKNOWN
> David
>
> On 2/20/19 9:12 AM, David Powell wrote:
>
> I believe I may have found a bug in Motion, but I'm not sure how to
> officially report it.
>
> I have it running on a RPi with Apache and MySQL, using one camera.
> Everything works fine unless I send a malformed URL, which results in a
> segmentation fault that causes Motion to abend. The URL is routed through a
> reverse proxy on Apache.
>
> Relevant Apache config:
>
>
> *ProxyPass /homecam http://localhost:1525 <http://localhost:1525>
> ProxyPassReverse /homecam http://localhost:1525 <http://localhost:1525>*
>
> Relevant Motion config:
>
> *stream_port 1525*
> *stream_localhost off*
>
> If I open a browser on a different computer and browse to
> *http://motionserver/homecam/
> <http://motionserver/homecam/>* I get a nice video stream from the
> camera. However, if I browse to *http://motionserver/homecam/
> <http://motionserver/homecam/>1* then the segfault occurs.
>
> Here are the last few lines from the level-9 log file before the segfault
> occurs:
>
> *[1:ml1] [NTC] [ALL] [Feb 20 02:56:21] motion_init: Camera 0 started:
> motion detection Enabled*
> *[1:ml1] [NTC] [VID] [Feb 20 02:56:21] vid_start: Opening Netcam RTSP*
> *[1:ml1] [INF] [NET] [Feb 20 02:56:21] netcam_rtsp_set_parms: Setting up
> Normal resolution stream.*
> *[1:ml1] [INF] [NET] [Feb 20 02:56:21] netcam_rtsp_set_path: Setting up
> rtsp via ffmpeg netcam*
> *[1:ml1] [INF] [NET] [Feb 20 02:56:21] netcam_rtsp_set_rtsp: Normal
> resolution: Setting rtsp transport to tcp*
> *[1:ml1] [INF] [NET] [Feb 20 02:56:22] netcam_rtsp_open_context: Normal
> resolution: Opened camera((null))*
> *[1:ml1] [INF] [ENC] [Feb 20 02:56:26] ffmpeg_avcodec_log: deprecated
> pixel format used, make sure you did set range correctly*
> *[1:ml1] [DBG] [NET] [Feb 20 02:56:26] netcam_check_buffsize: expanding
> buffer from [0/0] to [0/1384448] bytes.*
> *[1:ml1] [DBG] [NET] Above message repeats 1 times*
> *[1:ml1] [DBG] [NET] [Feb 20 02:56:26] netcam_check_buffsize: expanding
> buffer from [1382400/1384448] to [1382400/2764800] bytes.*
> *[1:ml1] [NTC] [NET] [Feb 20 02:56:26] netcam_rtsp_connect: Normal
> resolution: Camera ((null)) connected*
> *[1:ml1] [DBG] [NET] [Feb 20 02:56:26] netcam_check_buffsize: expanding
> buffer from [1382400/1384448] to [1382400/2764800] bytes.*
> *[1:ml1] [NTC] [ALL] [Feb 20 02:56:26] image_ring_resize: Resizing
> pre_capture buffer to 1 items*
> *[2:nc2] [NTC] [NET] [Feb 20 02:56:26] netcam_rtsp_handler: Normal
> resolution: Camera handler thread [2] started*
> *[2:nc2] [INF] [NET] [Feb 20 02:56:27] netcam_rtsp_open_context: Normal
> resolution: Opened camera((null))*
> *[0:cn0] [DBG] [STR] [Feb 20 02:56:28] webu_parseurl: Sent url:
> /1/current/?rnd=0.3595820748485028*
> *[0:cn0] [DBG] [STR] [Feb 20 02:56:28] webu_parseurl: Decoded url:
> /1/current/?rnd=0.3595820748485028*
> *[0:cn0] [DBG] [STR] [Feb 20 02:56:28] webu_parseurl: camid: >1< cmd1:
> >current< cmd2: >?rnd=0.3595820748485028< parm1:>< val1:>< parm2:>< val2:><*
>
> I captured this log whilst trying to debug the segfault, so the URL it
> shows is a bit different from what I mentioned above. I narrowed it down
> to */homecam/1 *and still got it*. *The URL works fine on my other
> Motion server, but it has more than one camera.
>
>
> *David *
>
>
>
>
> _______________________________________________
> Motion-user mailing
> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Thu, 21 Feb 2019 08:14:38 +0100
From: Roman <qwasi_1...@yahoo.de>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] Can't get motion to work as before
Message-ID: <39494807-3754-4e85-b0be-c7f1f370b...@yahoo.de>
Content-Type: text/plain; charset="utf-8"
Hi there,
I was running motion for about a year without any trouble. Now I had to switch
to a new server and I can't get it working again :-(
I'm using latest version 4.2.2 on bionic, installed with builddeb.sh as before.
I'm using the same config but it is not working.
Were there any changes to the palettes being used?
My camera provides YUYV and MJPEG, but with MJPEG I always get corrupt
pictures, so I had it working with YUYV (palette 15).
With YUYV I can't get any result now, only with MJPEG.
So my question is, were there any changes to palette 15?
I'm able to post logs when at home this evening, so pls tell me what I should
set logging to.
I already tried different USB ports and reverted to motion 4.1
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Thu, 21 Feb 2019 10:15:59 +0200
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Possible bug in Motion
Message-ID:
<CACHTdwSPr8YqNXY-EmmLApY2RbUCjuBCsOEMM_PU+=8vhia...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
The bug has been just registered by Mr-Dave:
https://github.com/Motion-Project/motion/issues/916
On Wed, Feb 20, 2019 at 4:21 PM Zan Thorn <zanth...@gmail.com> wrote:
>
> You can report the bug/issue on the Github page:
> https://github.com/Motion-Project/motion/issues
>
> On Wed, Feb 20, 2019 at 7:18 AM David Powell <da...@depowell.com> wrote:
>>
>> Oh yes, the version I'm running is Motion 4.2.1+gitUNKNOWN
>>
>> David
>>
>> On 2/20/19 9:12 AM, David Powell wrote:
>>
>> I believe I may have found a bug in Motion, but I'm not sure how to
>> officially report it.
>>
>> I have it running on a RPi with Apache and MySQL, using one camera.
>> Everything works fine unless I send a malformed URL, which results in a
>> segmentation fault that causes Motion to abend. The URL is routed through a
>> reverse proxy on Apache.
>>
>> Relevant Apache config:
>>
>> ProxyPass /homecam http://localhost:1525
>> ProxyPassReverse /homecam http://localhost:1525
>>
>> Relevant Motion config:
>>
>> stream_port 1525
>> stream_localhost off
>>
>> If I open a browser on a different computer and browse to
>> http://motionserver/homecam/ I get a nice video stream from the camera.
>> However, if I browse to http://motionserver/homecam/1 then the segfault
>> occurs.
>>
>> Here are the last few lines from the level-9 log file before the segfault
>> occurs:
>>
>> [1:ml1] [NTC] [ALL] [Feb 20 02:56:21] motion_init: Camera 0 started: motion
>> detection Enabled
>> [1:ml1] [NTC] [VID] [Feb 20 02:56:21] vid_start: Opening Netcam RTSP
>> [1:ml1] [INF] [NET] [Feb 20 02:56:21] netcam_rtsp_set_parms: Setting up
>> Normal resolution stream.
>> [1:ml1] [INF] [NET] [Feb 20 02:56:21] netcam_rtsp_set_path: Setting up rtsp
>> via ffmpeg netcam
>> [1:ml1] [INF] [NET] [Feb 20 02:56:21] netcam_rtsp_set_rtsp: Normal
>> resolution: Setting rtsp transport to tcp
>> [1:ml1] [INF] [NET] [Feb 20 02:56:22] netcam_rtsp_open_context: Normal
>> resolution: Opened camera((null))
>> [1:ml1] [INF] [ENC] [Feb 20 02:56:26] ffmpeg_avcodec_log: deprecated pixel
>> format used, make sure you did set range correctly
>> [1:ml1] [DBG] [NET] [Feb 20 02:56:26] netcam_check_buffsize: expanding
>> buffer from [0/0] to [0/1384448] bytes.
>> [1:ml1] [DBG] [NET] Above message repeats 1 times
>> [1:ml1] [DBG] [NET] [Feb 20 02:56:26] netcam_check_buffsize: expanding
>> buffer from [1382400/1384448] to [1382400/2764800] bytes.
>> [1:ml1] [NTC] [NET] [Feb 20 02:56:26] netcam_rtsp_connect: Normal
>> resolution: Camera ((null)) connected
>> [1:ml1] [DBG] [NET] [Feb 20 02:56:26] netcam_check_buffsize: expanding
>> buffer from [1382400/1384448] to [1382400/2764800] bytes.
>> [1:ml1] [NTC] [ALL] [Feb 20 02:56:26] image_ring_resize: Resizing
>> pre_capture buffer to 1 items
>> [2:nc2] [NTC] [NET] [Feb 20 02:56:26] netcam_rtsp_handler: Normal
>> resolution: Camera handler thread [2] started
>> [2:nc2] [INF] [NET] [Feb 20 02:56:27] netcam_rtsp_open_context: Normal
>> resolution: Opened camera((null))
>> [0:cn0] [DBG] [STR] [Feb 20 02:56:28] webu_parseurl: Sent url:
>> /1/current/?rnd=0.3595820748485028
>> [0:cn0] [DBG] [STR] [Feb 20 02:56:28] webu_parseurl: Decoded url:
>> /1/current/?rnd=0.3595820748485028
>> [0:cn0] [DBG] [STR] [Feb 20 02:56:28] webu_parseurl: camid: >1< cmd1:
>> >current< cmd2: >?rnd=0.3595820748485028< parm1:>< val1:>< parm2:>< val2:><
>>
>> I captured this log whilst trying to debug the segfault, so the URL it shows
>> is a bit different from what I mentioned above. I narrowed it down to
>> /homecam/1 and still got it. The URL works fine on my other Motion server,
>> but it has more than one camera.
>>
>> David
>>
>>
>>
>>
>> _______________________________________________
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> _______________________________________________
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 152, Issue 18
********************************************
