Menu

#319 Ping scan is not working

1.1
open
nobody
5
2016-06-10
2015-05-26
Anonymous
No

Hi,

If I do scan subnet for new hosts, I get following error: Error executing scan! Error code - 255 (see attached pic), if I use Discover scan.
If I use status update scan, it is working fine, only.

I have enabled debugging, but I cannot see any failure messages in webserver logs.

1 Attachments

Discussion

  • Anonymous

    Anonymous - 2015-06-23

    same problem here...

     
  • Miha Petkovsek

    Miha Petkovsek - 2015-06-23

    It is permissions related, make sure apache has permissions to execute ping. Or check selinux policy.

     
  • Anonymous

    Anonymous - 2015-08-14

    This is not a permissions problem on FreeBSD 10. Prior to using 1.1 this worked perfectly. No changes were made to the ping binary and is globally readable and executable as shown below:

    % ls -l /sbin/ping
    -r-sr-xr-x 1 root wheel 28072 Jul 13 11:00 /sbin/ping

    Ping Path is set to /sbin/ping

     
  • Anonymous

    Anonymous - 2015-08-14

    I should note that I also tried switching to fping, which was installed via the ports collection and is also globally accessible by all users and I receive the same error.

    ls -l /usr/sbin/fping
    lrwxr-xr-x 1 root wheel 21 Sep 11 2014 /usr/sbin/fping -> /usr/local/sbin/fping

     
  • Anonymous

    Anonymous - 2015-12-22

    Hello same problem here with a basic conf

     
  • Miha Petkovsek

    Miha Petkovsek - 2016-02-02

    Please check 1.2

     
  • Lantizia

    Lantizia - 2016-06-10

    Hi, We've just upgraded from 1.1 to 1.2... before the upgrade pings were fine... but after the upgrade we get this error too. Nothing has changed with the web server or PHP setup (or things like open base dir)... I've even created a little test.php file in the ipam directory to call ping itself and that works. This is something specifically to do with phpipam I feel.

    FIXED...

    It seems 1.2 scans subnets by calling php itself to call another php script to do it - thus it won't necessarily be the same php.ini. Make sure you have included PEAR (e.g. /usr/share/php/) in both your /etc/php5/cli/php.ini and your normal php for running web sites.

     

    Last edit: Lantizia 2016-06-29

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.