Hi Peter,
Le 16/07/2014 17:28, Peter M Souter a écrit :
Yeah, I looked in the logs before and I couldn't find the errors. But
either I didn't look hard enough or someone's changed the settings since
I last looked:
cat /var/log/capd/haproxy.log | grep 'has no server available!' | wc -l
46
But at least I can confirm I got the correct setup! :)
To complete Baptiste's answer, this is probably because your rsylog
configuration contains something like :
*.emerg :omusrmsg:*
haproxy has also an option to reduce the range of log levels :
log <address> [len <length>] <facility> [max level [min level]]
I tend to use "err" as the value for "min level", in order to never
reach the "emerg" level : any log with a level lower than err (crit,
alert, emerg) will be logged as a err level, which prevent such messages
for logged users when the rsyslog configuration is not guaranted.
See [1] for more details.
As a side note, please don't top post when your reply (and really reply,
not forward) ;-)
[1] http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#3.1-log
--
Cyril Bonté
