close
keyboard_arrow_left
Table of Contents
- play_arrow Debug Paragon Automation Components
- play_arrow Troubleshoot Paragon Pathfinder
- General Troubleshooting Techniques
- LSP Controller Statuses Overview
- LSP Stuck in PENDING or PCC_PENDING State
- The Operational State of the LSP Is Down
- LSPs Missing from the Network Information Table
- Topology Not Displayed in the GUI
- Changes Not Reflected in the GUI
- Topology Displayed in the GUI Is Incorrect
- PCS Out of Sync with Toposerver
- PCCs Are Not PCEP-Enabled
- play_arrow Troubleshoot Paragon Insights
- play_arrow Troubleshoot Paragon Planner
list Table of Contents
Troubleshoot RabbitMQ Cluster Failure
Solution
If
the
RabbitMQ
cluster
fails as a result of a power outage, the RabbitMQ message bus may not restart properly. To
identify
the status of the RabbitMQ message bus, run the kubectl get po -n
northstar -l app=rabbitmq command. This command should show three pods with their
status as Running. For
example:
content_copy zoom_out_map
$ kubectl get po -n northstar -l app=rabbitmq NAME READY STATUS RESTARTS AGE rabbitmq-0 1/1 Running 0 10m rabbitmq-1 1/1 Running 0 10m rabbitmq-2 1/1 Running 0 9m37s
If the status of one or more pods is Error, use the following recovery
procedure:
Delete RabbitMQ.
kubectl delete po -n northstar -l app=rabbitmqCheck the status of the pods.
kubectl get po -n northstar -l app=rabbitmq.Repeat
kubectl delete po -n northstar -l app=rabbitmquntil the status of all pods isRunning.Restart the Paragon Pathfinder application.
content_copy zoom_out_mapkubectl rollout restart deploy -n northstar
