Nagios Support Forum

We appear to be having two problems
First being using subdirectories after $USER1$
The second being creating new nagios user macros.

We are trying to migrate a group of oracle checks for application specific issues, and trying to keep them consolidated in one folder rather than in the libexec.

Attempt 1
Command was defined as: Service was defined with appropriate arguments, all of which appear to resolve properly, and configuration was applied.

Check output is as follows: Notice that oracle11 is not in the path for the check.

Attempt 2
Assuming that we were simply not able to use subdirectories of a check, we tried creating a new USER macro for the oracle11 directory.
We have added the following to resources.cfg on the parent and all children. and have bounced nagios, and dnx for good measure.

the check command has been defined as Please note using USER10 rather than USER1 as in the first attempt.

The service has been defined with the appropriate arguments, and applied.
If we run it manually on any host (parent or children) all is well.

When the check runs, we just get: Notice that oracle11 is not in the path for the check.

It appears that nagios does not catch the user10 macro we created, and defaults to user1.

I've dug through documentation, but could not find anything specific to creating USERn macros, just utilizing them.
Can someone kick me in the right direction, or explain what I'm doing wrong in these two scenarios?

Without seeing the config snapshot I cannot know for sure, but my guess would be that the new command and the command your check is referencing are named 2 different things.

You are on the right track, and everything outlined should work just fine, but you likely are using 2 different command names.

Feel free to open an email ticket submitting your current snapshot and the name of the service running the check and we can take a look.

I did go back and verify, they are using the same name, and it does show the $USER10$ in the Command View. I'll open a ticket.

I just had another thought, I'm not sure what plugin you are using, but you might want to make sure the path isn't being hardcoded in the plugin