Hello,
I am working with some Nagios XI servers and I have multiple hosts throwing "CRITICAL: Incorrect credentials given" errors on mainly McAfee and RMF related services. I checked/update the community token and made sure it matched. Also reset the services but still getting these errors.
I am new to Nagios so any help would be greatly appreciated. Someone else set this up prior and is no longer with the company.
Thanks
CRITICAL: Incorrect credentials given
Re: CRITICAL: Incorrect credentials given
Hi @callcollin,
Thanks for reaching out.
How are these service checks on the affected hosts setup? You mention community token, so I'm guessing the checks may be setup using NCPA agents.
If you navigate to the Monitoring tab for one of the affected service check...
Thanks for reaching out.
How are these service checks on the affected hosts setup? You mention community token, so I'm guessing the checks may be setup using NCPA agents.
If you navigate to the Monitoring tab for one of the affected service check...
- Navigate to Configure | Core Config Manager
- Click on Services on the CCM Object Summary
- Click on the Config Name next to the name of one of the affected service checks
- Click on the Run Check Command button
- In the modal (popup window), click on the Run Check Command button
You do not have the required permissions to view the files attached to this post.
Please let us know if you have any other questions or concerns.
-Laura
-Laura
Re: CRITICAL: Incorrect credentials given
@callcollin,
Please be advised there is a known issue with special characters in NCPA tokens currently in XI, which could be affecting you depending on your token. This issue has been tagged with #1975 and has been addressed, so please keep an eye on the changelog in future releases for a fix.
Please be advised there is a known issue with special characters in NCPA tokens currently in XI, which could be affecting you depending on your token. This issue has been tagged with #1975 and has been addressed, so please keep an eye on the changelog in future releases for a fix.