NCPA "Incorrect Credentials Given" After Nagios 2024R1.0.2 Update
Posted: Mon Feb 26, 2024 3:10 pm
Hi everyone,
It looks like after the update to Nagios XI 2024R1.0.2, using check_xi_ncpa with a community string (token) that contains exclamation marks isn't working for newly created/cloned services.
We have a lot of existing NCPA services using this community string that are passing checks just fine, but if I go and clone those checks they no longer work. Even if I use the "Run check command" on a working service/host that shows green in XI right now, I get "CRITICAL: Incorrect credentials given". I suspect this has something to do with a change of how Nagios/NCPA escape special characters.
If I manually edit the check to remove the escaping backslash before the "!", then "Run Check Command", it works. But as soon as I click "Save" the check adds the backslashes again and fails.
I'm hoping someone can look into this so we don't have to change all our ncpa.cfg files and Nagios XI services to use a new community string that does not contain "!".
It looks like after the update to Nagios XI 2024R1.0.2, using check_xi_ncpa with a community string (token) that contains exclamation marks isn't working for newly created/cloned services.
We have a lot of existing NCPA services using this community string that are passing checks just fine, but if I go and clone those checks they no longer work. Even if I use the "Run check command" on a working service/host that shows green in XI right now, I get "CRITICAL: Incorrect credentials given". I suspect this has something to do with a change of how Nagios/NCPA escape special characters.
If I manually edit the check to remove the escaping backslash before the "!", then "Run Check Command", it works. But as soon as I click "Save" the check adds the backslashes again and fails.
I'm hoping someone can look into this so we don't have to change all our ncpa.cfg files and Nagios XI services to use a new community string that does not contain "!".