yahoo-eng-team team mailing list archive

[John Schwarz <jschwarz@xxxxxxxxxx>]

Public bug reported:

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 the relevant haproxy process produces.

** Affects: neutron
     Importance: Undecided
     Assignee: John Schwarz (jschwarz)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => John Schwarz (jschwarz)

** Changed in: neutron
       Status: New => In Progress

-- 
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 OpenStack Neutron (virtual network service):
  In Progress

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 the relevant haproxy process produces.

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