article Agent not responding after IP or hostname change

If up.time has difficulty communicating with agents that have had their IP address or hostname changed, follow these steps to debug the issue:

  1. Confirm that the up.time hostname of the agent matches the new hostname or IP address.
  2. Try adding the full domain name to the hostname if it is not already entered.
  3. Restart the up.time data collector.
  4. Confim that the monitoring station is able to properly resolve the new IP / hostname by running the following commands from the monitoring station:

    > nslookup <hostname>
    > ping <IP returned from the above>

Related Articles


Linux or UNIX agent is not responding

RatingViews
article

By: uptime Support | Date Created: 10-25-2005 | Last Modified: 7-14-2011 | Index: 034

  6551

AIX agent installation error - sar: time change not positive

RatingViews
article

During the installation of the AIX agent you may encounter this error --- Checking to see if perfparse returns valid columns sar: time change not positive /opt/uptime-agent/bin/perfparse.sh[28]:...

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

  3895

Unable to access up.time after changing hostname

RatingViews
article

After changing the hostname of a system, you may not be able to access the up.time UI due to the hard coded hostname configuration in the uptime.conf file. To resolve this issue, ensure that the...

By: uptime Support | Date Created: 7-28-2011 | Last Modified: 7-31-2014 | Index: 553

  2036

Oracle database not responding in up.time interface

RatingViews
article

If you are seeing a Database Not Responding message in up.time GUI, with something similar to the following error: =================== Database is not responding ...

By: uptime Support | Date Created: 10-14-2009 | Last Modified: 8-13-2011 | Index: 436

  3346

"Database Not Responding" Message Appears in Global Scan

RatingViews
article

When this issue occurs, check the uptime.log file for messages similar to the following: 011-03-29 11:40:48,873 ERROR (ProtocolHandler:79) - In command...

By: uptime Support | Date Created: 7-9-2011 | Last Modified: 10-26-2012 | Index: 539

  2925

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement