Nagios Support Forum

One of the things overwritten in upgrades are wizards.

Can you follow the steps in the previous thread I linked too and report the results? This will go easier if no changes are made independently of instructions, as we need to base our responses on the information provided. When you do make changes, please specify exactly how/where the changes were made and then applied if necessary.

Did you get the errors resolved after adding / removing the quotes?
What could of caused it was that the upgrade reverts the default nagios commands back to their default arguments and also some of the plugins are updated as well.
If those checks were using a modified setting from before the upgrade could of caused the error when the command was reverted.

Sorry, which steps are you looking for me to follow? Adding and removing quotes?

I've surrounded the commands user and pw with single, double and no quotes. All returning the same error that says invalid characters in username.

If there are no special characters in the username, remove all of the quotes around the macro in the service check.
For the password macro, put double quotes around them.
Also, can you post a screen shot showing the errors so we can see what you are seeing?

The username has an underscore. This is fine correct?


The Other post I was pointed to had double quotes around the Macro response $USER9$="!" Should I have mine be $USER3$="Password!"

The double quotes should be around the macros in the command definition and not in the resource.cfg file so edit your service checks like below. Because the username has a _ in it, you may need to double quote the "$USER2$" as well.

Hm, I tried this with no luck. I also deleted one of the services and tried creating it by scratch with no luck.

Can you create a usename and password without any special characters and see if that works?

I suppose I can request a new AD account that falls within the Nagios login requirements. I'd then have to request access to the database I am looking to monitor. I am not positive they are going to give me an account that connects to databases that house Patient Health information with an account whose login and password complexity falls below our company requirements.

So, I am supposed to suggest to the decision makers here that even though this worked before the upgrade, this is the only way to get back to monitoring these databases?

brettmlawrence wrote:I suppose I can request a new AD account that falls within the Nagios login requirements. I'd then have to request access to the database I am looking to monitor. I am not positive they are going to give me an account that connects to databases that house Patient Health information with an account whose login and password complexity falls below our company requirements.

So, I am supposed to suggest to the decision makers here that even though this worked before the upgrade, this is the only way to get back to monitoring these databases?

The resource.cfg should be working for this use case. Looking through the thread, it looks like we haven't had you test this over the CLI. Are you able to get it working if you run the check manually from the command line? Please show us the full input / output.