How to set up monitoring for a cloned Linux server with the same host name or UUID?
One of the many reasons for a Linux server monitor not showing up on the Site24x7 dashboard even after successful installation of the agent is due to having the same host name for multiple servers. This calls for a way to distinguish the cloned servers since it is mandatory to have a unique host name for every server.
The following list the possible cases:
- More then one server is created using the same image (AMI) in Amazon Web Services (AWS)
- In a virtual machine (VM), a server monitoring agent is installed and the VM is cloned along with the installed service
Let us explain the solution with one of the above scenarios:
In AWS, three servers have the same host name because it was created using the same Amazon Machine Image (AMI). In this case, the first server will be added, but the second and third servers will get mapped to the same monitor, because of the same host name. To resolve this, please follow the below steps for the other two servers:
- Edit the configuration file "/opt/site24x7/monagent/conf/monagent.cfg"
- Change the [PRODUCT_REGISTRATION_KEY]
from site24x7 = SITE24X7
to site24x7 = SITE24X7NEW - Change the [AGENT_INFO]
from agent_key = "AGENT_KEY"
to agent_key = 0 - Restart the agent by using "/opt/site24x7/monagent/bin/monagent restart"
If you are creating a custom image with Site24x7 Linux agent pre-installed to create VMs manually or through an auto scaling group, refer to our help document to create a VM image or template with server monitoring agent installed.
Related Articles
How to set up monitoring for a cloned Windows server with the same host name or UUID?
One of the many reasons for a server monitor not showing up on the Site24x7 dashboard even after successful installation of the agent is due to having the same host name for multiple servers. This calls for a way to distinguish the cloned servers ...How to set up monitoring for a cloned FreeBSD server with the same host name?
One of the many reasons for a FreeBSD server monitor not showing up on the Site24x7 dashboard even after successful installation of the agent is due to having the same host name for multiple servers. This calls for a way to distinguish the cloned ...How to fix a SSL connection error when downloading the Site24x7 Linux server monitoring agent installer
In a few scenarios, when you try to download the Site24x7 Linux server monitoring agent installer, an SSL connection failure error message will display. Follow the instructions below based on your use case to fix this error. Prerequisite: For ...Troubleshooting host name overwrites of Linux EC2 instance, while adding a Linux server monitoring agent
You can monitor system level metrics of Linux EC2 instances by installing Site24x7's Linux server monitoring agent Once the agent is installed, the instance will be automatically added to your Site24x7 account. Please note that Site24x7 uses host ...Add an On-Premise Poller for different servers having similar host name and IP address
On-Premise Poller helps monitor your internal network/resources behind the firewall. To add an On-Premise Poller for multiple servers having similar hostname and IP addresses, please follow the steps given below: Install the Poller agent. Refer here ...