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. Motion 4.1 random crash with jpgutl_error_exit: Unsupported
marker type (Gordon)
----------------------------------------------------------------------
Message: 1
Date: Wed, 6 Dec 2017 10:15:37 -0600 (CST)
From: Gordon <mot...@res-g2.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: [Motion-user] Motion 4.1 random crash with jpgutl_error_exit:
Unsupported marker type
Message-ID:
<307572520.3037826.1512576937905.javamail.zim...@res-g2.com>
Content-Type: text/plain; charset="utf-8"
It looks like the Motion termination problem is separate from the picture
corruption problem, so I will start a new message here.
This is an Ubuntu 16.04 LTS system, a VM running on an ESXi host. It was using
Motion from the Ubuntu repository (3.12 I believe) until manually installing
the 4.1 deb. The system has a USB camera connected directly and monitors 2
Amcrest camera H264 feeds, for a total of 3 cameras.
The Amcrest threads use the new netcam_highres feature. I disabled creating the
preview picture a few days ago in case it was contributing to this problem (see
other message), so creating a picture is not the issue.
The system can run as long as 24 hours or more with recordings from all cameras
and no problems. The crash seems to occur right after a motion event, but it
could be at the very beginning of a new event that is not logged because of the
crash.
This last time it crashed was after a recording on an Amcrest camera. Based on
the timestamp the last video file appears to be already finalized before the
crash occurs, not during. So that is why I say the last movie file appearing in
syslog may not be the problem. The error looks like this:
[3:ml3] [CRT] [VID] vid_mjpegtoyuv420p: Corrupt image ... continue
[3:ml3] [ERR] [ALL] Above message repeats 3 times
[3:ml3] [ERR] [ALL] jpgutl_error_exit: Unsupported marker type 0xfb
The first line suggests this has something to do with Motion reading the
low-res stream from the Amcrest camera, in this case only for motion detection
because the netcam_highres feature is in use. That stream is 420p or 640*480.
Both the low-res and high-res streams are set to H264. MJPEG is an option on
these cameras but it's almost unusable. The image quality is poor regardless of
resolution or other settings, but that is a limitation of these cameras not
Motion.
After the crash Motion appears to start with no output error to "sudo service
motion start" but it never starts. There is no dead process running according
to "ps aux | grep motion" command. No new messages in syslog appear even if I
increase logging to 9. Only a reboot will fix it.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------
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 138, Issue 3
*******************************************
