From the man page:
Alive value
Specify how often Pound will check for resurected back-end
hosts (default: 30 seconds). In general, it is a good idea to set this as low
as possible - it will find resurected
hosts faster. However, if you set it too low it will consume
resources - so beware.
Alive only determines how often pound checks to see if the host is alive
*after* it’s already been marked dead. HAPort would be for more ongoing checks.
I use what you describe in your PS. (http-based URL checks w/ Nagios in my
environment)
Joe
From: van Melis Jean-Pierre [mailto:[email protected]]
Sent: Tuesday, June 18, 2013 2:00 AM
To: [email protected]
Subject: AW: [Pound Mailing List] poundctl doesn't detect a dead backend until
that backend is needed
Okay, fair enough...
Just wanted to make sure it wasn't something that was supposed to work and was
now broken.
In pound.cfg the "## check backend every X secs: Alive 30" somewhat
implies the backends are checked every 30 seconds...
Cheers,
JP
PS To get the monitoring I was after I could combine it of course with a
httping-check to the URL's I think are vital.
-----Oorspronkelijk bericht-----
Afzender: Joe Gooch <[email protected]<mailto:[email protected]>>
Verstuurd: Maandag 17 Juni 2013 23:43
Aan: '[email protected]' <[email protected]<mailto:[email protected]>>
Onderwerp: RE: [Pound Mailing List] poundctl doesn't detect a dead backend
until that backend is needed
Poundctl doesn’t detect anything, poundctl just shows what Pound has detected,
and pound only discovers dead backends when it makes a request, or if you are
using HAPort functions (with an appropriate helper script) in the pound config.
Joe
From: van Melis Jean-Pierre [mailto:[email protected]]
Sent: Saturday, June 15, 2013 4:25 AM
To: [email protected]<mailto:[email protected]>
Subject: [Pound Mailing List] poundctl doesn't detect a dead backend until that
backend is needed
Hi All,
I'm monitoring a lot of stuff with Zabbix and recently I thought of monitoring
my backends of pound.
One can configure Zabbix to call programs on the computer which is running the
agent, so I'm calling "poundctl" to count the amount of backends and also the
ones that are dead
/etc/zabbix/zabbix_agentd.conf now contains these lines
UserParameter=pound.backends.active, sudo poundctl -c
/var/run/pound/poundctl.socket 2>/dev/null | grep -ci 'Backend .* active'
UserParameter=pound.backends.alive, sudo poundctl -c
/var/run/pound/poundctl.socket 2>/dev/null | grep -ci 'Backend .* active .*
alive'
UserParameter=pound.backends.dead, sudo poundctl -c
/var/run/pound/poundctl.socket 2>/dev/null | grep -ci 'Backend .* active .*
DEAD'
UserParameter=pound.services, sudo poundctl -c /var/run/pound/poundctl.socket
2>/dev/null | grep -ci 'Service .* active'
UserParameter=pound.listeners, sudo poundctl -c /var/run/pound/poundctl.socket
2>/dev/null | grep -ci ' Listener '
All the results in my dashboard corresponds with the output of poundctl
I noticed that poundctl doesn't detect a dead backend until pound has to
actually handle that backend.
Do I need some additional directives in my config to achieve the result I'm
after or is it not possible?
Maybe I need to do something else to detect a backend that's down?
The command that I expected to use is:
sudo poundctl -c /var/run/pound/poundctl.socket 2>/dev/null | grep
-ci 'Backend .* active .* DEAD'
This is the header of my config:
cat /etc/pound/pound.cfg
######################################################################
## global options:
User "www-data"
Group "www-data"
#RootJail "/chroot/pound"
## Logging: (goes to syslog by default)
## 0 no logging
## 1 normal
## 2 extended
## 3 Apache-style (common log format)
LogLevel 3
## check backend every X secs:
Alive 30
## use hardware-accelleration card supported by openssl(1):
#SSLEngine "<hw>"
# poundctl control socket
Control "/var/run/pound/poundctl.socket"
