[squid-users] Problem with access.log and when using SMP

[Giorgi Tepnadze]

Hello,

I have own squid log parsing software which worked flawlessly before we 
moved to squid 3.3.8 (old was 2.7). Log parser stopped working. This is 
the problem I found.

Problem lines:
1416971036.802 184393 10.xx.xx.xx TCP_MISS/200 10963 CONNECT 
pixel.facebook.com:1416971036.390      0 10.yy.yy.yy TCP_DENIED/407 3751 
CONNECT clients4.google.com:443 - HIER_NONE/- text/html
1416971036.645   7164 10.zz.zz.zz TCP_MISS/200 55438 GET 
http://s40.radikal.ru/i089/1107/9b/2fbf1779ead9.jpg user at domain.com 
HIER_DIRECT/81.176.238.141 image/jpeg
443 user2 at domainc.com HIER_DIRECT/31.13.93.3 -

As it should be:
1416971036.390      0 10.yy.yy.yy TCP_DENIED/407 3751 CONNECT 
clients4.google.com:443 - HIER_NONE/- text/html
1416971036.802 184393 10.xx.xx.xx TCP_MISS/200 10963 CONNECT 
pixel.facebook.com:443 user2 at domainc.com HIER_DIRECT/31.13.93.3 -
1416971036.645   7164 10.zz.zz.zz TCP_MISS/200 55438 GET 
http://s40.radikal.ru/i089/1107/9b/2fbf1779ead9.jpg user at domain.com 
HIER_DIRECT/81.176.238.141 image/jpeg

I think that's because of SMP as I have 4 squid kids running and they 
all write to same access.log file and there is concurrency problem. 
Sometimes one is writing log line when previous log line is not finished 
yet or something like this. Such errors are rare but enough to stop my 
parser with  error.

Is it a bug? Is there any workaround or solution?

-- George Tepnadze