Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Duplicate Application of the same name assigned for each node added to Template

Let me start with the environment this incident has happened:

Orion Platform: 2019.2 HF2

SAM: 6.9.1

So, what started out to be a fix on our issue related to Group members NOT being assigned to an application template has started another issue of a different behavior. This fix to our initial concern was to do the following:

1. Stop Orion services

2. Make sure you have database backup

3. Execute on the Orion dababase: DELETE FROM APM_TemplateGroupAssignmentsBlacklist

4. Start Orion services

5. Wait up to 15 minutes - test now the Group Assignment

6. In case Group Assignment is still not there - try assigning it again and wait up to 20 minutes.

Reference: Application Templates Assigned to Group no longer updates with node assigned to group

After doing the above -- even waited for another hour -- I had to remove the Group from the template, remove then re-add again, and, finaly, out of desperation, decided to add Nodes directly.

The result started to be normal, where one by one the nodes get activated with the application until a couple of hours later, the duplication was observed.

Currently, I'm deleting the application, but given I have to delete 14,000+ objects from a single template, the system already crashes before it even finishes.

Eventually, this simple incident causes my environment to run out Polling capacity shooting one of my engines up to 200%++ which renders the server less than half effective.

I have an open ticket with support now, but I am hoping someone from the community has any experience with this. Thanks in advance.

Find more posts tagged with

Accepted answers

All comments

serena

sploy wrote:
Let me start with the environment this incident has happened:
Orion Platform: 2019.2 HF2
SAM: 6.9.1
So, what started out to be a fix on our issue related to Group members NOT being assigned to an application template has started another issue of a different behavior. This fix to our initial concern was to do the following:
1. Stop Orion services
2. Make sure you have database backup
3. Execute on the Orion dababase: DELETE FROM APM_TemplateGroupAssignmentsBlacklist
4. Start Orion services
5. Wait up to 15 minutes - test now the Group Assignment
6. In case Group Assignment is still not there - try assigning it again and wait up to 20 minutes.
Reference: Application Templates Assigned to Group no longer updates with node assigned to group
After doing the above -- even waited for another hour -- I had to remove the Group from the template, remove then re-add again, and, finaly, out of desperation, decided to add Nodes directly.
The result started to be normal, where one by one the nodes get activated with the application until a couple of hours later, the duplication was observed.
Currently, I'm deleting the application, but given I have to delete 14,000+ objects from a single template, the system already crashes before it even finishes.
Eventually, this simple incident causes my environment to run out Polling capacity shooting one of my engines up to 200%++ which renders the server less than half effective.
I have an open ticket with support now, but I am hoping someone from the community has any experience with this. Thanks in advance.

Ralph, do you mind sharing your support ticket number so I can follow it for updates?

mesverrum

Not that it will be of much help to you, but I had a similar problem once when I assigned a template to a group with like 5,000 servers in it. Seems like something went wrong in assigning the template to so many devices at once and it ended up double and triple assigning it before I finally killed the services and deleted all the trash it created in the db. Ultimately I ended up manually assigning the servers in chunks of a few hundred at a time until eventually they all had it, then after that I assigned it to the group to catch new servers that get added in the future and that all seemed to work okay.

sploy

Really helpful actually! Knowing the fact that I am not alone who experienced this just says I have not done something really wrong and it just happened for no apparent reason beyond our control.

sploy

Hey Serena!

Thanks for looking into this. In the end, we were able to clean up the 14K objects manually with all the thanks to our NOC who did a great job of cleaning them up 24x7 for a couple of days. But, for what it's worth, here is the ticket number: 00410774, which was eventually closed after a follow-up call from the support.

This incident ,to me, is a very good lesson when adding several components to hundreds of components where Orion takes time to process all of them.

First, although there were no queues when the support and I checked the MSMQ, it is still a very good practice not to click on OK or Confirm buttons for several times just because I was impatient.

Next is to make sure to do a RESTART of Orion Services when Node members of a group assigned to an Application Template do not reflect in Template Assignments (found under All Settings>SAM Settings>Manage Templates>Application Monitor Templates)