RESOLVED: New install of Nagios xi - What next for Windows Monitoring

This support forum board is for support questions relating to Nagios xi, our flagship commercial network monitoring solution.
LACMAIS
Posts: 16
Joined: Fri Mar 07, 2025 11:44 am

Re: New install of Nagios xi - What next for Windows Monitoring

Post by LACMAIS »

lgute wrote: ↑Thu Mar 13, 2025 4:00 pm Hi @LACMAIS,

Do you have any special characters in your NCPA Community string/Token?
Yes, I do. I will change to numbers and letters and edit the .cfg file and restart the agent and see if that clears up the issues... or do I need to uninstall and re-install?
Top
LACMAIS
Posts: 16
Joined: Fri Mar 07, 2025 11:44 am

Re: New install of Nagios xi - What next for Windows Monitoring

Post by LACMAIS »

LACMAIS wrote: ↑Thu Mar 13, 2025 5:26 pm
lgute wrote: ↑Thu Mar 13, 2025 4:00 pm Hi @LACMAIS,

Do you have any special characters in your NCPA Community string/Token?
Yes, I do. I will change to numbers and letters and edit the .cfg file and restart the agent and see if that clears up the issues... or do I need to uninstall and re-install?
Token changed to just uppercase, lowercase, and numbers on both the host (agent restarted) and the server and while the host still shows as active, all other things being monitored are still showing as critical and with the error code 127.
Top
User avatar
lgute
Posts: 321
Joined: Mon Apr 06, 2020 2:49 pm

Re: New install of Nagios xi - What next for Windows Monitoring

Post by lgute »

Hi @LACMAIS,

Have you tried running check_ncpa.py, from a few posts back, with the new token?

If that works, you will need to update the Service checks with the new NCPA token.
Please let us know if you have any other questions or concerns.

-Laura
Top
LACMAIS
Posts: 16
Joined: Fri Mar 07, 2025 11:44 am

Re: New install of Nagios xi - What next for Windows Monitoring

Post by LACMAIS »

lgute wrote: ↑Fri Mar 14, 2025 1:59 pm Hi @LACMAIS,

Have you tried running check_ncpa.py, from a few posts back, with the new token?

If that works, you will need to update the Service checks with the new NCPA token.
I tried with the new token and this time I get:

Code: Select all

CRITICAL: Incorrect credentials given.
I try the new token with the website and it allows me in. Is there a token length maximum for the CLI? Current token length is 16 characters
Top
LACMAIS
Posts: 16
Joined: Fri Mar 07, 2025 11:44 am

Re: New install of Nagios xi - What next for Windows Monitoring

Post by LACMAIS »

lgute wrote: ↑Fri Mar 14, 2025 1:59 pm Hi @LACMAIS,

Have you tried running check_ncpa.py, from a few posts back, with the new token?

If that works, you will need to update the Service checks with the new NCPA token.
I reduced the length of the token to 12 characters and again, it works with the agent's website, but not in the CLI - Same error as this last time, Incorrect credentials given.
Top
LACMAIS
Posts: 16
Joined: Fri Mar 07, 2025 11:44 am

Re: New install of Nagios xi - What next for Windows Monitoring

Post by LACMAIS »

lgute wrote: ↑Fri Mar 14, 2025 1:59 pm Hi @LACMAIS,

Have you tried running check_ncpa.py, from a few posts back, with the new token?

If that works, you will need to update the Service checks with the new NCPA token.
I deleted the services and the host and recreated with the new shorter token, and now things seem to be working.
Thank you all for your help and guidance.
Top
User avatar
lgute
Posts: 321
Joined: Mon Apr 06, 2020 2:49 pm

Re: New install of Nagios xi - What next for Windows Monitoring

Post by lgute »

Hi @LACMAIS,

Thank you for letting us know that you got things working. I am going to lock this topic and mark it resolved.

In the near future, xi will handle special characters in NCPA tokens.
Please let us know if you have any other questions or concerns.

-Laura
Top

Return to “Nagios xi”