Garbeled Image on 1.22.0

wmoore · Post by **wmoore** » Tue Feb 28, 2006 8:24 pm

Have had a solid 1.21.4 running for some time. Decided to upgrade to 1.22.0. I did a drop database ZM; in order to start fresh with a clean system. No other changes in Hardware/Software

All went quite well, but now having an issue with both FPS and mixed up (garbeled) images, but only for 1 camera. (Axis 2420 IR) The garbeled images are not consistant. Maybe 50 incidents in 20 mins.... each one causes an event to be registered..

Maybe I just need some help tuning the implementation... Not sure where to look.

FYI:

<cam_IP>/cgi-bin/mjpg/video.cgi?resolution=352x240
24 Bit Color

Note: The 2420 IR is a B&W camera, but has never successfully with run (on any version) with 8 bit grayscale... I have assumed that the camera must output a color stream with a black and white image.

Also Note: The problem can be imporved (fewer garbled frames), but not fixed by disabeling (removing the check box) ZM_NETCAM_REGEXPS.

1.22.0 also recored most of these events as motion, but some as "signal" events.

Post by **zoneminder** » Fri Mar 03, 2006 4:46 pm

Are you saying you are getting an image that is a mixture of snaps from different cameras?

If so I can't really see a way that this could happen unless someone they are writing to the same shared memory area, which should be impossible. Do you still the problem if you shut one of the cams down?

wmoore · Post by **wmoore** » Fri Mar 03, 2006 5:25 pm

Sorry for the confustion. The image parts are all from the same camera. Aditionally, the issue occures evin when there is a single camera in operation.

This camera has been working perfectly with previous versions of ZM for several years now. Because this is the first time I have not done an upgrade, but a fresh install, perhaps there is a setting that i have neglected.

any ideas are welcome.

See aditional expamples:

wmoore · Post by **wmoore** » Sat Mar 04, 2006 2:21 pm

Interesting finding:

When I limit the frame rate on that monitor, evin to a very high number (15.0 FPS), the frequency of the episodes is increased. No limiting (0.00 FPS), it still occures, but at a much much less frequent rate. Note, this monitor is reporting between 13.33 and 40.00 FPS when it is running clean. Remember this is a Network Cam...? Possible?

zmdc.log snipp from an episode:

Corrupt JPEG data: 31 extraneous bytes before marker 0xd9
Corrupt JPEG data: 38 extraneous bytes before marker 0xdb
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: 27 extraneous bytes before marker 0xd9
Corrupt JPEG data: 27 extraneous bytes before marker 0xd9
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Invalid JPEG file structure: two SOI markers
03/04/06 09:11:33.737139 zmdc[22858].ERR ['zmc -m 1' crashed, exit status 1]
03/04/06 09:11:33.737886 zmdc[22858].INF [Starting pending process, zmc -m 1]
03/04/06 09:11:33.740341 zmdc[22858].INF ['zmc -m 1' starting at 06/03/04 09:11:33, pid = 24230]
03/04/06 09:11:33.742760 zmdc[24230].INF ['zmc -m 1' started at 06/03/04 09:11:33]
Corrupt JPEG data: premature end of data segment
Invalid JPEG file structure: two SOI markers
03/04/06 09:11:36.141338 zmdc[22858].ERR ['zmc -m 1' crashed, exit status 1]
03/04/06 09:11:41.090850 zmdc[22858].INF [Starting pending process, zmc -m 1]
03/04/06 09:11:41.093376 zmdc[22858].INF ['zmc -m 1' starting at 06/03/04 09:11:41, pid = 24267]
03/04/06 09:11:41.096227 zmdc[24267].INF ['zmc -m 1' started at 06/03/04 09:11:41]
Corrupt JPEG data: 31 extraneous bytes before marker 0xd9
Corrupt JPEG data: 26 extraneous bytes before marker 0xd9
Corrupt JPEG data: 117 extraneous bytes before marker 0xd9
Corrupt JPEG data: 30 extraneous bytes before marker 0xd9
Corrupt JPEG data: 30 extraneous bytes before marker 0xd9
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: 83 extraneous bytes before marker 0xd9
Corrupt JPEG data: 83 extraneous bytes before marker 0xd9
Corrupt JPEG data: 40 extraneous bytes before marker 0xdb
Corrupt JPEG data: 31 extraneous bytes before marker 0xd9
Corrupt JPEG data: 31 extraneous bytes before marker 0xd9
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment

Should I reconfigure the shared memory address? If so what is the proceedure? I know how to increase it, but I am unsure about how to move it?

wiggsdannyboy · Post by **wiggsdannyboy** » Mon Mar 06, 2006 6:59 am

