On 26/06/2014 1:06 a.m., Jasper Van Der Westhuizen wrote: > Hi all > > I'm running a compiled version of Squid 3.4.4 and I'm having some > strange behavior lately. I have a two node cluster load balancing via a > F5 LB and at times one of the two servers will simply not complete a > connection. Squid is running, the logs keep rolling(although much slower > and most entries are from it's sibling cache, but no connections go > through. A restart of Squid fixes this. > > As a matter of interest, in my cache logs I see many lines like these > > 2014/06/25 14:52:58 kid1| WARNING: swapfile header inconsistent with > available data > 2014/06/25 14:53:28 kid1| WARNING: swapfile header inconsistent with > available data > > On one of my servers I cleaned out the cache, as well as the swap.state > file but it didn't make a difference. > > squid -v output. > > Squid Cache: Version 3.4.4 > configure options: '--prefix=/usr/local/squid' > '--sysconfdir=/etc/squid3.4.4/' '--enable-follow-x-forwarded-for' > '--with-logdir=/var/log/squid/' '-with-pidfile=/var/run/squid.pid' > '--with-swapdir=/var/cache/squid/' '--with-large-files' > '--disable-strict-error-checking' '--with-default-user=squid' > > Can anyone shed some light on this problem? Are you using SMP workers with an AUFS, UFS or diskd cache_dir? UFS/AUFS/diskd are not SMP-aware and this is how it shows up when two or more workers are over-writing cache disk files and corrupting each others records. Amos
