Duplicate agent's record -- Agent client collector

[_navin9898]

Hi Team,

We are rolling out agent client collectors on multiple windows server, however we are seeing an issue where 2 records are getting created for the same server under 'Agents', when investigated found that there is only one difference between both the records where one record is having configured check field value as '1' and other one is having it as '0'.

Could you please let me know what is causing it?

Best Regards,

Nav

[Yashsvi]

Hi @_navin9898,

The issue where two records are created for the same server under 'Agents' with a difference in the configured check field value ('1' and '0') typically indicates that there might be two instances of the agent client collector running simultaneously on the server. Here are some common causes and troubleshooting steps you can consider:

1. Multiple Instances of the Collector: Check if there are multiple instances of the agent client collector service running on the server. This can happen if the collector service was started manually or if there are conflicting automated processes.

2. Configuration Issues: Verify the configuration of the agent client collector. Ensure that it is configured to run as a single instance per server. Sometimes, configuration files or scripts may inadvertently launch multiple instances.

3. Service Startup: Review how the collector service is started. If it's started manually by different users or scripts, it could result in multiple instances running concurrently.

4. Logging and Monitoring: Enable detailed logging for the agent client collector to track when and how instances are started. This can help identify any automated processes or scripts that may be starting the service unexpectedly.

5. Environment Variables: Check if there are any environment variables or startup parameters that could cause multiple instances to run.

6. Scheduled Tasks or Cron Jobs: Ensure that there are no scheduled tasks or cron jobs configured to start the agent client collector at different times or with conflicting parameters.

Thank you, please make helpful if you accept the solution.

[_navin9898 · Accepted solution]

Hi @Yashsvi 

Thank you for your swift response.

With regards to below points, could you please let me know your inputs?

1. Configuration Issues: Verify the configuration of the agent client collector. Ensure that it is configured to run as a single instance per server. Sometimes, configuration files or scripts may inadvertently launch multiple instances.

1. Environment Variables: Check if there are any environment variables or startup parameters that could cause multiple instances to run.

         How to find it?

1. Scheduled Tasks or Cron Jobs: Ensure that there are no scheduled tasks or cron jobs configured to start the agent client collector at different times or with conflicting parameters.

Where I can find it?

I am a newbie with respect to agent client collector and still learning it. Additionally I have gone through multiple articles but didn't anything.

Best Regards,

Nav

[Yashsvi]

Hi @_navin9898,

To address your concerns:

Configuration Issues:

To verify and ensure that the agent client collector is configured to run as a single instance per server, you typically need to check the configuration files or scripts responsible for launching the collector. Here are steps you can take:

1. Configuration Files: Locate the configuration file(s) for the agent client collector. These are usually located in directories specific to the collector software or in a designated configuration folder on your server.

2. Startup Scripts: Review any startup scripts used to launch the agent client collector. These scripts might reside in /etc/init.d, /etc/systemd/system, or similar directories depending on your operating system.

Environment Variables:

Check for environment variables or startup parameters that might inadvertently cause multiple instances to run. Here’s how you can find them:

1. Environment Variables:
   • On Linux: Use the env command or check the startup files (~/.bashrc, /etc/environment).
   • On Windows: Check System Properties > Advanced > Environment Variables.

Scheduled Tasks or Cron Jobs:

Ensure that there are no scheduled tasks or cron jobs configured to start the agent client collector at different times or with conflicting parameters. Here’s where to look:

1. Cron Jobs (Linux/Unix):

   • Use crontab -l to list scheduled tasks for the current user.
   • Check system-wide cron jobs in /etc/crontab, /etc/cron.d/, and /etc/cron.daily/, etc.

2. Scheduled Tasks (Windows):

   • Open Task Scheduler (taskschd.msc).
   • Look for any tasks related to the agent client collector under Task Scheduler Library.

Thank you, please make helpful if you accept the solution.

[_navin9898]

@Yashsvi  thank you for your response. Additionally I just came to know that there is a server migration going on, do you think that could also cause reported issue? 

Additionally could you please redirect me some resources pertaining to Agent client collector?

Best Regards,

Nav