Products
Applications
Support
Company
How To Buy
Skip to main content (Press Enter).
Sign in
Skip auxiliary navigation (Press Enter).
Register
Skip main navigation (Press Enter).
Toggle navigation
Search Options
Home
Communities
All Communities
Enterprise Software
Mainframe Software
Symantec Enterprise
Blogs
All Blogs
Enterprise Software
Mainframe Software
Symantec Enterprise
Events
All Events
Enterprise Software
Mainframe Software
Symantec Enterprise
VMware
Water Cooler
Groups
Enterprise Software
Mainframe Software
Symantec Enterprise
Members
DX Infrastructure Management
Private Community
View Only
Community Home
Threads
Library
Events
Members
Back to Library
CA UIM - hub process does not start automatically / Controller.cfg missing probe sections
1
Recommend
May 31, 2018 01:00 PM
Ryan Dunn
Issue:
- The hub process does not start automatically after restarting the primary hub server.
- Manually starting the hub.exe allows us to access IM however, most probes are missing and the remaining hub and controller probes do not start (in yellow status).
Cause:
UIM - Windows environment
Resolution:
1. Go to Program Files (x86)\Nimsoft\hub and manually start the hub.exe process.
2. Access Infrastructure Manager and check the status of the hub and probes.
3. If most/all of the probes are missing, its most likely that the probe sections are missing from the controller.cfg, this is usually caused by a corruption of the controller.cfg.
- Go to Nimsoft\robot, open the controller.cfg and confirm if probe sections are missing.
4. Stop the Nimsoft service and kill the manually started hub.exe process.
5. You will now need to re-add all of the required probe sections to the controller.cfg, if you have a copy of the controller.cfg or a secondary hub controller.cfg please use it.
- I will attach a copy of my UIM 8.51 primary hub controller.cfg as an example which can be used (all magic_key entries removed).
6. Once the probe sections are in place, you will need to remove all "magic_key = ************" entries from each probe section, example:
- Before:
<nas>
description = Nimsoft Alarm Server
group = Infrastructure
active = yes
type = daemon
command = nas.exe
config = nas.cfg
logfile = nas.log
workdir = probes/service/nas
start_after = alarm_enrichment
magic_key = etABXGc//Wv2stc5V+FRZZ5v6e6r0EZYWsu6ix9yufXTZwm9p2QkqLQ1zP0F8Azd
</nas>
- After:
<nas>
description = Nimsoft Alarm Server
group = Infrastructure
active = yes
type = daemon
command = nas.exe
config = nas.cfg
logfile = nas.log
workdir = probes/service/nas
start_after = alarm_enrichment
</nas>
7. Once the above is complete, save the controller.cfg and restart the Nimsoft Service.
8. Login to IM and re-validate security on all probes.
- Select all probes -> Right Click -> Security -> Validate -> Yes All
9. If a handful of probes still do not start, redeploy them from the local archive.
External KB:
CA UIM - hub process does not start automatically - CA Knowledge
Statistics
0 Favorited
4 Views
1 Files
0 Shares
0 Downloads
Attachment(s)
controller.cfg.PrimaryHubCopy.UIM851.txt.zip
2 KB
1 version
Uploaded - May 29, 2019
Download
Download Document
Please accept the terms of the copyright associated with this attachment before downloading it. Click the link below to read the terms.
Accept
Tags and Keywords
Related Entries and Links
No Related Resource entered.
Copyright 2019. All rights reserved.
Powered by Higher Logic