Troubleshooting PMN
-
Problem: The pmn.logs file contains the following error message:
An authentication Error sending PMN notification: Possibly caused by authentication failure.
Scenario: After you upgrade a DCNM Native-HA setup to Release 11.1(1), an authentication failure message is logged in the pmn.logs file. This error occurs because RabbitMQ is not started correctly, and it is missing the administrator user.
Workaround: Restart the AMQP service. If this issue is not resolved, create an admin user with full access.
-
Option 1 - Restart AMQP using the following commands:
#appmgr stop amqp #appmgr start amqp
-
Option 2 - Create an admin user with full access using the following commands:
# rabbitmqctl add_user <username> <password> # rabbitmqctl set_user_tags <username> administrator # rabbitmqctl set_permissions -p "/" <username> ".*" ".*" ".*"
-
-
Problem: When checking the “appmgr status all” for the AMQP status, you get the below error message.
Cluster status of node rabbit@sol-dcnm1 ... Error: {:aborted, {:no_exists, [:rabbit_runtime_parameters, :cluster_name]}}
Scenario: This issue might occur in a DCNM Native HA setup.
A workaround is not required for this issue because it is a temporary status. Due to the auto heal option, the AMQP services will come up automatically in both the nodes.