Nagios Support Forum

slansing wrote:have you tried with a different browser?

You're right. The problem exists in Chrome but not Firefox. I submit a bug report to Chrome. Hopefully it gets fixed... if they even see it as a problem.

I do not think this is a feature. Look what happens when I increase the width of my browser window. The problem with the long lines goes away. However, I don't like having my browser fully extended...

Hello, please see the attached screenshot. I have an HTTP probe checking a URL with a long string and this is causing the lines to do something funky and end up indenting. Is there a way to shorten the length of what is displayed in the alert log or is there another viable solution? Thanks in advance!

This has been resolved. It turns out the ampersands need to be double escaped when used in the configuration like in the example below. Now I feel kind of silly because I have a FreeBSD and CentOS Nagios server now.... check_hvac!/hvac_temp/index.php?mode=fetch\\&hvac=1\\&probe=1!"Unit0...

I thought it was pretty interesting too. And annoying. Single or double quotes do not make any difference. The problem is actually worse than I thought. I basically cannot use more than 1 argument with the check_http command. I think I've tried all the combinations I can. I could try installing a ne...

Yes, everything is installed. I have many probes set up for ping, basic http, smtp, etc. I am just having issues in this specific situation. Here is my ls output of the folder. However, I use FreeBSD so the lib folder is in a different location. My $USER1$ macro is also correctly set to $USER1$=/usr...

I tried creating a custom command and service and I get the same error message. define command{ command_name check_hvac command_line $USER1$/check_http -I $HOSTADDRESS$ -u $ARG1$ -s $ARG2$ } define service{ host_name HVACs service_description Unit01 Comp 1 Hot Gas Temperature check_command check_hva...

I tried that before even attempting to write anything to the config files and it runs fine but does not seem to work the way I have it in the config. [user@server ~]$ check_http -I 192.168.10.10 -u /hvac_temp/index.php?mode=fetch\&hvac=1\&probe=1 -s "Unit01 Hot Gas Bypass (Compressor 1)...

Hello all, I am trying to use -u and -s with the default check_http set up and it results in "Return code of 127 is out of bounds - plugin may be missing." Here is my command definition: define command{ command_name check_http command_line $USER1$/check_http -I $HOSTADDRESS$ $ARG1$ } Here ...