- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2024 11:31 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2024 11:50 PM
Hi @Yashsvi
Thank you for your swift response.
With regards to below points, could you please let me know your inputs?
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.
Environment Variables: Check if there are any environment variables or startup parameters that could cause multiple instances to run.
How to find it?
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2024 12:59 AM
Hi @_navin9898,
Yes, a server migration could definitely contribute to the issues you're experiencing with multiple instances of the agent client collector. During a migration, there can be configuration discrepancies, duplicated tasks, or changes in environment variables and scheduled jobs that might cause multiple instances to launch.
Thank you, please make helpful if you accept the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2024 06:15 AM
I am seeing a different but similar issue where a server is rebuilt, and the old entry is still present, and cannot be deleted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2024 01:10 AM
@RGreene May I know what is the status of the agent in the old entry? If it is 'down' then it will be removed by 'agent client collector' table after 30 days automatically.
Please go through below article which talks about the same:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1125106
Best Regards,
Naveen
