Hi Pavel,
Zenstatus will consume as much CPU as it can as it pings 50 or so
devices in parallel. It should stop after cycling through all known
devices and cpu usage should drop to zero.
How long does this take:
$ zenstatus run -v 10
That's one cycle. If your cycle time is one minute and the command
above takes longer than 60 seconds, increase your cycle time.
You can increase the max rows on the status table like this:
$ mysql -u $MYSQLUSER -p$MYSQLPASS events
mysql> alter table status max_rows = 0;
If you want the events to persist, change the engine type for the table:
mysql > alter table status engine = innodb;
You may see decreased performance on this table with these changes.
-Eric
Chlupáček Pavel wrote:
Anyone had an idea why? It is after a while (let's say about the 2-3 h of
operation)...
Also having issu that live logs table can hold only about 3000 events, than zentrap and other "events" related processes logs that status table is full. I wonder if there is any way how to increase it to let's say bigger number (testing purposes, don't wat to get the logs looged to history for now)
P.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
