Nagios Support Forum

hi scottwilkerson,

we managed to bring back the nagios server and we noticed that something is being written to root so much that it filled up the inodes of the root partition thus we had the issue that we could not get nagios up. The server we have is only meant for nagiosxi..
Are you able to provide us some insights on this on what may be the culprit and how to resolve it permanently?

Can you give an example what is being written?

hi scottwilkerson,

we suspect /usr/local/nagios/var/spool/checkresults/

Can you advise what is written there? When we remove the files inside, the inodes decreased from 100% to 4%.

hi scottwilkerson,

i have another question.. please see the attached log captured from /usr/local/nagios/var/nagios.log and /var/lo/messages.

i see this "Caught SIGTERM, shutting down... " lines when i try to import some services with our software using nrdp and the import failed. Is this normal? We are trying to investigate the cause of import failure and need to know if this is a factor..
Thanks

/usr/local/nagios/var/spool/checkresults/ is where NRDP results would be written until they are picked up from Nagios

charmainequek wrote:i see this "Caught SIGTERM, shutting down... " lines when i try to import some services with our software using nrdp and the import failed. Is this normal? We are trying to investigate the cause of import failure and need to know if this is a factor..

This could be a factor if nagios isn't running, it would cause the /usr/local/nagios/var/spool/checkresults/ to fill up until nagios is running again

hi scottwilkerson,

understand on the checkresults folder now. how are the results picked by Nagios and i there a config file for this somewhere?

Regarding the other issue with the screen shots attached, it is a separate issue from the checkresults folder.
It happened when i am trying to import new hosts and services from a monitoring wizard (our own software). The import failed and i had the log windows open and caught these few lines that seem critical.

Trying to figure out what causes the shutting down or import failure and which one came first..

charmainequek wrote:how are the results picked by Nagios and i there a config file for this somewhere?

Nagios look in the path that is set in the check_result_path directive on the nagios.cfg for results that it needs to process.

charmainequek wrote:Regarding the other issue with the screen shots attached, it is a separate issue from the checkresults folder.
It happened when i am trying to import new hosts and services from a monitoring wizard (our own software). The import failed and i had the log windows open and caught these few lines that seem critical.

This would depend on if the software that is writing the files to be imported are writing correct files.

If it is creating config files with errors it could be problematic.

hi scottwilkerson,

just an update, the import failure issue has been resolved (caused by our software).

Would like to clarify with you on 2 questions :

1. If a host that is sending passive check results to Nagios is down, will Nagios be able to notify that it is down? I see that when my host is down, the service check status in Nagios XI is outdated but is still indicated a "Ok".

2. For snmp trap sender, when state type is set to "Critical" for Services, services in both "Unknown" and "Critical" status are sent over to snmp trap receiver? Is "Unknown" classified as "Critical" as well?

charmainequek wrote:1. If a host that is sending passive check results to Nagios is down, will Nagios be able to notify that it is down? I see that when my host is down, the service check status in Nagios XI is outdated but is still indicated a "Ok".

See page 8 of the doc below to see how to configure checks for freshness checking, whereas they will change to a critical state if a result isn't received in a timely manner
https://assets.nagios.com/downloads/nag ... ios-XI.pdf

charmainequek wrote:2. For snmp trap sender, when state type is set to "Critical" for Services, services in both "Unknown" and "Critical" status are sent over to snmp trap receiver? Is "Unknown" classified as "Critical" as well?

Unknown is it's own state and would be classified as Unknown

hi scottwilkerson,

thanks..
but when i send trap messages for "Critical", the snmp receiver is receiving both "Critical" and "Unknown" messages.
how do we fix this?