Hmm. I set it up that was a while ago and never had a problem (this was
with 3.1.6), and as I said, if I do a squid3 -k reconfigure, both sets
of things get written to the log file for some period of time. I haven't
had a chance to dig too far into it to determine when it stops logging.
I'll take a look at it tomorrow to see if I can get any further details.
(by the way, replies sent directly to you got rejected by your mail service)
Amos Jeffries wrote:
On 17/06/11 05:18, Farokh Irani wrote:
I'm running squid 3.1.12.2 on Ubuntu 10.04 LTS and I've been seeing a
strange problem with the logging.
I have the following in my squid.conf file:
logformat ourlogformat %tl %>a %Ss/%03>Hs %<st %rm %ru %un %Sh/%<A %mt
%et %ea
access_log /var/log/squid3/access.log ourlogformat
logformat icaplogformat %tl %>a %icap::to/%03icap::Hs %icap::rm
icap_log /var/log/squid3/access.log icaplogformat
What happens is that once squid is running, it logs everything (TCP_HIT,
MISS, etc) and then at some point it stops logging everything but the
ICAP entries.
If I do squid -k reconfigure the logging starts to work again.
Any ideas on what might be going on?
Or taking a closer look at the config itself. You have two parallel FD
overwriting each others data in the same file.
Amos
--
Farokh Irani
farokh@xxxxxxxxxxxxxxx
Skype: farokhitp
Phone: 914-262-1594
