Nagios Support Forum

Good Day The /usr/local/nagios/var/spool/perfdata folder has taken up 28GB of space, and has over 100 000 files in it. I don't seem to be missing graphs, but this doesn't seem right. I have 2 installs and my second install is not using any space, 4 files in it. What is the process to get this cleane...

Apologies for the late reply

Yes, that folder has the data from the servers that have been deleted

Cheers!

Good Day So we decommissioned some servers, and removed them from nagios. Now been asked to get a report of availability of them to compare against the newer ones. I do not see them as hosts to choose to make reports from anymore I have 4 years of archive logs. Is there anyway i can generate reports...

Sorry for the late reply

Thank you for your suggestions. You can close this request

Cheers!

Thank you for your reply kfanselow.
We were already thinking that route, but thought we would put it out here to the forum to see if anyone else had other suggestions.

Cheers!

Hey Everyone Thought i would post this question to see if anyone has any ideas. We need to monitor a port on 2 servers, but we only want an alert if port is ACTIVE on BOTH servers. If its active on only one, then that is fine as that is how it should be, but we cannot have both ports active Anyone h...

Thank you very much for your help

I applied the change and it was successful. No longer see the error and the check goes immediately

Thank you again. You can close this post

Cheers!

Well I dont see the same error when I force check this specific service, but i do see simlar error that the KBA talks about: ERROR: syntax error at or near "stopped" at character 282 STATEMENT: UPDATE xi_sysstat SET value='a:3:{s:10:"nagioscore";a:4:{s:6:"daemon";s:6:&q...

Info Sent

Thank you for your help

Thank you for the reply So we have 2 nagios servers in our environment, Both are at 5.6.10. This server specifically was updated from 5.2.5 to 5.6.10 and we have seen this issue ever since. The other server wasnt that old, went from 5.5.2 to 5.6.10, and i do not see the same issue with it. Dont know...