Re: [squid-users] Log Daemon (queue is too large)
On Thu, Aug 14, 2014 at 8:43 AM, Amos Jeffries wrote: > > Are you using the default Squid daemon or a custom one? Its the default Squid daemon. > Can you reproduce this problem with the current 3.4 stable release? I have not tried just yet - its the first time I have come across this error. Searching the archives and Google turned up nothing. So I figured let me ask. > Are you able to identify what the daemon helper is doing when it is > loosing log lines? Unfortunately I did not think to see what the logfile-daemon was doing at the time and simply reconfigured squid. The next time it happens I'll be sure to do that. Thanks Amos. -- .warren
Re: [squid-users] Log Daemon (queue is too large)
On 13/08/2014 10:09 p.m., Warren Baker wrote: > HI all, > > I noticed this error message (multiple entries) for yesterday and > today on Squid 3.3.11 > > 2014/08/13 00:01:06 kid1| Logfile: > daemon:/util/var/squid/log/access.log: queue is too large; some log > messages have been lost. > > Its not a very high utilized proxy so I was a little surprised this > happened. I assume something may have caused a spike in traffic > resulting in the log buffer filling up but whats concerning is that it > never recovers until a -k reconfigure was issued, a -k rotate didnt > help. So all log entries for yesterday and today are gone. > > Any ideas on why it doesn't recover and possibly what could have > caused the issue? As looking at the access logs leading up to the > event there is nothing that stands out. Are you using the default Squid daemon or a custom one? Can you reproduce this problem with the current 3.4 stable release? Are you able to identify what the daemon helper is doing when it is loosing log lines? Amos
[squid-users] Log Daemon (queue is too large)
HI all, I noticed this error message (multiple entries) for yesterday and today on Squid 3.3.11 2014/08/13 00:01:06 kid1| Logfile: daemon:/util/var/squid/log/access.log: queue is too large; some log messages have been lost. Its not a very high utilized proxy so I was a little surprised this happened. I assume something may have caused a spike in traffic resulting in the log buffer filling up but whats concerning is that it never recovers until a -k reconfigure was issued, a -k rotate didnt help. So all log entries for yesterday and today are gone. Any ideas on why it doesn't recover and possibly what could have caused the issue? As looking at the access logs leading up to the event there is nothing that stands out. Thanks, Warren
