| 2014-08-27 15:33:59 |
John Schwarz |
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. |
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 administrator. |
|
| 2014-08-27 15:34:11 |
John Schwarz |
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 administrator. |
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. |
|
