Scalix Forums

I have been setting up the various commands and services to monitor our Scalix install on our existing Nagios machine. I have a couple of problems:

1: How to setup the checks for the SWA and other web services?

Since we are running tomcat on 8443, I made the changes to the commands as follows: (uneccessary text removed)

check_ubermanager
command_line $USER1$/check_http -H $HOSTADDRESS$ -u /caa?query=monitor -p 8443

check_res
command_line $USER1$/check_http -H $HOSTADDRESS$ -u /res/RESDispatcher?query=monitor -p 8443

check_swa
command_line $USER1$/check_http -H $HOSTADDRESS$ -u /webmail/ -p 8443

These all return "Invalid HTTP response received from host on port 8443"

2: Settings for the check_queues, check_daemons and check_services

These all fail with "no output" but I can run any of them as root. The command for each is listed as

command_line sudo $USER1$/check_queues.py -c $ARG1$ -w $ARG2$ -q $ARG3$

So I added the nagios user to the /etc/sudoers file, but still no luck?

BigBirdy wrote:I have been setting up the various commands and services to monitor our Scalix install on our existing Nagios machine. I have a couple of problems:

1: How to setup the checks for the SWA and other web services?

Since we are running tomcat on 8443, I made the changes to the commands as follows: (uneccessary text removed)

check_ubermanager
command_line $USER1$/check_http -H $HOSTADDRESS$ -u /caa?query=monitor -p 8443

check_res
command_line $USER1$/check_http -H $HOSTADDRESS$ -u /res/RESDispatcher?query=monitor -p 8443

check_swa
command_line $USER1$/check_http -H $HOSTADDRESS$ -u /webmail/ -p 8443

These all return "Invalid HTTP response received from host on port 8443"

2: Settings for the check_queues, check_daemons and check_services

These all fail with "no output" but I can run any of them as root. The command for each is listed as

command_line sudo $USER1$/check_queues.py -c $ARG1$ -w $ARG2$ -q $ARG3$

So I added the nagios user to the /etc/sudoers file, but still no luck?

Hello,

with regard to the first part of your question :

Please use --ssl on the command line as you are connecting to an SSL server, e.g.

command_line $USER1$/check_http --ssl -H $HOSTADDRESS$ -u /caa?query=monitor -p 8443

Cheers,

Sascha.

Thanik for the suggestion. It worked for the ubermanager check and returned...

OK - HTTP/1.1 302 Moved Temporarily - 0.092 second response time

But the basic check for the SWA does not? Running the command manually returns the following...

./check_http --ssl -H 192.168.1.3 -u /res/RESDispatcher?query=monitor -p 8443


HTTP WARNING: HTTP/1.1 404 /res/RESDispatcher


Anything else I might be missing?

BigBirdy wrote:Thanik for the suggestion. It worked for the ubermanager check and returned...

OK - HTTP/1.1 302 Moved Temporarily - 0.092 second response time

But the basic check for the SWA does not? Running the command manually returns the following...

./check_http --ssl -H 192.168.1.3 -u /res/RESDispatcher?query=monitor -p 8443


HTTP WARNING: HTTP/1.1 404 /res/RESDispatcher


Anything else I might be missing?

Actually, for monitoring purposes it would be sufficient to just not pass a URL on and by the mere fact that you are getting a response on that port you can be certain the box still lives. So why don't you try that? The error codes you are getting back are standard http error codes, a redirect and a page not found. Both are due to the URL passed.

Cheers,

Sascha.