Either reload the nagios agent on the box you resized the volume for or if possible reboot the box at the earliest convenience.
It's the linux agent that is reporting back faulty information so my guess is that rebooting the Nagios server won't help in this case.
if you logon to the linux box lookup the nrpe process:
# ps -ef | grep -i nrpe
Select allOpen in new window
You should get similar output like:
UID PID PPID C STIME TTY TIME CMD
nagios 10813514 1 0 Apr 26 - 7:38 /usr/local/nagios/nrpe -c /usr/local/nagios/nrpe.cfg -d
Where in this example you would kill PID number 10813514,restart the NRPE client and show info about the newly started process:
# kill -9 10813514;/usr/local/nagios/nrpe -c /usr/local/nagios/nrpe.cfg -d;ps -ef | grep -i nrpe
As output you should get the newly started process info of NRPE.
Then run the drive check manually to see if the values turn out okay.
Are you sure you're even using NRPE? Try and look for 'nagios' instead and post the output here.
BTW restarting Inetd might also interrupt other services you may have running under inetd.
© 1996-2023 Experts Exchange, LLC. All rights reserved. Covered by US Patent