Nagios Support Forum

Unfortunately, v.4.4.2 didn't solve the problem

I am manually checking the following: Node1: ./check_http --ssl --sni -E -I -t 10 -p 443 -H site1.mydomain.com -I 10.128.5.5 3 -u "/test123.txt" Node2: ./check_http --ssl --sni -E -I -t 10 -p 443 -H site1.mydomain.com -I 10.128.5.5 4 -u "/test123.txt" This seems to work as expect...

Thanks for your reply. mcapra : I am configuring servers/services using exactly the same philosophy (no Kubernetes though). Specific nodes are being checked from the Load Balancers (F5) for their availability based on various metrics. If the nodes are not responding are being removed from the pool. ...

Try sendEmail.pl from here: http://caspian.dotconf.net/menu/Software/SendEmail/

Hello everyone,

I have a cluster composed from two nodes.
All users normally access the various sites through the cluster IP.
I host various sites on each node. All DNS/vhost point to the cluster IP.

How can I monitor the availability of the sites on each node?

Regards

Sorry, but I cannot delete retention.dat !! It will create chaos in my installation!

Updating the state for specific service, those with problems, will not fix the problem?

I am using 4.4.1 with some fixes from git; downloaded on 20180813 and is probably version 4.4.2 .
So I hit a bug again?

Would you like to install the current main branch and check if the problem is fixed?

I have configured a service as follows: it will send an alert only to critical & recovery states. However, I am receiving numerous recovery alerts but no critical. The service indeed is changing states between OK and Warning: Snap1.png define service{ use generic-service host_name HOST service_d...

scottwilkerson wrote:

amprantino wrote:Is nagios interpreting "\n" to the webinterface for some reason?

Yes, the GUI would interpret \n as a new line

Thx - I will open a ticket there for some issues. I couldn't find a link to github from their official site.

I agree something certainly is not correct, the examples with | tee -a /tmp/TEST1 shows the command is displaying in Nagios exactly what is being output from the command when Nagios runs it. Check also this output: ./check_mssql_health --server 'sqlserer\PROD' --port 12345--username 'gateway\nagios...