← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1362213] Re: haproxy configuration spams logged-in users when no servers are available

 

** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1362213

Title:
  haproxy configuration spams logged-in users when no servers are
  available

Status in neutron:
  Fix Released

Bug description:
  On certain systems which use the default syslog configuration, using
  haproxy-based LBaaS causes error logs to spam all the logged-in users:

  Message from syslogd@alpha-controller at Jun  9 01:32:07 ...
   haproxy[2719]:backend 32fce5ee-b7f7-4415-a572-a83eba1be6b0 has no server available!

  Message from syslogd@alpha-controller at Jun  9 01:32:07 ...
   haproxy[2719]:backend 32fce5ee-b7f7-4415-a572-a83eba1be6b0 has no server available!

  The error message is valid - it happens when, for example, there are no backend servers available to handle the service requests because all members are down.
  However, there is no point in sending the messages to all the logged-in users. The wanted result is that each namespace will have its own log file, which will contain all the log messages that the relevant haproxy process produces. This log file should be placed in the $state_path/lbaas path along with the other files (conf, pid...), to be later accessed by the setup's administrator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1362213/+subscriptions


References