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: newbie problems (vector457)
2. Re: newbie problems (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Wed, 12 Jun 2019 06:09:05 +1000
From: vector457 <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] newbie problems
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
I seem to be getting a lot of very short motion detected videos and lots
of these errors in the log overnight. Funny thing was last night when I
first got it working, for an hour or so whilst playing with it(testing
motion detect) I never saw even one of these.
/[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:00:02] ffmpeg_avcodec_log: Too
short data for FU-A H.264 RTP packet
[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:00:51] ffmpeg_avcodec_log:
corrupted macroblock 55 27 (total_coeff=-1)
[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:00:51] ffmpeg_avcodec_log: error
while decoding MB 55 27
[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:00:53] ffmpeg_avcodec_log: Too
short data for FU-A H.264 RTP packet
[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:01:23] ffmpeg_avcodec_log: Too
short data for FU-A H.264 RTP packet
[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:02:17] ffmpeg_avcodec_log: Too
short data for FU-A H.264 RTP packet
[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:02:21] ffmpeg_avcodec_log: Invalid
UE golomb code
[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:02:21] ffmpeg_avcodec_log: cbp too
large (3199971767) at 48 27
[4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:02:21] ffmpeg_avcodec_log: error
while decoding MB 48 27
[2:ml2:MyCam2] [INF] [EVT] [Jun 12 06:03:49] event_new_video: Source FPS 15/
On 11/6/19 7:18 pm, tosiara wrote:
> Your camera does not support TCP transport. Change your config to:
> netcam_use_tcp off
>
> On Tue, Jun 11, 2019 at 12:11 PM vector457 <[email protected]> wrote:
>> thanks please find attached..looks like a "transport" error?
>>
>> On 11/6/19 5:17 pm, tosiara wrote:
>>> Please provide full log with -d 7 command line switch
>>>
>>> On Mon, Jun 10, 2019 at 11:03 PM vector457 <[email protected]> wrote:
>>>> thanks for reply.
>>>> Strange. This morning i tried locahost:8080 and cam1 appeared so that
>>>> seems to be working now. Not sure why it wasnt last night. What was
>>>> interesting last night when it wasnt was that the Camera list was the
>>>> default Camera1 and not what I had renamed it too, as if localhost wasnt
>>>> using the conf file info. This morning its indeed using the renamed
>>>> cameras. Browser cache problem? Even tho I tried a number of refresh.
>>>> Browser running from the same machine as motion is.
>>>>
>>>> tried ffplay rtsp://user:[email protected]/onvif1, worked as expected.
>>>> tried restarting motion same problem
>>>>
>>>> [2:ml2:MyCam2] [NTC] [ALL] motion_loop: Thread exiting
>>>> [0:motion] [NTC] [ALL] main: Motion thread 2 restart
>>>> [0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 102 is from
>>>> /etc/motion/camera2.conf
>>>> [0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 102 Camera Name:
>>>> MyCam2 Service: rtsp:
>>>> [2:ml2:MyCam2] [NTC] [ALL] motion_init: Camera 102 started: motion
>>>> detection Enabled
>>>> [2:ml2:MyCam2] [NTC] [VID] vid_start: Opening Netcam RTSP
>>>> [2:ml2:MyCam2] [ERR] [NET] netcam_rtsp_open_context: Normal resolution:
>>>> Unable to open camera(MyCam2): Invalid data found when processing input
>>>> [2:ml2:MyCam2] [NTC] [NET] netcam_rtsp_cleanup: Normal resolution: Shut
>>>> down complete.
>>>> [2:ml2:MyCam2] [ERR] [VID] vid_start: Netcam RTSP failed to open
>>>> [2:ml2:MyCam2] [WRN] [ALL] motion_init: Could not fetch initial image from
>>>> camera
>>>>
>>>>
>>>> On 11/6/19 12:44 am, tosiara wrote:
>>>>
>>>> 1. You can't see the stream, probably, because you are trying from
>>>> another machine?
>>>> Try to set "stream_localhost off". Will that work?
>>>> I wonder how does it "say no cameras running"? Provide either log or
>>>> screenshot of the message
>>>>
>>>> 2. What URL is used for camera? Please provide the full log
>>>>
>>>> Do not use VLC for verification. Always test with "ffplay"
>>>>
>>>> On Mon, Jun 10, 2019 at 11:48 AM vector457 <[email protected]> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> installed motion on Ubuntu18
>>>>
>>>> I can see both of my two network cameras using VLC. they are old cams but
>>>> working.
>>>>
>>>> I have attached copy of motion.conf
>>>>
>>>> rtsp://user:[email protected]/11 {tenvis 1p391w or similar(no further
>>>> info)camera}
>>>>
>>>> rtsp://user:[email protected]/onvif1 {sricam SP007 or similar(no
>>>> further info on it)camera}
>>>>
>>>> I used camera1-dist.conf file for both, modifying name ,id and netcam url
>>>>
>>>> to create camera1.conf and camera2.conf.
>>>>
>>>> Problem 1 no local host view.
>>>>
>>>> I ran,mark@fatcat:~$ motion
>>>>
>>>> [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
>>>> /etc/motion/motion.conf
>>>> [0:motion] [NTC] [ALL] config_camera: Processing camera config file
>>>> /etc/motion/camera1.conf
>>>> [0:motion] [NTC] [ALL] motion_startup: Logging to syslog
>>>> [0:motion] [NTC] [ALL] motion_startup: Motion 4.2.2 Started
>>>> [0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
>>>> [0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
>>>> [0:motion] [NTC] [STR] webu_start_strm: Starting all camera streams on
>>>> port 8081
>>>> [0:motion] [NTC] [STR] webu_start_strm: Unable to start stream for camera 0
>>>> [0:motion] [NTC] [STR] webu_start_ctrl: Starting webcontrol on port 8080
>>>> [0:motion] [NTC] [STR] webu_start_ctrl: Unable to start MHD
>>>> [0:motion] [NTC] [ENC] ffmpeg_global_init: ffmpeg libavcodec version
>>>> 57.107.100 libavformat version 57.83.100
>>>> [0:motion] [NTC] [ALL] translate_init: Language: English
>>>> [0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 101 is from
>>>> /etc/motion/camera1.conf
>>>> [0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 101 Camera Name:
>>>> MyCam1 Service: rtsp:
>>>> [0:motion] [NTC] [ALL] main: Waiting for threads to finish, pid: 21036
>>>> [1:ml1:MyCam1] [NTC] [ALL] motion_init: Camera 101 started: motion
>>>> detection Enabled
>>>> [1:ml1:MyCam1] [NTC] [VID] vid_start: Opening Netcam RTSP
>>>> [1:ml1:MyCam1] [NTC] [NET] netcam_rtsp_connect: Normal resolution: Camera
>>>> (MyCam1) connected
>>>> [1:ml1:MyCam1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer
>>>> to 1 items
>>>> [2:nc2:MyCam1] [NTC] [NET] netcam_rtsp_handler: Normal resolution: Camera
>>>> handler thread [2] started
>>>> [2:nc2:MyCam1] [NTC] [NET] netcam_rtsp_connect: Normal resolution: Camera
>>>> (MyCam1) connected
>>>> [1:ml1:MyCam1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer
>>>> to 4 items
>>>> [1:ml1:MyCam1] [NTC] [EVT] event_newfile: File of type 8 saved to:
>>>> ./CAM01_101-01-20190610181942.mkv
>>>>
>>>> The mkv is indeed in my local dir and is capturing images as expected. But
>>>> yet when I go to web browser(firefox) localhost:8080 it says no cameras
>>>> running. I expected to see a live view?
>>>>
>>>> Problem 2
>>>>
>>>> camera 2 the onvif1 errors with
>>>>
>>>> Unable to open camera(MyCam2): Invalid data found when processing input
>>>> not sure why its works from this url in VLC.
>>>>
>>>>
>>>> thoughts?
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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...
------------------------------
Message: 2
Date: Wed, 12 Jun 2019 11:08:20 +0300
From: tosiara <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] newbie problems
Message-ID:
<CACHTdwTstu9_wvf7azReET=n1of83yvve4sbtdbkoxsiokz...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
If all of your recorded videos contained "garbage" and because of that
motion was triggered - then it is a common issue of using UDP
protocol. Network packet loss are causing this. The only reliable
solution is to use TCP portocol
On Tue, Jun 11, 2019 at 11:10 PM vector457 <[email protected]> wrote:
>
> I seem to be getting a lot of very short motion detected videos and lots of
> these errors in the log overnight. Funny thing was last night when I first
> got it working, for an hour or so whilst playing with it(testing motion
> detect) I never saw even one of these.
>
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:00:02] ffmpeg_avcodec_log: Too short
> data for FU-A H.264 RTP packet
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:00:51] ffmpeg_avcodec_log: corrupted
> macroblock 55 27 (total_coeff=-1)
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:00:51] ffmpeg_avcodec_log: error while
> decoding MB 55 27
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:00:53] ffmpeg_avcodec_log: Too short
> data for FU-A H.264 RTP packet
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:01:23] ffmpeg_avcodec_log: Too short
> data for FU-A H.264 RTP packet
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:02:17] ffmpeg_avcodec_log: Too short
> data for FU-A H.264 RTP packet
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:02:21] ffmpeg_avcodec_log: Invalid UE
> golomb code
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:02:21] ffmpeg_avcodec_log: cbp too
> large (3199971767) at 48 27
> [4:nc4:MyCam2] [INF] [ENC] [Jun 12 06:02:21] ffmpeg_avcodec_log: error while
> decoding MB 48 27
> [2:ml2:MyCam2] [INF] [EVT] [Jun 12 06:03:49] event_new_video: Source FPS 15
>
> On 11/6/19 7:18 pm, tosiara wrote:
>
> Your camera does not support TCP transport. Change your config to:
> netcam_use_tcp off
>
> On Tue, Jun 11, 2019 at 12:11 PM vector457 <[email protected]> wrote:
>
> thanks please find attached..looks like a "transport" error?
>
> On 11/6/19 5:17 pm, tosiara wrote:
>
> Please provide full log with -d 7 command line switch
>
> On Mon, Jun 10, 2019 at 11:03 PM vector457 <[email protected]> wrote:
>
> thanks for reply.
> Strange. This morning i tried locahost:8080 and cam1 appeared so that seems
> to be working now. Not sure why it wasnt last night. What was interesting
> last night when it wasnt was that the Camera list was the default Camera1 and
> not what I had renamed it too, as if localhost wasnt using the conf file
> info. This morning its indeed using the renamed cameras. Browser cache
> problem? Even tho I tried a number of refresh.
> Browser running from the same machine as motion is.
>
> tried ffplay rtsp://user:[email protected]/onvif1, worked as expected.
> tried restarting motion same problem
>
> [2:ml2:MyCam2] [NTC] [ALL] motion_loop: Thread exiting
> [0:motion] [NTC] [ALL] main: Motion thread 2 restart
> [0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 102 is from
> /etc/motion/camera2.conf
> [0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 102 Camera Name:
> MyCam2 Service: rtsp:
> [2:ml2:MyCam2] [NTC] [ALL] motion_init: Camera 102 started: motion detection
> Enabled
> [2:ml2:MyCam2] [NTC] [VID] vid_start: Opening Netcam RTSP
> [2:ml2:MyCam2] [ERR] [NET] netcam_rtsp_open_context: Normal resolution:
> Unable to open camera(MyCam2): Invalid data found when processing input
> [2:ml2:MyCam2] [NTC] [NET] netcam_rtsp_cleanup: Normal resolution: Shut down
> complete.
> [2:ml2:MyCam2] [ERR] [VID] vid_start: Netcam RTSP failed to open
> [2:ml2:MyCam2] [WRN] [ALL] motion_init: Could not fetch initial image from
> camera
>
>
> On 11/6/19 12:44 am, tosiara wrote:
>
> 1. You can't see the stream, probably, because you are trying from
> another machine?
> Try to set "stream_localhost off". Will that work?
> I wonder how does it "say no cameras running"? Provide either log or
> screenshot of the message
>
> 2. What URL is used for camera? Please provide the full log
>
> Do not use VLC for verification. Always test with "ffplay"
>
> On Mon, Jun 10, 2019 at 11:48 AM vector457 <[email protected]> wrote:
>
> Hi all,
>
> installed motion on Ubuntu18
>
> I can see both of my two network cameras using VLC. they are old cams but
> working.
>
> I have attached copy of motion.conf
>
> rtsp://user:[email protected]/11 {tenvis 1p391w or similar(no further
> info)camera}
>
> rtsp://user:[email protected]/onvif1 {sricam SP007 or similar(no further
> info on it)camera}
>
> I used camera1-dist.conf file for both, modifying name ,id and netcam url
>
> to create camera1.conf and camera2.conf.
>
> Problem 1 no local host view.
>
> I ran,mark@fatcat:~$ motion
>
> [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
> /etc/motion/motion.conf
> [0:motion] [NTC] [ALL] config_camera: Processing camera config file
> /etc/motion/camera1.conf
> [0:motion] [NTC] [ALL] motion_startup: Logging to syslog
> [0:motion] [NTC] [ALL] motion_startup: Motion 4.2.2 Started
> [0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
> [0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
> [0:motion] [NTC] [STR] webu_start_strm: Starting all camera streams on port
> 8081
> [0:motion] [NTC] [STR] webu_start_strm: Unable to start stream for camera 0
> [0:motion] [NTC] [STR] webu_start_ctrl: Starting webcontrol on port 8080
> [0:motion] [NTC] [STR] webu_start_ctrl: Unable to start MHD
> [0:motion] [NTC] [ENC] ffmpeg_global_init: ffmpeg libavcodec version
> 57.107.100 libavformat version 57.83.100
> [0:motion] [NTC] [ALL] translate_init: Language: English
> [0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 101 is from
> /etc/motion/camera1.conf
> [0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 101 Camera Name:
> MyCam1 Service: rtsp:
> [0:motion] [NTC] [ALL] main: Waiting for threads to finish, pid: 21036
> [1:ml1:MyCam1] [NTC] [ALL] motion_init: Camera 101 started: motion detection
> Enabled
> [1:ml1:MyCam1] [NTC] [VID] vid_start: Opening Netcam RTSP
> [1:ml1:MyCam1] [NTC] [NET] netcam_rtsp_connect: Normal resolution: Camera
> (MyCam1) connected
> [1:ml1:MyCam1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to
> 1 items
> [2:nc2:MyCam1] [NTC] [NET] netcam_rtsp_handler: Normal resolution: Camera
> handler thread [2] started
> [2:nc2:MyCam1] [NTC] [NET] netcam_rtsp_connect: Normal resolution: Camera
> (MyCam1) connected
> [1:ml1:MyCam1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to
> 4 items
> [1:ml1:MyCam1] [NTC] [EVT] event_newfile: File of type 8 saved to:
> ./CAM01_101-01-20190610181942.mkv
>
> The mkv is indeed in my local dir and is capturing images as expected. But
> yet when I go to web browser(firefox) localhost:8080 it says no cameras
> running. I expected to see a live view?
>
> Problem 2
>
> camera 2 the onvif1 errors with
>
> Unable to open camera(MyCam2): Invalid data found when processing input
> not sure why its works from this url in VLC.
>
>
> thoughts?
>
> _______________________________________________
> 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
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
>
> _______________________________________________
> 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
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 156, Issue 26
********************************************
