My apologies. The problem is not the numbers of events but encoding of event. I've found this in event.log.
------
2009-11-06T18:33:29 ERROR Zope.SiteErrorLog http://bim.mts.com.ua:8080/zport/dmd/Events/evconsole_router
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.ZenUtils.Ext, line 107, in __call__
Module Products.ZenUtils.json, line 49, in json
Module simplejson, line 230, in dumps
Module simplejson.encoder, line 200, in encode
Module simplejson.encoder, line 260, in iterencode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xd0 in position 127: unexpected end of data
This cause problem with Event Console.
I've surrounded code in Products/ZenUtils/Ext.py in try except block and Event Console works now. (see attachment)
Of cource I can't see bgous events and the real solution lies match deeper.
Added:
In attachment script which fix bogus events in database.
Put it in your ~zenoss/zenoss directory, edit connection parameter to your mysql database and execute as python fix-utf-events.py
The problem in Products/ZenEvents/MySqlSendEvent.py when it calculates summary it simply trim's first 127 characters but with utf-8 encoded strings doing so is totally wrong and leads to bugs like this:
$python
Python 2.4.4 (#1, Oct 13 2009, 04:36:48)
[GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-56)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> print 'фвыа'[:3]
ф?
>>> print u'фвыа'[:3]
фвы
>>>
Message was edited by: pavelmart
