Nagios : CRITICAL – Could not interpret output from ping command

by Herman Tarigan on December 9, 2008

Nagios

Nagios

Host Status:
DOWN
(for 0d 0h 48m 36s)
Status Information:
/bin/ping -n -U -w 30 -c 5 67.15.225.4
CRITICAL – Could not interpret output from ping command


solusi :
root@concat [/usr/local/nagios/etc]# ls -al /bin/ping
-rwxr-xr-x 1 root root 35864 Dec 21  2006 /bin/ping*
root@concat [/usr/local/nagios/etc]# chmod u+s /bin/ping
root@concat [/usr/local/nagios/etc]# ls -al /bin/ping
-rwsr-xr-x 1 root root 35864 Dec 21  2006 /bin/ping*

Done !!!

Herman Tarigan

Pernah menjadi Operator warnet, Customer Service Webhosting, System Administrator Webhosting, Website (SEO) Consultant, Operational Manager, Marketing dan sekarang memilih menjadi FREELANCE :)

Incoming search terms for the article:

CRITICAL - Could not interpret output from ping command, Could not interpret output from ping command, nagios Could not interpret output from ping command, mikrotik nagios, nagios CRITICAL - Could not interpret output from ping command
Share and Enjoy:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • LinkedIn
  • Live
  • Print this article!
  • Slashdot
  • StumbleUpon
  • Technorati
  • YahooMyWeb

{ 1 comment… read it below or add one }

Perk1z December 19, 2008 at 5:29 pm

ngeteh comment :P

Reply

Leave a Comment

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Click to hear an audio file of the anti-spam word