I had similar pictures to those when I attempted to use XAWTV without turning off the ZM server.

wmoore · Post by **wmoore** » Mon Mar 06, 2006 10:45 pm

Wish it were that easy... Unfortunatly, this is a headless, Xless, system. Aditionally, it only supports IP cameras... No fram card.

Post by **zoneminder** » Tue Mar 07, 2006 11:06 pm

Have you tried changing the ZM_NETCAM_REGEXPS setting?

wmoore · Post by **wmoore** » Wed Mar 08, 2006 3:12 am

Yep. Happens with or without ZM_NETCAM_REGEXPS setting. Evin updated the libpcre implimentation to 6.x

The system is a probably underpowered. It is a Sun RaQ 550 PIII 1.2Ghz/256M Ram.

Under the previous release the load was usualy .3 and spiked to 1.5. This release definatly gets more out of the netcams... Very high frame rates. I.E. The Axis 2420 can do 40 - 50 FPS. The load is also 2.5 - 3.0 and spikes above that.

Interestingly, the problem is worse if I throttle the FPS on the Monitor config screen.

I am starting to believe this is a buffer over run issue. ZMC and ZMU getting weird with limited memory. I ordered aditonal RAM. Will report back on its impact. Any other ideas are welcome.

-WAM

jameswilson · Post by **jameswilson** » Wed Mar 08, 2006 7:41 am

try limiting the fps in the axis setup to say 5

jameswilson · Post by **jameswilson** » Tue Mar 14, 2006 5:15 pm

Just for giggles im gettingt his too. Its on a 4200+ X2 with a gig of ram and the images go funny colours from time to time. They didnt on the previous recorder that was a 1.21.3.
All net cams are axis 206

wmoore · Post by **wmoore** » Wed Mar 15, 2006 2:08 am

Yep...Same here.

I installed 2G Ram today. Plenty of shared memory now.

The problem persists... Also experiening a number of "signal" events, but only on the Axis camera. Like James Wilson, the previous release was rock solid. Begining to think that there is somthing about the Axis cameras that is not liking this version.

-WAM

jameswilson · Post by **jameswilson** » Wed Mar 15, 2006 2:54 pm

this is getting worse as now its doing this

It was set to mocord and creating very short events so i set to record thinking it would help. It didnt. I have restarted zm to see if this helps.

This has done this twice now and i have to restart the service to stop it. I also have the funny images as above on my ip cameras but i dont think i do on the local cams. All logs are available but it appears it juist stops the event then restarts with no crashing. Then as the events rise ext2 cant handle it and it cant write to disk anymore?

I need some advice on this

James

jameswilson · Post by **jameswilson** » Wed Mar 15, 2006 7:43 pm

a restart stops the event issue but i still get the odd image error. After the server has been up for a day and a half it starts creating thousands of events

wmoore · Post by **wmoore** » Wed Mar 15, 2006 8:10 pm

When it does begin to happen, does you zmdc.log look roughly like this?

03/15/06 14:52:43.449822 zmdc[5788].ERR ['zmc -m 1' crashed, exit status 1]
03/15/06 14:52:57.112187 zmdc[5788].INF ['zmc -m 1' starting at 06/03/15 14:52:57, pid = 15782]
03/15/06 14:52:57.124505 zmdc[15782].INF ['zmc -m 1' started at 06/03/15 14:52:57]
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: 20 extraneous bytes before marker 0xd8
Invalid JPEG file structure: two SOI markers
03/15/06 14:53:12.373150 zmdc[5788].ERR ['zmc -m 1' crashed, exit status 1]
03/15/06 14:53:27.823511 zmdc[5788].INF ['zmc -m 1' starting at 06/03/15 14:53:27, pid = 15821]
03/15/06 14:53:27.825556 zmdc[15821].INF ['zmc -m 1' started at 06/03/15 14:53:27]
Corrupt JPEG data: 34 extraneous bytes before marker 0xdb
Corrupt JPEG data: 16 extraneous bytes before marker 0xd9
Corrupt JPEG data: 10 extraneous bytes before marker 0xd9
Corrupt JPEG data: bad Huffman code
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: 15 extraneous bytes before marker 0xd9
Corrupt JPEG data: 5 extraneous bytes before marker 0xd9
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Invalid JPEG file structure: two SOI markers
03/15/06 14:53:41.358531 zmdc[5788].ERR ['zmc -m 1' crashed, exit status 1]
03/15/06 14:53:48.551659 zmdc[5788].INF ['zmc -m 1' starting at 06/03/15 14:53:48, pid = 15846]
03/15/06 14:53:48.553655 zmdc[15846].INF ['zmc -m 1' started at 06/03/15 14:53:48]
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: 2 extraneous bytes before marker 0xd9
Corrupt JPEG data: bad Huffman code
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: 3 extraneous bytes before marker 0xd9
Corrupt JPEG data: 4 extraneous bytes before marker 0xd9
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: 4 extraneous bytes before marker 0xd9
Corrupt JPEG data: 20 extraneous bytes before marker 0xd9
Corrupt JPEG data: premature end of data segment
Invalid JPEG file structure: two SOI markers
03/15/06 14:54:24.498238 zmdc[5788].ERR ['zmc -m 1' crashed, exit status 1]

