Nagios Support Forum

I tested on version 2.4.5 and 2.4.10 of the plugin and they both work. One thing else it could be. When using the rate option, it creates a state file to use for the calculations and maybe that is the issue, a bad state file. The thing is, I do not know how the plugin was compiled on that docker so ...

You may need to add the multiplier option to the check to see if that allows the rate calculation. /opt/nagios/libexec/check_snmp -C <community> -o ifHCInOctets.525 -m IF-MIB -H 172.20.170.1 --rate --multiplier=1 -v One thing that does not look right, when you ran the command without the rate option...

The server is running more than InfluxDB

Search the internet for
InfluxDB
Grafana
Nagflux
Histou

The service called nagflux is what is putting the performance data in that folder so stop that from running.

Thank You.

Is the server running Ubuntu? If so, when you were cleaning up files from before, you may have deleted that folder that is needed for Apache2 to run so recreate it mkdir /var/log/apache2 chown root.adm /var/log/apache2 chmod 755 /var/log/apache2 Restart Apache systemctl restart apache2 See if you ca...

Take a look at the Apache error logs in this folder /var/log/apache2 to see what errors are logged and use that to determine what to do to fix the issue.

Thank you.

That is good news you found the files taking up the inodes.

Those files are for a application called Nagflux which is not a Nagios product so to find out why is failed and filled up the drive, you would have to go to their support site for help.


Thank You.

The problem is that the command needs to create temporary files on the filesystem to create the list of inode usage but since there are not any free inodes, it cannot so that is why you see the error. Login as root to the server and stop as many processes as you can. Remove any log files or other fi...

The only way to see if you cleaned up the files that are taking up the inodes is to run this command again.

The command I posted is supposed to output data but is maybe failing because of the inode issue and not displaying data.

Login as root and run this shortened command to see if it works.

You ran the commands from the wrong folder. They were ran from the /proc/53121 folder which is not correct. Change to the root folder of the drive by running this cd / Then run the commands or better yet, run this command that starts at the root folder and will show 30 of the largest folders with us...