Release Automation

Expand all | Collapse all

How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

  • 1.  How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Posted Feb 09, 2016 06:39 PM

    We have been renaming the node id for our execution servers. After made changes to the nimi_config.xml and restart. We found that the entry with the old node id is still presented in Health Monitoring along with the new Node id.

     

    How could I remove the entry of the old node id?

     

     

    Kind Regards

    Sindy



  • 2.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Broadcom Employee
    Posted Feb 10, 2016 01:30 PM

    Hi Sindy,

     

    This was posted to the CA Automation community so I am moving it to the CA Release Automation community. In regards to your question, I don't have an answer. I wonder if it stores any historical data for X amount of time and maybe it is just a matter of time before it is removed. Otherwise, I'm not sure if recycling the NAC would help but have you tried? If neither of these things help and there are no other answers offered then you can open a support issue for us to look into it further.

     

    Kind regards,

    Gregg



  • 3.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Posted Feb 10, 2016 09:44 PM

    NAC was started couple of times hoping that it will clean these entries up but it didn't.



  • 4.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Posted Feb 10, 2016 02:05 PM

    I believe that you would need to delete the old nodes out of the system from the administration tab in the ASAP.  I haven't found a way to do this in the ROC yet.



  • 5.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Posted Feb 10, 2016 09:45 PM

    The obsolete entries are not displayed in the ASAP. Only found in ROC.



  • 6.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?
    Best Answer

    Broadcom Employee
    Posted Feb 11, 2016 05:17 AM

    Hi,

     

         I believe the only way to remove these objects from the health monitor panel involves removing the old server objects from the DB tables, could you please raise a support ticket so our engineering team can help you do this.

     

    Regards

    Keith



  • 7.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Broadcom Employee
    Posted Feb 11, 2016 10:30 AM

    Per Keith's recommendation, we're available to further help with this via a ticket, since we'll need to take a look at your specific DB tables.



  • 8.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Broadcom Employee
    Posted Feb 16, 2016 05:42 PM

    Hi Sindy, we haven't heard back in a while -- Do you still need help with this one?  Or if you figured out a solution, could you share it with us? 

     

    Also, something else to check -- Have you tried clearing the persistency folder?  That's advised as the third step in this Communities KB post: .Nolio KB: How do I Change the ID of an Execution server or an Agent?



  • 9.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Posted Feb 16, 2016 09:57 PM

    James,

     

    We still experience the issue. Our management server is not available at the moment. When it's back up again then I will raise the support ticket with appropriate screen dump for the support team to assist us.

     

    Thanks for following it up.

     

     

    Sindy



  • 10.  Re: How to remove obsolete execution server entry from Health Monitoring in CA Release Automation?

    Broadcom Employee
    Posted Feb 17, 2016 10:08 AM

    No problem!  Let us know once the case is opened. I'd like whatever solution is determined from the case on our end to also be shared here.