Gatt Posted October 10, 2006 Posted October 10, 2006 OK Squid/DG was working fine till today Sites were becoming slow to hit, and now no one can hit anything It is set to use the LEA's ISA server as its "parent" but when i stop/start squid i see this error startproc: exit status of parent of /usr/sbin/squid: 1 Squid reports as starting, DG fails to start tho. Have checked the config as best i can and all seems ok the cache_peer peer line is as follows cache_peer 8080 3128 proxy-only default login=
Geoff Posted October 10, 2006 Posted October 10, 2006 What do the log files say. The cache.log in paticular?
Gatt Posted October 10, 2006 Author Posted October 10, 2006 2006/10/10 11:28:13| Configuring Parent 10.201.2.7/8080/3128 2006/10/10 11:28:13| Ready to serve requests. 2006/10/10 11:28:13| Done reading /var/cache/squid swaplog (15 entries) 2006/10/10 11:28:13| Finished rebuilding storage from disk. 2006/10/10 11:28:13| 15 Entries scanned 2006/10/10 11:28:13| 0 Invalid entries. 2006/10/10 11:28:13| 0 With invalid flags. 2006/10/10 11:28:13| 15 Objects loaded. 2006/10/10 11:28:13| 0 Objects expired. 2006/10/10 11:28:13| 0 Objects cancelled. 2006/10/10 11:28:13| 0 Duplicate URLs purged. 2006/10/10 11:28:13| 0 Swapfile clashes avoided. 2006/10/10 11:28:13| Took 0.4 seconds ( 38.9 objects/sec). 2006/10/10 11:28:13| Beginning Validation Procedure 2006/10/10 11:28:13| Completed Validation Procedure 2006/10/10 11:28:13| Validated 15 Entries 2006/10/10 11:28:13| store_swap_size = 384k 2006/10/10 11:28:14| storeLateRelease: released 0 objects 2006/10/10 11:28:38| temporary disabling (Proxy Authentication Required) digest from 10.201.2.7 2006/10/10 11:29:34| Detected DEAD Parent: 10.201.2.7/8080/3128 2006/10/10 11:33:38| temporary disabling (Proxy Authentication Required) digest from 10.201.2.7 2006/10/10 11:43:40| temporary disabling (Proxy Authentication Required) digest from 10.201.2.7 2006/10/10 12:03:41| temporary disabling (Proxy Authentication Required) digest from 10.201.2.7 2006/10/10 12:43:41| temporary disabling (Proxy Authentication Required) digest from 10.201.2.7 lithium:/var/log/squid # Now the weird bit - despite the "dead parent" line - i am currently writing this post whilst IE is configured to use that addresss ! So that server is alive and well!
Geoff Posted October 10, 2006 Posted October 10, 2006 Have you told Squid to use some sort of peering arrangement the other cache does not support? eg, ICP? What does your cache_peer line look like?
Gatt Posted October 10, 2006 Author Posted October 10, 2006 cache_peer 10.201.2.7 parent 8080 3128 proxy-only no-delay login=domain\username:password
Gatt Posted October 10, 2006 Author Posted October 10, 2006 cache_peer 10.201.2.7 parent 8080 3128 proxy-only no-delay login=domain\username:password The service starts - as does dansguardian - but cannot get to any site other than http://www.google.co.uk No other URL will work nor will any google search.
Geoff Posted October 10, 2006 Posted October 10, 2006 Ok, so your parent cache is running ICP on port 3128? Also, if the parent cache fails, there's direct internet access?
Gatt Posted October 10, 2006 Author Posted October 10, 2006 No, if the LEA's ISA fails then we're dead in the water - guessing that I've missed a bit out then?
Geoff Posted October 10, 2006 Posted October 10, 2006 Yes, your cache_peer line says: My upstream proxy is 10.201.2.7:8080 I need to login to it I can query it with ICP on port 3128. If it's dead I can access the internet directly. The combination of the second two is whats causing the problem. Try this instead: cache_peer 10.201.2.7 parent 8080 0 no-query default login=domain\username:password Presumably you also have a: never_direct allow all Somewhere in your ACL's too?
Gatt Posted October 10, 2006 Author Posted October 10, 2006 Yep though when i use never_direct acl all i get this when i try to stop/start squid ACL name 'all' not defined! FATAL: Bungled squid.conf line 364: never_direct allow all yet later in the code I have acl all src 0.0.0.0/0.0.0.0
Gatt Posted October 10, 2006 Author Posted October 10, 2006 Sorted it! The never_direct acl all was in the wrong place!!
Geoff Posted October 10, 2006 Posted October 10, 2006 Yes, you need to have the directive after your acl definition because squid reads it's configuration top to bottom rather than all at once.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now