* Ingvar Hagelund > >> We've got this sort of strange problem: Given two squid web > >> proxy/cache servers with identical configuration; the first > >> works without problems, the second won't fill it's cache spool. > >> > >> We think we have checked the obvious, like file rights and > >> so, but any starting point for debugging would be very welcome. > >> > >> OS: Red Hat Enterprise Linux ES3, kernel 2.4.21-15.0.4.ELsmp > >> Daemon: squid-v2.5STABLE6 * Werner Rost > I suggest trying > > cd /squid (directory where your cache-dir is located) > chmod -R 777 * > > If this works you have to doublecheck your file permnissions. This had (not surprising) no effect. Here's en excerpt from the cache.log after a sighup. It looks quite sane to me. Ingvar 2005/12/08 06:11:07| Reconfiguring Squid Cache (version 2.5.STABLE6)... 2005/12/08 06:11:07| FD 7 Closing HTTP connection 2005/12/08 06:11:07| FD 39 Closing ICP connection 2005/12/08 06:11:07| FD 41 Closing SNMP socket 2005/12/08 06:11:07| Cache dir '/var/spool/squid/cache' size remains unchanged at 52428800 KB 2005/12/08 06:11:07| Store logging disabled 2005/12/08 06:11:07| DNS Socket created at 0.0.0.0, port 55370, FD 6 2005/12/08 06:11:07| Adding nameserver 10.42.42.42 from /etc/resolv.conf 2005/12/08 06:11:07| Adding nameserver 10.42.42.43 from /etc/resolv.conf 2005/12/08 06:11:07| Adding nameserver 10.42.42.44 from /etc/resolv.conf 2005/12/08 06:11:07| helperOpenServers: Starting 30 'squidGuard' processes 2005/12/08 06:11:10| Accepting HTTP connections at 0.0.0.0, port 8080, FD 7. 2005/12/08 06:11:10| Accepting ICP messages at 0.0.0.0, port 3130, FD 39. 2005/12/08 06:11:10| Accepting SNMP messages on port 3401, FD 41. 2005/12/08 06:11:10| Configuring Parent 127.0.0.1/8081/0 2005/12/08 06:11:10| Loaded Icons. 2005/12/08 06:11:10| Ready to serve requests. -- Many that live deserve death. And some that die deserve life. Can you give it to them? Then do not be too eager to deal out death in judgement. For even the very wise cannot see all ends. Gandalf
