Troubleshooting

Use the entries in this section to troubleshoot problems.

Recovering from a long time site outage
Use these troubleshooting instructions to recover a site from a long time site outage on a geo-redundancy enabled cluster.
Service failure on the primary site does not trigger auto failover
In a geo-redundancy enabled setup, when services fail on the primary site, the system does not automatically fail over to the backup site.
Agile Service Manager pages unavailable after assigning user roles
In a geo-redundancy enabled environment, the IBM® Agile Service Manager pages are unavailable after you assign user roles to smadmin.
Menu items in Web GUI can disappear if primary and backup clusters fail
In a geo-redundancy enabled environment, if both primary and backup clusters are down, then the menu items in Web GUI might not appear.
Information window about untrusted servers appears
After you log in to Dashboard Application Services Hub (DASH), a window opens that mentions that the servers are untrusted.
Cloud native analytics grouping stops on a geo-redundant cluster
If live events are not being grouped by cloud native analytics policies, restart the gateway pod.
Cannot create Netcool/OMNIbus artifacts on a backup ObjectServer after failover
When you run in a geo-redundant environment, if you can't create Netcool®/OMNIbus artifacts on a backup ObjectServer after ObjectServer failover, increase the load balancer HTTP timeout settings.

Parent topic: Technology preview