>>> -----Original Message----- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>> Sent: Friday, August 05, 2005 5:40 AM >>> To: squid-users@squid-cache.org >>> Subject: [squid-users] Unable to rebuild cache >>> >>> >>> Squid's cache limit is set to 4GB. >>> When the cache fills up and squid attempts to rebuild, it >>> dies and reloads >>> itself continually, failing to rebuild the cache. >>> My squid.conf is below: >>> >>> -------------------- squid.conf ----------------------- >>> cache_effective_user nobody >>> log_fqdn on >>> http_port 8000 >>> icp_port 3130 >>> htcp_port 4827 >>> udp_incoming_address 0.0.0.0 >>> udp_outgoing_address 255.255.255.255 >>> tcp_outgoing_address 208.224.3.155 >>> icp_query_timeout 2000 >>> maximum_icp_query_timeout 2000 >>> mcast_icp_query_timeout 2000 >>> dead_peer_timeout 10 seconds >>> cache_mem 64 MB >>> maximum_object_size 20000 KB >>> half_closed_clients off >>> #cache_mem 4048 MB >>> cache_swap_low 95 >>> cache_swap_high 99 >>> #maximum_object_size 1000000 KB >>> minimum_object_size 0 KB >>> visible_hostname kalproxy.kalsec.com >>> cache_dir ufs /services/squid/var/cache 4048 16 256 >>> cache_access_log /services/squid/var/logs/access.log >>> cache_log /services/squid/var/logs/cache.log >>> ftp_passive on >>> ftp_sanitycheck off >>> refresh_pattern ^ftp: 1440 20% 10080 >>> refresh_pattern ^gopher: 1440 0% 1440 >>> refresh_pattern . 0 20% 4320 >>> quick_abort_min 0 KB >>> quick_abort_max 0 KB >>> quick_abort_pct 95 >>> acl kalmail src mail.kalsec.com >>> acl hitachi dst 192.168.1.117 >>> acl manager proto cache_object >>> acl intranet dst 192.168.1.0/255.255.255.0 >>> acl one_nine_two src 192.168.1.0/255.255.255.0 >>> acl one_seven_two_twenty_four src 172.24.0.0/255.255.0.0 >>> acl one_seven_two_sixteen_two_fifty src 172.16.250.0/255.255.255.0 >>> acl one_seven_two_twenty_four_ten src 172.24.10.0/255.255.255.0 >>> acl hr src 172.16.100.0/255.255.255.0 >>> acl vine src 192.168.2.0/255.255.255.0 >>> acl vpn src 192.168.99.0/255.255.255.0 >>> acl all src 0.0.0.0/0.0.0.0 >>> http_access allow kalmail >>> http_access allow intranet >>> http_access allow one_nine_two >>> http_access allow one_seven_two_twenty_four >>> http_access allow one_seven_two_sixteen_two_fifty >>> http_access allow one_seven_two_twenty_four_ten >>> http_access allow hr >>> http_access allow hitachi >>> http_access allow vpn >>> http_access allow manager >>> http_access allow vine >>> redirect_program /services/squidGuard/bin/squidGuard -c >>> /services/squid/etc/squidguard.conf >>> redirect_children 50 >>> cachemgr_passwd 8675309 >>> cache_mgr [EMAIL PROTECTED] >>> coredump_dir /services/squid/core >>> http_access deny all >>> ---------------------------squid.conf------------------------- >>> --------- >>> >>> Tim Rainier >>> >>> >> >> "Chris Robertson" <[EMAIL PROTECTED]> >> 08/05/2005 03:29 PM >> >> To >> <squid-users@squid-cache.org> >> cc >> >> Subject >> RE: [squid-users] Unable to rebuild cache >> >> The cache.log might hold some clues. Check it out, and if >> you don't see >> anything obvious, share it with the list. >> >> Chris >> > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, August 05, 2005 12:52 PM > To: squid-users@squid-cache.org > Subject: RE: [squid-users] Unable to rebuild cache > > > All it ever reported was that the store was 1.5% rebuilt and then it would > show it starting back up. > Yes, that's correct, it never even reported in the log that > it was quiting > and re-starting. > > Tim Rainier > >
At this point, I'd shut the proxy down, clear out the cache_dir (rm -rf /services/squid/var/cache/*) and the cache_swap_log (which is by default in the cache_dir, therefore would be cleared out by the above command), and start over (squid -z). If you are curious as to why the cache is failing to restart, running it under a debugger or checking the code dump *might* give more clues. Then again, that's just me. Chris
