article Error while pinging: Failed to create raw socket

When up.time attempts to perform a ping check, the following error message may appear:

 

Error while pinging: Failed to create raw socket

 

This error is commonly caused by permission problems with the icmp executable that up.time uses to verify the PING status of a monitored element.  To resolve this issue, follow the steps below for the appropriate platform.

 

Windows Platforms

 

Ensure that you have installed up.time as a local administrator.  This error is only known to occur when up.time is installed as a domain or by a non-local administrator.

 

Linux or Solaris Platforms

 

Ensure that the permissions on the icmp binary are the same as those detailed below.  The root user must own this binary so that it can create raw sockets.

 

# ls -l /usr/local/uptime4/icmp.exe -rws--x--x 1 root root 9663 Sep 18 16:35 /usr/local/uptime4/bin/icmp.exe

 

To test that the permissions are correct, execute the icmp binary directly by entering the following command:

/bin/icmp.exe 3

The following example shows a sample output from the icmp binary:

 

> icmp.exe testagent 3 ICMP PING:avg-6.67, loss-0.00%, packets-3

 

Solaris Platforms

 

Only In some cases, non-global zones may be utilizing a Loopback File System that will prevent the suid bit from being used.  If a loopback file system is in place, ICMP.EXE should be able to run if the file is moved to another filesystem type that allows suid, and symlinked into the uptime/bin folder.

Related Articles


Problems adding an Agent to up.time

RatingViews
article

By: uptime Support | Date Created: 6-15-2006 | Last Modified: 8-9-2011 | Index: 083

  7001

Agent rpm install error: unpacking of archive failed on file

RatingViews
article

At times during the installation of up.time's rpm based agents (Linux and ESX 2) you may receive a 'file size' error. This error is usually a result of a bad file download. It is suggested that you...

By: uptime Support | Date Created: 10-10-2009 | Last Modified: 8-10-2011 | Index: 406

  2942

monitor failed: software caused connection abort: recv failed

RatingViews
article

This error message indicates a general network connectivity error from the monitoring station to the monitored agent servers. It has only been seen on windows monitoring stations and is generally...

By: uptime Support | Date Created: 12-31-1969 | Last Modified: 6-27-2013 | Index: 280

  5388

Increasing Windows TCP socket limits

RatingViews
article

Because up.time is a network heavy application it requires many short lived socket connections to be running at any given time. At times this socket load can reach the limits of the default Windows...

By: uptime Support | Date Created: 12-31-1969 | Last Modified: 9-1-2011 | Index: 271

  10910

Still receiving alerts when topological dependency has failed

RatingViews
article

When the host check for a topological host enters a failure state (i.e. WARN or CRIT), the service monitors for hosts that depend on that element will have their alerts / actions suppressed and...

By: uptime Support | Date Created: 7-7-2011 | Last Modified: 8-11-2011 | Index: 533

  1523

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement