Use > Functionalities > Service Modeling > Troubleshooting > Host Discovery by Shell job

Host Discovery by Shell Job

This section describes the error messages you may receive from the Host Discovery by Shell job and provides suggested solutions.


Error Message: The IP address is not in the discovery IP Range

Error Category: Probe Errors

Solution: Add the IP address or range to the Ranges setting of the probe. For more information about how to do this, see Add an IP Range to the Ranges Setting.


Error Message: Inaccessible network path to target server. Perhaps it is a virtual IP address.

Error Category: Connection Errors

Solution: Add physical IPs as entry points of next hop


Error Message: Need credential to the host

Error Category: Credential-related Errors

Solution: Add the valid credentials. For more information about how to do this, see Add or Edit Credentials.


Error Message: Connection timeout

Error Category: Timeout Errors

Solution:

  • Increase the timeout value in protocol settings.
  • For Windows machines, wait for a few minutes and then try again.

Error Message: The discovery job did not find any process listening on port: <port_number>

Error Category: Software Related Errors

Solution:

  • Check if the configured account has sufficient privileges to run relevant commands. Specifically,

    • ps -e
    • netstat -nap
    • lsof

    Elevate privilege for UNIX credentials.

  • Verify if the service is still accessible.
  • Check if lsof is installed on the target machine if it runs UNIX.

Error Message: No application signature matches the process <process_info> listening on port <port_number>

Error Category: Software Related Errors

Solution: Add the signature for the application. For more information about how to do this, see Add or Edit Application Signatures.


Error Message: The following outgoing ports are filtered because they are not in portNumberToPortName.xml

Error Category: Software Related Errors

Solution: Add the port number to portNumberToPortName.xml.

To do this, click the Application Signature button in the error message and then follow the instructions. Alternatively, you can directly modify the portNumberToPortName.xml file to add the port number.


Error Message: Failed to resolve host name to IP

Error Category: IP-related Errors

Solution: Check DNS server configuration.


Error Message: Need sudo permission

Error Category: Software Related Errors

Solution: Elevate privilege for UNIX credentials to run the relevant command.


Error Message: No lsof installed on the host

Error Category: Software Related Errors

Solution: Install lsof on the target machine.


Error Message: The host is a Solaris local zone

Error Category: Software Related Errors

Solution: None for this release. Currently Solaris local zone is not supported by ASM.