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! :) On Wed, Jul 16, 2014 at 4:08 PM, Baptiste <[email protected]> wrote: > On Wed, Jul 16, 2014 at 4:22 PM, Peter M Souter <[email protected]> > wrote: > > Hello All! > > > > I'm fairly new to Haproxy and I'm configurting it with puppet as a > reverse > > proxy for several web apps. > > > > An issue I'm running into right now is that we're not getting error logs > in > > a file, they're just sent to stdout like so: > > > > Message from syslogd@localhost at Jul 16 11:17:06 ... > > HAPROXY[8271]: backend foo has no server available! > > > > Right now the haproxy.cfg looks something like this: > > > > global > > maxconn 4096 > > user haproxy > > group haproxy > > daemon > > log 127.0.0.1 local0 debug > > log-tag HAPROXY > > > > And my rsyslog config looks like this: > > > > $ModLoad imudp > > $UDPServerRun 514 > > > > local0.* -/var/log/capd/haproxy.log > > > > I read through the documentation and saw the log-separate-errors flag, > if I > > turn this on will those errors that normally go to stdout go to the > file? Or > > will it go to a seperate file that I need to configure in Rsyslog? Thanks > > Regards > > > > Hi Peter, > > Have you looked into /var/log/capd/haproxy.log and look for the errors > here? > They should be there ;) > This is your syslog server which is printing this error on your > console, not HAProxy. > > Second, this is not a parsing error, but an error related to > load-balancing: HAProxy tells you that there is no servers available > in your farm . > none of them where able to positively answer to health checks. > > Baptiste >
