Closed unix196 closed 4 years ago
Thank you for the report. I've an idea of the root cause of this issue...
Is it possible to add 2>&1
at the end of nagios command_line
definition?
Does this fix the null output issue?
Yes, this working! That's basically enough, but better mention in documentation.
I will fix this directly in the code. This is just a workaround and a test to see if I got the cause of the problem.
We have nagios3 in docker (~3400 checks). Added vault monitoring in nagios:
When I try run check in CLI, everything is working:
Some other token:
In nagios web interface I see that - https://ibb.co/1K76F7p. I try in my check "vault: expire token accessor token-for-nagios" add single and double quotes, but problem with null output is remain. When check is generate null in web interface, I see her output in docker logs:
I don't think that problem with nagios in docker ( we now run 3000 different checks without any trouble) + when hashicorp-vault-monitor generate "OK" - I see that in web interface. Trouble only when plugin generate "Warning" or "Critical" (also null outputs will be in other checks - I check that).
For example, I found thread - https://www.linuxquestions.org/questions/linux-software-2/nagios-interprets-perl-plugin-output-as-null-948605/, where similar problem (plugin written on perl)
May be same problem (or similar) in that plugin?