[squid-users] squid smp fails -k reconfigure

Hi there,

Since I enabled SMP mode on my squid 3.4.3 server, reconfiguring is not
working consitently. Here's the relevant log entries:

------------------
2014/06/02 11:35:37| Set Current Directory to /cache
2014/06/02 11:35:37 kid6| Reconfiguring Squid Cache (version 3.4.3)...
2014/06/02 11:35:37 kid6| Logfile: closing log
stdio:/var/log/squid/access.log
2014/06/02 11:35:37 kid5| Reconfiguring Squid Cache (version 3.4.3)...
...
2014/06/02 11:35:37 kid6| ERROR opening swap log
/cache/worker6/swap.state: (2) No such file or directory
2014/06/02 11:35:37 kid5| ERROR opening swap log
/cache/worker5/swap.state: (2) No such file or directory
2014/06/02 11:35:37 kid5| storeDirWriteCleanLogs: Starting...
2014/06/02 11:35:37 kid5| log.clean.start() failed for dir #1
2014/06/02 11:35:37 kid5| Finished. Wrote 0 entries.
2014/06/02 11:35:37 kid5| Took 0.00 seconds ( 0.00 entries/sec).
FATAL: UFSSwapDir::openLog: Failed to open swap log.
Squid Cache (Version 3.4.3): Terminated abnormally.
FATAL: UFSSwapDir::openLog: Failed to open swap log.
Squid Cache (Version 3.4.3): Terminated abnormally.
------------------

I find very strange that workers 6 and 5 try to get aufs cache stores.
They are supposed to be the rock store disker and the coordinator! My
squid.conf has:

workers 4
cache_mem 6144 MB
cache_dir rock /cache/shared 30000 min-size=1 max-size=31000
max-swap-rate=250 swap-timeout=350
cache_dir aufs /cache/worker${process_number} 25000 16 256
min-size=31001 max-size=346030080
logfile_rotate 4

Would squid be having troubles with my cache_mem and cache_dir big sizes?

Is squid -k reconfigure working well for everyone else with SMP?

Other strange entries, from earlier in the cache.log:
---------------------
2014/06/01 03:13:05 kid5| Set Current Directory to /cache
2014/06/01 03:13:05 kid5| Starting Squid Cache version 3.4.3 for
x86_64-redhat-linux-gnu...
2014/06/01 03:13:05 kid5| Process ID 23990
2014/06/01 03:13:05 kid5| Process Roles: disker
2014/06/01 03:13:05 kid5| With 65536 file descriptors available
2014/06/01 03:13:05 kid5| Initializing IP Cache...
2014/06/01 03:13:05 kid5| DNS Socket created at 0.0.0.0, FD 7
2014/06/01 03:13:05 kid5| Adding nameserver 200.20.212.75 from
/etc/resolv.conf
2014/06/01 03:13:05 kid5| Adding nameserver 200.20.212.99 from
/etc/resolv.conf
2014/06/01 03:13:05 kid5| Adding domain inmetro.gov.br from /etc/resolv.conf
2014/06/01 03:13:05 kid5| Adding domain inmetro.gov.br from /etc/resolv.conf
2014/06/01 03:13:05 kid5| helperOpenServers: Starting 10/100
'basic_ldap_auth' processes
---------------------

If kid5 is a disker, why does it setups up dns resolver and ldap auth
helpers? It looks like disker and coordinator try to process all
squid.conf directives, even when they are supposed not to do any
network-related stuff.

Should I try to "hide" those directives from them?

I also got something strange on shutdown:

----------------
2014/06/02 14:36:47| Set Current Directory to /cache
2014/06/02 14:36:47 kid6| Preparing for shutdown after 0 requests
2014/06/02 14:36:47 kid6| Waiting 5 seconds for active connections to finish
...
2014/06/02 14:36:53 kid6| Shutting down...
2014/06/02 14:36:53 kid6| Not currently OK to rewrite swap log.
2014/06/02 14:36:53 kid6| storeDirWriteCleanLogs: Operation aborted.
-----------------

What means "not OK to rewrite swap log"? kid6 is the coordinator, it
shoud not mess with cache dirs!

[]s, Fernando Lozano
Received on Thu Jun 05 2014 - 16:54:31 MDT