Just adding some few indexes to the database would help the load
enormously. I remember Ton Voon giving a speech at Nagios Konferenz
in germany last year, stating that analyzing the queries and then
creating the appropriate indexes boosted performance by as close
to 30% (querytimes
I was able to write to database and I already have setting to removed
the oldest data from database. So problem was somewhere else.
It seems to me ndo problems are often related to mysql performance...
On my smallish nagios test instance (50 hosts - 300 services), the
db weighs ~300 Mb / 1M
Hi
It seems to me ndo problems are often related to mysql performance...
On my smallish nagios test instance (50 hosts - 300 services), the
db weighs ~300 Mb / 1M records, and everything works fine since
I switched to innodb storage engine. Don't know whether it's really
related (table
It tasks at this moment are only:
- run nagios checks over NRPE - and collect data to DB (NDO)
- run (every 30 minutes) Shell script (it is slow but it was the fastest way
to write it) to read DB and update RRD files.
- cacti poller has minimal tasks (just check network stats over SNMP).
Hi
'about 4'oclock' is a typical start time for cron.daily, cron.weekly
and cron.monthly scripts, at least under Redhat and clones, all of
which ran recently. Is there anything interesting set to run in those?
Database backups, anything like that? You have free disk space on your
Hi
I've configured Nagios 2.6 with NDOUtils so time ago.
And everything was working well till today. About 4'oclock from some reason
Nagios stopped writing data to database.
When I am running Nagios without ndoutils (no changes on event broken). Nagios
is working well.
When I switch
No answers but some thoughts...
On Jun 2, 2008, at 8:11 AM, Marcin Praczko wrote:
Hi
I've configured Nagios 2.6 with NDOUtils so time ago.
And everything was working well till today. About 4'oclock from some
reason
Nagios stopped writing data to database.
'about 4'oclock' is a typical
I recently experienced something similar. The reason for it is that the
plugin option to discard old data was disabled, and my servicechecks table
grew to a size that MySQL didn't like. If you can't insert a record in that
table from PHPMyAdmin (or the command line), that may be your problem.
