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. Possible bug in Motion (David Powell)
2. Re: Possible bug in Motion (David Powell)
----------------------------------------------------------------------
Message: 1
Date: Wed, 20 Feb 2019 09:12:50 -0500
From: David Powell <[email protected]>
To: Motion discussion list <[email protected]>
Subject: [Motion-user] Possible bug in Motion
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
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
/
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Wed, 20 Feb 2019 09:17:01 -0500
From: David Powell <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Possible bug in Motion
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
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
> [email protected]
> 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...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 152, Issue 17
********************************************
