Troubleshooting administration on Cloud and hybrid systems

Use these troubleshooting entries to help resolve problems and to see known issues for administration on Cloud and hybrid systems.

Pod fails to connect to LDAP
Learn how to troubleshoot the ncoprimary pod failing to connect to Lightweight Directory Access Protocol (LDAP).
Archived policies are not displayed
After archiving a temporal event policy, an Uh, oh, something's not quite working error is displayed on the archived policies panel.
Change to operator property is unfulfilled
Changes made to immutable properties are not fulfilled.
Cloud native analytics data flow stops
Read this topic to learn how to debug and recover Cloud native analytics data flow.
Console not available
The console is not available and a couchdb error is displayed.
Empty Probable Cause and Topology columns
The Events page has empty Probable cause and Topology columns.
Failed ncoprimary, which does not restart successfully
The ncoprimary pod fails liveness and readiness checks and does not start.
Filtering for analytics policies displays an "Unknown error"
In the Policies GUI, filtering by policy type or status sometimes returns an error.
Information message about untrusted content after login
After logging in to Operations Management, an information message is always displayed.
Large policies can fail to load
When selecting a policy from Insights->Manage Policies, some larger policies can fail to load.
Impact login fails after MS Active Directory connection
After connecting to the Microsoft Active Directory external LDAP proxy, login to the UI is unsuccessful. To log in, enable contextPool on the Impact pods.
Manage Policies screen has broken policy hyperlinks
If the Policies GUI has broken hyperlinks for the policies, then this means that the links have changed, and the Policies GUI has cached the previous hyperlinks.
No restart for dedup-aggregationservice due to OOMkilled
No new actions or new groupings are displayed for events in the Alert Viewer because the de-duplicator goes in to crashloopbackoff or fails to restart.
ObjectServer log errors
Authentication errors reported in logs when ncoprimary and ncobackup pods are restarted.
Selecting all policies sometimes generates an error
In the various tabs of the Policies GUI, there is an option in the table to select all policies. Selecting this option sometimes generates an error.
Slanted line in temporal group details GUI
A slanted line appears when two events with a single event instance and the same first and last occurrence are displayed in the policy details UI.
Unable to access Impact UI after failback
Following Netcool®/Impact failback, you are not able to access the Impact UI. This happens because following failback, the Impact UI is not able to identify which is the active primary cluster.
Unable to access the Web GUI
Web GUI login attempt fails with error message.
UI shows blank page after login
Users must have the appropriate roles assigned. Either directly, or indirectly through group membership.
UI displays incorrect role
The access level of the user might not match the role that is displayed in the UI.
UI fails to launch
A leadership election between the pods can sometimes cause the nominee to crash, or move and change its IP address.
Calendar missing from the Seasonality details of policies
When a policy's Policy details are opened, no Calendar is shown in the default SelfMonitoring view.
Seasonal policy details: timezone inconsistencies
When a local time zone is different to Coordinated Universal Time (UTC), the seasonal justification page shows data in two different time zones.
Unable to assign User Roles
Error displayed when assigning User Roles in DASH.
Not all Ansible templates displayed as Ansible automations
An increase is required to the default pagination size of the Ansible® REST framework.

Parent topic: Troubleshooting administration