[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haproxy
Subject:    Re: logging to unix socket
From:       Bryan Talbot <btalbot () aeriagames ! com>
Date:       2010-12-30 18:45:33
Message-ID: AANLkTikuoR2JkzLhu23nU4=MS53WuspSwbUE3=Oscpzi () mail ! gmail ! com
[Download RAW message or body]

Ahh ok, restarting syslog fixed the issue.  I didn't realize that
the max_dgram_qlen setting would only take affect when the socket was bound.
 Our site is fairly busy but not a load for haproxy: we get several tens of
millions of hits a day.  What is a reasonable setting for max_dgram_qlen?

As far as synchronous writes goes, I've been using async for normal logs but
write errors from 'log-separate-errors' in sync mode.

Thank you for helping get my restarts clean with no more scary looking ALERT
messages!


-Bryan



On Thu, Dec 30, 2010 at 10:03 AM, Willy Tarreau <w@1wt.eu> wrote:

> On Thu, Dec 30, 2010 at 09:45:44AM -0800, Bryan Talbot wrote:
> > Oh, and the syslogger is sysklogd which is the distribution default I
> > believe.
>
> OK, sysklogd does synchronous writes by default. You must append a "-"
> (minus sign) in front of the file names to make it use asynchronous
> writes.
>
> > How can I tell what mode the socket uses?  If it used the wrong mode,
> > wouldn't logging not work in general because logging messages seem to be
> > received properly otherwise.
>
> If even one message is received, then it's working in the proper mode.
> You should restart it after you change the /proc setting BTW, since those
> settings are used only when binding the socket.
>
> But I'm pretty sure that with the async write, your problem will be gone.
>
> Willy
>
>

[Attachment #3 (text/html)]

Ahh ok, restarting syslog fixed the issue.  I didn&#39;t realize that the \
max_dgram_qlen setting would only take affect when the socket was bound.  Our site is \
fairly busy but not a load for haproxy: we get several tens of millions of hits a \
day.  What is a reasonable setting for max_dgram_qlen?<div> <br></div><div>As far as \
synchronous writes goes, I&#39;ve been using async for normal logs but write errors \
from &#39;log-separate-errors&#39; in sync mode.</div><div><br></div><div>Thank you \
for helping get my restarts clean with no more scary looking ALERT messages!</div> \
<div><br></div><div><br></div><div>-Bryan</div><div><br><br></div><div><br><div \
class="gmail_quote">On Thu, Dec 30, 2010 at 10:03 AM, Willy Tarreau <span \
dir="ltr">&lt;<a href="mailto:w@1wt.eu">w@1wt.eu</a>&gt;</span> wrote:<br> \
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex;"><div class="im">On Thu, Dec 30, 2010 at 09:45:44AM -0800, \
Bryan Talbot wrote:<br> &gt; Oh, and the syslogger is sysklogd which is the \
distribution default I<br> &gt; believe.<br>
<br>
</div>OK, sysklogd does synchronous writes by default. You must append a \
&quot;-&quot;<br> (minus sign) in front of the file names to make it use \
asynchronous<br> writes.<br>
<div class="im"><br>
&gt; How can I tell what mode the socket uses?  If it used the wrong mode,<br>
&gt; wouldn&#39;t logging not work in general because logging messages seem to be<br>
&gt; received properly otherwise.<br>
<br>
</div>If even one message is received, then it&#39;s working in the proper mode.<br>
You should restart it after you change the /proc setting BTW, since those<br>
settings are used only when binding the socket.<br>
<br>
But I&#39;m pretty sure that with the async write, your problem will be gone.<br>
<font color="#888888"><br>
Willy<br>
<br>
</font></blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]