The infamous Corrupt JPEG problem...

[McFuzz]

Gents,

I have a Foscam FI8904W I just got, and a couple additional Foscam camera on their way (different model). I too receive the infamous 'Corrupt JPEG data: 1 extraneous bytes before marker 0xd9' error message that keeps flooding my logs.

I've tried the trick found here:

http://www.zoneminder.com/forums/viewto ... 29&t=19514

And here:

http://lachlanmiskin.com/blog/2012/06/2 ... rker-0xd9/


Alas - no success... my logs are still being flooded.


Any idea of what I can do to stop it from attacking me so mercilessly?

[McFuzz]

Here's something interesting... I used the guide on the wiki to install Zoneminder on top of Debian 6.0 (http://www.zoneminder.com/wiki/index.ph ... mbre_2011)

I also applied the performance patch...

On my end, zm is at /usr/src/zm/src so the zm_jpeg.cpp file path is /usr/src/zm/src/zm_jpeg.cpp - however, commenting out the function that causes the logs STILL has no effect; even if I change the line items! It's as if ZM on my end reads this off another file!

I am trying to find where this may be, but I think I will just give up... my load averages are still pretty darn low.

[McFuzz]

Update: works fine now - please close

Thanks

[Carrier82]

In case someone else has the same problem, what was the solution?

[McFuzz]

In case someone else has the same problem, what was the solution?

Well... it was a bit unconventional: I have an 'odd' install; I followed the wiki article for installing ZoneMinder on Debian 6 and it's done differently than with Ubuntu. I also have the performance patch installed. When I edited the zm_jpeg.cpp file and recompiled, it broke zoneminder - and it broke it hard. My only recourse was to revert to a snapshot of the Debian VM that is running Zoneminder, then modify the zm_jpeg.cpp file in the performance patch tarball, then install it - and that made the log messages disappear.

So it's not like I solved the firmware issue - I shushed the logs.