I am getting the following error when trying to send an event to our
zenoss installation:
2006-11-07 11:50:32 ERROR zen.ZenXEvent: (1114, "The table 'status' is
full")
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenEvents/zenxevent.py", line 67, in
doHandleRequest
retval = method(*data)
File "/usr/local/zenoss/Products/ZenEvents/EventManagerBase.py", line
763, in sendEvents
self.sendEvent(event, db)
File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line
92, in sendEvent
raise ZenBackendFailure(str(e))
ZenBackendFailure: (1114, "The table 'status' is full")
I came across a mention of this problem on the zenoss mailing list
archives but no clear solution. In that thread somone had mentioned
going into mysql and issuing
/alter table status max_rows = 0;/
in the events database. This did not fix the problem, nor did it have
any noticable effect at all.
http://lists.zenoss.org/pipermail/zenoss-users/2006/002151.html is the
posting I reference.
I figured out that one of our boxes had sent over 2,500 error messages
to zenoss because of a component that was improperly removed. Once I
deleted that server from the zenoss setup I stopped receiving the "table
status is full" error and events work fine again.
My question is, how can I get it to retain an amount of status messages
that is only limited by disk space? If one of our devices goes haywire
and sends enough status messages to fill the status table then zenoss
becomes effectively useless for receiving valid status messages from
other machines. Any solutions for this? Am I just missing something obvious?
I'm using zenoss 0.23.0
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