messages :

Mar 15 14:54:39 Security zmc_m1[15869]: INF [Starting Capture]
Mar 15 14:54:39 Security zma_m1[5819]: INF [Infra-Red: 227688 - Gone into alarm state]
Mar 15 14:54:40 Security zma_m1[5819]: INF [Infra-Red: 227692 - Gone into alert state]
Mar 15 14:54:42 Security zma_m1[5819]: INF [Infra-Red: 227697 - Left alarm state (4551) - 14(4) images]
Mar 15 14:54:50 Security zma_m2[5831]: INF [Auto resuming at count 357214]
Mar 15 14:54:56 Security zmc_m1[15869]: ERR [Found unsupported content type '?x^XA^Yy^XA^Iz^XA\210z^XA?{^XAf|^XA?|^XAP}^XA\207~^XA\222~^XA?\177^XA?\177^XA?\177^XA^R\200^XA2\201^XA1\202^XAe\202^XAi\202^XAM\203^XA?\203^XA?\203^XA?\203^XA?\205^XA?\205^XA^K\206^XA?\206^XAt\207^XA?\207^XA?\207^XA'\210^XA\206\210^XA?\210^XA\222\211^XA^^\212^XA?\212^XAG\213^XAK\213^XAt\213^XA?\213^XA?\215^XA?\217^XA^\\221^XA}\221^XA \222^XA']
Mar 15 14:55:18 Security zmc_m1[15869]: INF [Infra-Red: 1000 - Capturing at 25.64 fps]
Mar 15 14:55:29 Security zmc_m1[15869]: ERR [Found unsupported content type 'Content-Type: image/jpeg']
Mar 15 14:55:32 Security zma_m1[5819]: INF [Infra-Red: 228000 - Processing at 4.22 fps]
Mar 15 14:55:58 Security zmc_m1[15869]: INF [Infra-Red: 2000 - Capturing at 25.00 fps]
Mar 15 14:56:40 Security zmc_m1[15869]: ERR [Found unsupported content type '']
Mar 15 14:56:40 Security zma_m1[5819]: WAR [Signal Lost]
Mar 15 14:56:40 Security zma_m1[5819]: INF [Infra-Red: 228411 - Gone into alarm state]
Mar 15 14:56:40 Security zma_m1[5819]: WAR [Signal Reacquired]
Mar 15 14:56:40 Security zma_m1[5819]: INF [Infra-Red: 228412 - Gone into alarm state]
Mar 15 14:56:41 Security zma_m1[5819]: INF [Infra-Red: 228413 - Gone into alert state]
Mar 15 14:56:42 Security zma_m1[5819]: INF [Infra-Red: 228418 - Left alarm state (4553) - 11(1) images]
Mar 15 14:56:45 Security zmc_m1[15869]: INF [Infra-Red: 3000 - Capturing at 21.28 fps]
Mar 15 14:57:22 Security zmc_m1[15869]: INF [Infra-Red: 4000 - Capturing at 27.03 fps]
Mar 15 14:57:59 Security zmc_m1[15869]: INF [Infra-Red: 5000 - Capturing at 27.03 fps]
Mar 15 14:58:19 Security zma_m1[5819]: INF [Infra-Red: 229000 - Processing at 5.99 fps]
Mar 15 14:58:38 Security zmc_m1[15869]: INF [Infra-Red: 6000 - Capturing at 25.64 fps]

Interestingly, at night if I turn off the IR illuminator, a black frame is stable. no problems. but as soon as there is any light (detail in the frame) it gets squerly

Also interestng, above where the "Content-Type: image/jpeg" is found... Strange because the get string is definatly motion jpeg ("/cgi-bin/mjpg/video.cgi?resolution=352x240").

I dont know what else to try. Near as I can see there are three of us having issues, but only with AXIS cameras, and only on 1.22.0. The upgrade seems to have had no ill affects on a Panasonic IP cam also on the system.

jameswilson · Post by **jameswilson** » Wed Mar 15, 2006 8:16 pm

are you having the event issue to on mocord/record?

ZoneMinder Forums

Garbeled Image on 1.22.0

Garbeled Image on 1.22.0

Is another app using the cam?