OC Group, Inventory and Alarm Console stop working after an OC server restart
search cancel

OC Group, Inventory and Alarm Console stop working after an OC server restart

book

Article ID: 388048

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

OC Group, Inventory and Alarms Console stopped working after the OC server was restarted. Alarm Console displays "Error Retrieving Alarms" and other Portlets display a blank page for all users.

1. A restart of the Nimsoft Robot Watcher service on the UIM Server and OC did not make a difference. 

2. The browser refresh allows other portlets in OC to temporarily work except for Alarm Console. Alarm Console continues to display "Error Retrieving Alarms"

3. Error captured in the operatorconsole.log; 

WARN  com.firehunter.operatorconsole.controller.UserHomePagePreferenceController:getLandingPageByUser:169 controller.UserHomePagePreferenceController - Found a user with name: administrator has a landing page preference personal as null and it does not have access to it. Account:null and it does not have access to it. Global:Home and it does have access to it.

Environment

OC 23.4.x

Resolution

This issue is sometimes seen with the OC install is corrupted

Option 1. Redeploy the OC again

Option 2. Uninstall and reinstall OC if Step 1 does not resolve the issue.

a. Backup the .:\Nimsoft\probes\service\wasp\conf\wasp.keystore if HTTPS is enabled

b. Backup the .:\Nimsoft\probes\service\wasp\wasp.cfg if HTTPS is enabled

c. Uninstall the OC per Uninstall Operator Console

d. Install the OC per Install Operator Console

e. Confirm that issue is resolved

f. Restore the wasp.keystore and wasp.cfg from backup

g. Deactivate/Activate the wasp probe

Additional Information