Nagios Support Forum

Have you seen any similar problems with other installations, and have any tips to prevent this from happening again in the future? We saw something like this in a few mysql tables, but this is the first time we've seen it in a postgresql table. We did some adjustments to our db maintenance script, ...

I ran the commands you mentioned. Here are the results: select count(*) from xi_commands; took one or two seconds, result 0 (1 row) select count(*) from xi_events; took about 15-20 seconds, result 656 (1 row) select count(*) from xi_meta; took nearly 30 seconds, results 719 (1 row) select count(*) f...

Running dbmaint on our server produces the same kind of output as i copied into my post of january 6. No mention of MIBs in the output, so the problem doesn't seem to be related to that. There is a bit of disk i/o on the system, but since neither 'top' nor 'vmstat' reports any waiting on i/o (aside ...

'ps aux|grep dbmaint' gave no output aside from the grep itself, so no dbmaint.php processes were running. running the script however gave a bit more output: # /usr/local/nagiosxi/cron/dbmaint.php CLEANING ndoutils TABLE 'externalcommands'... SQL: DELETE FROM nagios_externalcommands WHERE entry_time...

All that's in the logs are two separate error messages, repeated to make a filesize of about 20kb per day. The error messages are "LOG: could not receive data from client: Connection reset by peer" and "LOG: unexpected EOF on client connection" with the latter being more frequent...

We are still experiencing crazy loads from postmaster/postgres. Do you have any further ideas what may be the problem or cause?

Here's a screenshot of a 'top' from the machine, sorted by %CPU, in case you have use for it.

We have now updated to the latest version, 2009R1.4. The upgrade itself is working fine, but postmaster/postgre is still eating up a lot of CPU and slowing the whole system down. A screenshot from a few minutes ago of 'top', sorted by processor usage, showed 13 postmaster processes each using from 1...

It's been running with the postgresql changes for a few days now, and i don't notice change in postmaster's cpu usage.
If there's been any changes, then they are minimal.

Here is the output from the script: OLD VALUES -------------- xi_commands_command_id_seq = 625 xi_events_event_id_seq = 68632 xi_meta_meta_id_seq = 68737 xi_options_option_id_seq = 61 xi_sysstat_sysstat_id_seq = 29 xi_usermeta_usermeta_id_seq = 327 xi_users_user_id_seq = 29 NEW VALUES --------------...

Could you run the attached file and give us the output? [...] Here's the output: Nagios XI Postgres Database Sequence Information CURRENT VALUES -------------- xi_commands_command_id_seq = 614 xi_events_event_id_seq = 66949 xi_meta_meta_id_seq = 67055 xi_options_option_id_seq = 61 xi_sysstat_syssta...