Gents!

After several weeks of Rdmelin's nice distro, I get weirdness happening as per the attached pic. trying to view the event throws an error with changing code, but the code is similiar to a color hex number. This has happened previously and i ended up reinstalling.
I'd love to hear anyone's opinion of how to fix this one!
-Lee

hi parabolix!
I had some times ago similar problem....
in log was "not enough space on device" ...but I have 78 Gb free space!!
I think - it's - limit for our filesystem (I am use ReiserFS on zmlarch). (but i'm not sure).
Actual question - how to resolve this problem?

I fixed my own problem, but wanted to post it for someone elses benefit:

the events table had become corrupted, and is easily fixed by stopping ZM and repairing it via http://localhost/PhpMyAdmin/

Do you have a UPS on the machine, I had a similar issue, turns out someone
unplugged the machine, appears it was in mid event capture mangled the db,
ran mysqlcheck and fixed it, was supposed to be on a good solid backed circuit
but some one was in the cable closet installing other gear and unplugged the
whole thing, now there is a UPS up there and all of the plugs are enclosed,
if they pull the plug on the UPS to change something, there is 3 hours of UPS
backup there. Now to get the system to toss some sort of UPS message on
the app just in case it happens again...

This looks very much like something that has been happening to me. It seems that when a monitor (camera) reaches 32000 events my viewer window shows the same information that is shown in the first post of this thread.
----
139706 New Event 2010-10-21 07:34:22 0.00 null/null 0/0 X
----

This goes on for many lines. ...as long as I let it run and events pile up.

I found that if I disable the monitor and make a new one (on the same camera), it works fine. However, it will also work temporarily once I drop the events to below 32000, but will stop and record null again once the events number reaches 32000.

So my assumption is this is either a limitation of MySQL's tables or the file system used.

My current stats are:
Ubuntu 9.10
P4 @ 2.66GHz
1GB RAM
500GB HDD (40GB for OS & 450GB mounted on /var/cache/zoneminder)
* Linux EXT3 partition type
ZONEMINDER 1.24.1

I don't know the definite answer here but I'm sure it has to do with the number of events hitting 32000 in either the db or the fs.

Does anyone have a fix or workaround for this?

I know this is a late response, but I recently ran into the same issue.

The problem is ext3 can only have about 32000 folders within a folder (it is a hardcoded limit). Since zoneminder makes a new folder for every event, it runs into errors trying to make new events.

The simple solution is switch the filesystem to ext4, which handles over 32000 no problem.

Of course, moving all of your recordings off your server while you reformat the drive is probably a pain (it is for me!)