[squid-users] Using squidclient
I'm trying to use squidclient to get some information on the performance of one
of our squid boxes. The version is 2.7x.
See below..
--
dss-cs99lv02-a:/usr/local/squid/bin # nmap localhost
Starting Nmap 4.00 ( http://www.insecure.org/nmap/ ) at 2010-05-21 14:16 CDT
Interesting ports on localhost (127.0.0.1):
(The 1665 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
111/tcp open rpcbind
427/tcp open svrloc
2033/tcp open glogger
2034/tcp open scoremgr
8080/tcp open http-proxy
Nmap finished: 1 IP address (1 host up) scanned in 0.146 seconds
dss-cs99lv02-a:/usr/local/squid/bin # ./squidclient -p8080 mgr:5_min
HTTP/1.0 404 Not Found
Server: squid/2.7.STABLE6
Date: Fri, 21 May 2010 19:17:01 GMT
Content-Type: text/html
Content-Length: 1229
X-Squid-Error: ERR_INVALID_URL 0
X-Cache: MISS from dss-cs99lv02-a
Via: 1.0 dss-cs99lv02-a:8080 (squid/2.7.STABLE6)
Connection: close
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
http://www.w3.org/TR/html4/loose.dtd;
HTMLHEADMETA HTTP-EQUIV=Content-Type CONTENT=text/html;
charset=iso-8859-1
TITLEERROR: The requested URL could not be retrieved/TITLE
STYLE
type=text/css!--BODY{background-color:#ff;font-family:verdana,sans-serif}PRE{font-family:sans-serif}--/STYLE
/HEADBODY
H1ERROR/H1
H2The requested URL could not be retrieved/H2
HR noshade size=1px
P
While trying to retrieve the URL:
A
HREF=cache_object://localhost.dss.state.la.us/5_mincache_object://localhost.dss.state.la.us/5_min/A
P
The following error was encountered:
UL
LI
STRONG
Invalid URL
/STRONG
/UL
P
Some aspect of the requested URL is incorrect. Possible problems:
UL
LIMissing or incorrect access protocol (should be `http://'' or similar)
LIMissing hostname
LIIllegal double-escape in the URL-Path
LIIllegal character in hostname; underscores are not allowed
/UL
PYour cache administrator is A HREF=mailto:webmaster;webmaster/A.
BR clear=all
HR noshade size=1px
ADDRESS
Generated Fri, 21 May 2010 19:17:01 GMT by dss-cs99lv02-a (squid/2.7.STABLE6)
/ADDRESS
/BODY/HTML
dss-cs99lv02-a:/usr/local/squid/bin #
as you can see, Squid is running on port 8080 of the local box, however,
when I run squidclient it appears to display the HTML rather than displaying
the metric I am looking for. Any ideas?
RE: [squid-users] Testing website I have set not to cache.
2010/5/20 Henrik Nordström hen...@henriknordstrom.net: ons 2010-05-19 klockan 14:03 -0500 skrev Ryan McCain: I have this set in my Squid 2.7 conf file.. #5/19/10 - Added to bypass Webex caching acl webex dstdomain .webex.com #5/19/20 - Added to not cache webex cache deny webex ...How can I verify Squid isn't caching anything going to Webex.com? Monitor cache.log and look for requests with TCP_HIT in their status code. Should that be access.log? :) So, if I see this then these requests ARE being cached? 1274366775.203 54 10.120.100.235 TCP_MISS/200 39 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - 1274366775.708554 10.120.100.235 TCP_MISS/200 6147 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - 1274366775.898164 10.120.100.235 TCP_MISS/200 3419 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - 1274366779.316 3394 10.120.100.235 TCP_MISS/200 7296 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - 1274366779.936170 10.120.100.235 TCP_MISS/200 2607 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - 1274366780.042703 10.120.100.235 TCP_MISS/200 30638 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - 1274366780.195425 10.120.100.235 TCP_MISS/200 11939 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - 1274366780.322214 10.120.100.235 TCP_MISS/200 3399 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - 1274366782.305 62237 10.120.100.235 TCP_MISS/200 3275 CONNECT dssla.webex.com:443 - DIRECT/64.68.104.194 - ..If so, what is wrong w/ the config that I posted? -- Tech support agency in China http://duxieweb.com/
[squid-users] Testing website I have set not to cache.
I have this set in my Squid 2.7 conf file.. #5/19/10 - Added to bypass Webex caching acl webex dstdomain .webex.com #5/19/20 - Added to not cache webex cache deny webex ...How can I verify Squid isn't caching anything going to Webex.com? Thanks..
RE: [squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57'
Thanks for the response. According to Websense, they only suppor 2.5x. :( Also, I will contact the site owner now and ask about this issue. Here are the headers using the Firefox Live Headers plugin. I'm not sure what it means, but I have the POST setting set to ACCURATE. This is when it doesn't work (going through a POP proxy v2.5 then up through our top level proxy v2.7): --- http://site463.mysite4now.net/mrengmal/gm/forum/login.asp POST http://site463.mysite4now.net/mrengmal/gm/forum/login.asp HTTP/1.1 Host: site463.mysite4now.net User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Proxy-Connection: keep-alive Referer: http://site463.mysite4now.net/mrengmal/gm/forum/login.asp?target=default.asp Cookie: Snitz00User=; ASPSESSIONIDQCASABDC=KHNDCKLCEEENIEDJCADGOLAD; ASPSESSIONIDQCBTBBCC=FDFFFLLCCDKFBDLJOOPELEMD; ASPSESSIONIDSABQCACC=GKKNJOLCAMCFDIELLEDGIHLB; ASPSESSIONIDQABSCCAC=PMAPIPLCFECHCPDDNEBCPDAH; ASPSESSIONIDSCBSCDBC=JKIDMAMCKODFGGNAMIOKAHDK Content-Type: application/x-www-form-urlencoded Content-Length: 101 target=default.aspName=studentsubmit1.x=33submit1.y=5submit1=LoginPassword=sswSavePassWord=true HTTP/1.0 500 Internal Server Error Date: Thu, 18 Feb 2010 18:08:15 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Length: 5339 Content-Type: text/html Set-Cookie: Snitz00User=Pword=80fef94b3945d30bd0adf30fa9915276881765b719c14f7ffa29f1128f11c1f9Name=student; expires=Sat, 20-Mar-2010 20:08:14 GMT; path=/ Cache-Control: private X-Cache: MISS from dss-cs99lv03-a, MISS from proxy-mon.dss.la.gov Via: 1.1 dss-cs99lv03-a:8080 (squid/2.7.STABLE6) X-Cache-Lookup: MISS from proxy-mon.dss.la.gov:8080 Proxy-Connection: close -- - This is when it does work going directly through a top level proxy (v2.7) --- http://site463.mysite4now.net/mrengmal/gm/forum/login.asp POST http://site463.mysite4now.net/mrengmal/gm/forum/login.asp HTTP/1.1 Host: site463.mysite4now.net User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Proxy-Connection: keep-alive Referer: http://site463.mysite4now.net/mrengmal/gm/forum/login.asp?target=default.asp Cookie: Snitz00User=; ASPSESSIONIDQCASABDC=KHNDCKLCEEENIEDJCADGOLAD; ASPSESSIONIDQCBTBBCC=FDFFFLLCCDKFBDLJOOPELEMD; ASPSESSIONIDSABQCACC=GKKNJOLCAMCFDIELLEDGIHLB; ASPSESSIONIDQABSCCAC=PMAPIPLCFECHCPDDNEBCPDAH; ASPSESSIONIDSCBSCDBC=JKIDMAMCKODFGGNAMIOKAHDK Content-Type: application/x-www-form-urlencoded Content-Length: 101 target=default.aspName=studentsubmit1.x=20submit1.y=8submit1=LoginPassword=sswSavePassWord=true HTTP/1.0 200 OK Date: Thu, 18 Feb 2010 18:10:48 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Length: 6646 Content-Type: text/html Set-Cookie: Snitz00User=Pword=80fef94b3945d30bd0adf30fa9915276881765b719c14f7ffa29f1128f11c1f9Name=student; expires=Sat, 20-Mar-2010 20:10:46 GMT; path=/ Cache-Control: private X-Cache: MISS from dss-cs99lv02-a Via: 1.1 dss-cs99lv02-a:8080 (squid/2.7.STABLE6) Connection: keep-alive Proxy-Connection: keep-alive -- http://site463.mysite4now.net/mrengmal/gm/forum/default.asp GET http://site463.mysite4now.net/mrengmal/gm/forum/default.asp HTTP/1.1 Host: site463.mysite4now.net User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Proxy-Connection: keep-alive Cookie: Snitz00User=Pword=80fef94b3945d30bd0adf30fa9915276881765b719c14f7ffa29f1128f11c1f9Name=student; ASPSESSIONIDQCASABDC=KHNDCKLCEEENIEDJCADGOLAD; ASPSESSIONIDQCBTBBCC=FDFFFLLCCDKFBDLJOOPELEMD; ASPSESSIONIDSABQCACC=GKKNJOLCAMCFDIELLEDGIHLB; ASPSESSIONIDQABSCCAC=PMAPIPLCFECHCPDDNEBCPDAH; ASPSESSIONIDSCBSCDBC=JKIDMAMCKODFGGNAMIOKAHDK HTTP/1.0 200 OK Date: Thu, 18 Feb 2010 18:10:50 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Length: 17878 Content-Type: text/html Cache-Control: private X-Cache: MISS from dss-cs99lv02-a Via: 1.1 dss-cs99lv02-a:8080 (squid/2.7.STABLE6) Connection: keep-alive Proxy-Connection: keep-alive -- Does anything stick out? Ryan McCain Northrop Grumman Corporation Email: ryan.mcc...@la.gov Phone: 225.505.3832 Registered Linux User #364609 -Original Message- From
RE: [squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57'
BTW, Websense does support Squid 2.6. Would upgrading from 2.5 to 2.6 possibly help? Ryan McCain Northrop Grumman Corporation Email: ryan.mcc...@la.gov Phone: 225.505.3832 Registered Linux User #364609 -Original Message- From: Henrik Nordström [mailto:hen...@henriknordstrom.net] Sent: Thursday, February 18, 2010 4:37 AM To: Ryan McCain Cc: 'squid-users@squid-cache.org' Subject: Re: [squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57' tor 2010-02-11 klockan 11:22 -0600 skrev Ryan McCain: We are using Squid 2.5 on SLES for compatibility reasons with a redirector we use at the POP level , Websense. Websebse doesn't support 2.7 or 3.x. Any external helpers (url rewriters, auth etc) which works with 2.5 also works in later releases. Anyways, if you go to http://www.garymallon.com -- COURSES -- DISCUSSION BOARD then login with: User: student Pw: ssw I get the following error: Microsoft JET Database Engine error '80040e57' The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data. /mrengmal/gm/forum/inc_func_common.asp, line 585 This is difficult to answer without knowing the web server application. Have you tried talking to the maintainers of that forum? A guess is that they are storing the X-Forwarded-For header in their database for tracking purposes and have assigned to small field with for storing that.. Regards Henrik
RE: [squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57'
I tried upgrading to 2.6 on one of the nodes of a POP cluster and it didn't work. To further troubleshoot this, I'm going to attempt to upgrade to 2.7 on one of the POP cluster nodes. Ryan McCain Northrop Grumman Corporation Email: ryan.mcc...@la.gov Phone: 225.505.3832 Registered Linux User #364609 -Original Message- From: Ryan McCain [mailto:ryan.mcc...@la.gov] Sent: Thursday, February 18, 2010 12:21 PM To: 'Henrik Nordström' Cc: 'squid-users@squid-cache.org' Subject: RE: [squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57' BTW, Websense does support Squid 2.6. Would upgrading from 2.5 to 2.6 possibly help? Ryan McCain Northrop Grumman Corporation Email: ryan.mcc...@la.gov Phone: 225.505.3832 Registered Linux User #364609 -Original Message- From: Henrik Nordström [mailto:hen...@henriknordstrom.net] Sent: Thursday, February 18, 2010 4:37 AM To: Ryan McCain Cc: 'squid-users@squid-cache.org' Subject: Re: [squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57' tor 2010-02-11 klockan 11:22 -0600 skrev Ryan McCain: We are using Squid 2.5 on SLES for compatibility reasons with a redirector we use at the POP level , Websense. Websebse doesn't support 2.7 or 3.x. Any external helpers (url rewriters, auth etc) which works with 2.5 also works in later releases. Anyways, if you go to http://www.garymallon.com -- COURSES -- DISCUSSION BOARD then login with: User: student Pw: ssw I get the following error: Microsoft JET Database Engine error '80040e57' The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data. /mrengmal/gm/forum/inc_func_common.asp, line 585 This is difficult to answer without knowing the web server application. Have you tried talking to the maintainers of that forum? A guess is that they are storing the X-Forwarded-For header in their database for tracking purposes and have assigned to small field with for storing that.. Regards Henrik
RE: [squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57'
According to this: http://www.squid-cache.org/Versions/v2/2.6/cfgman/header_access.html 2.6 uses header_access Hoping it was the same for 2.5x, I entered this into squid.conf header_access X-Forwarded-For deny all ...and it worked like a charm. How did you know it was the X-Forwarded-For header? -Original Message- From: Henrik Nordström [mailto:hen...@henriknordstrom.net] Sent: Thursday, February 18, 2010 12:35 PM To: Ryan McCain Cc: 'squid-users@squid-cache.org' Subject: RE: [squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57' tor 2010-02-18 klockan 12:21 -0600 skrev Ryan McCain: BTW, Websense does support Squid 2.6. Would upgrading from 2.5 to 2.6 possibly help? Most likely not as the error seems to be on the web server and not Squid. What you can try is to filter out the X-Forwarded-For header to see if that makes any difference. request_header_access X-Forwarded-For deny all [not sure the above syntax works in 2.5.. may be it's header_access, or mabe even older directives, memory of 2.5 and even 2.6 have faded] Regards Henrik
[squid-users] Tiered Squid proxy issue (Microsoft JET Database Engine error '80040e57'
This is a strange one. We have a 2 tiered Squid environment here. We have Squid at the POP region level each of those 5 POPs go to 2 top level Squid servers which go to the internet. We are using Squid 2.5 on SLES for compatibility reasons with a redirector we use at the POP level , Websense. Websebse doesn't support 2.7 or 3.x. Anyways, if you go to http://www.garymallon.com -- COURSES -- DISCUSSION BOARD then login with: User: student Pw: ssw I get the following error: Microsoft JET Database Engine error '80040e57' The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data. /mrengmal/gm/forum/inc_func_common.asp, line 585 --- When I turn off Websense at the POP level, I get the same error so Websense isn't the issue. I have worked with Websene technical support to confirm this. If I go directly through one of our 2 top level Squid servers I am able to access the forums fine. If I try it from home, I am able to access the forums fine. It appears to be an issue with our tiered setup. Any ideas?
RE: [squid-users] WARNING: got unused STORE_META type 10
-Original Message- From: Amos Jeffries [mailto:squ...@treenet.co.nz] Sent: Friday, February 05, 2010 4:33 PM To: Ryan McCain Subject: Re: [squid-users] WARNING: got unused STORE_META type 10 Ryan McCain wrote: Squid-2.7 uses more advanced storage formats for objects. Squid-2.5 is unable to cope with those and is probably discarding things. Please, why did you down grade all the way to 2.5? Amos, We use a Websense plugin that only supports 2.5 and 2.6. Why is it trying to use this storage format since I removed 2.7 before installing 2.5? Is there something I can do to get rid of these errors? Thanks.. You need to erase the cache directory content and rebuild it with squid -z again. Amos -- Please be using Current Stable Squid 2.7.STABLE7 or 3.0.STABLE23 Current Beta Squid 3.1.0.16 === Thank you. That did the trick.
RE: [squid-users] WARNING: got unused STORE_META type 10
Squid-2.7 uses more advanced storage formats for objects. Squid-2.5 is unable to cope with those and is probably discarding things. Please, why did you down grade all the way to 2.5? Amos, We use a Websense plugin that only supports 2.5 and 2.6. Why is it trying to use this storage format since I removed 2.7 before installing 2.5? Is there something I can do to get rid of these errors? Thanks..
[squid-users] WARNING: got unused STORE_META type 10
After downgrading from Squid 2.7 to Squid 2.5, I get this error multiple times per second in /var/log/messages. What does it mean? Can I supress it? Feb 4 16:38:10 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:10 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:10 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:11 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:12 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:12 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:12 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:12 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:12 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:12 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:12 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:13 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:13 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10 Feb 4 16:38:13 dss-so92la03 squid[28227]: WARNING: got unused STORE_META type 10
[squid-users] Consider increasing the number of url_rewriter processes / All url_rewriter processes are busy
Hello, A squid box we recently upgraded to use Websense 7.1 has intermitent issues. See the log below.. SNIP Dec 28 10:03:00 dss-so92la05 squid[26940]: Starting Squid Cache version 2.7.STABLE6 for i686-pc-linux-gnu... Dec 28 10:03:00 dss-so92la05 squid[26940]: Process ID 26940 Dec 28 10:03:00 dss-so92la05 squid[26940]: With 4096 file descriptors available Dec 28 10:03:00 dss-so92la05 squid[26940]: Using epoll for the IO loop Dec 28 10:03:00 dss-so92la05 squid[26940]: DNS Socket created at 0.0.0.0, port 33381, FD 6 Dec 28 10:03:00 dss-so92la05 squid[26940]: Adding nameserver 10.120.11.85 from /etc/resolv.conf Dec 28 10:03:00 dss-so92la05 squid[26940]: Adding nameserver 10.120.11.107 from /etc/resolv.conf Dec 28 10:03:00 dss-so92la05 squid[26940]: Adding domain dss.la.gov from /etc/resolv.conf Dec 28 10:03:00 dss-so92la05 squid[26940]: helperOpenServers: Starting 30 'WsRedtor' processes Dec 28 10:03:00 dss-so92la05 squid[26940]: logfileOpen: opening log /var/log/squid/access.log Dec 28 10:03:01 dss-so92la05 squid[26940]: Unlinkd pipe opened on FD 41 Dec 28 10:03:01 dss-so92la05 squid[26940]: Swap maxSize 16384000 + 262144 KB, estimated 0 objects Dec 28 10:03:01 dss-so92la05 squid[26940]: Target number of buckets: 64023 Dec 28 10:03:01 dss-so92la05 squid[26940]: Using 65536 Store buckets Dec 28 10:03:01 dss-so92la05 squid[26940]: Max Mem size: 262144 KB Dec 28 10:03:01 dss-so92la05 squid[26940]: Max Swap size: 16384000 KB Dec 28 10:03:01 dss-so92la05 squid[26940]: Store logging disabled Dec 28 10:03:01 dss-so92la05 squid[26940]: Rebuilding storage in /apps/squid/cache1 (CLEAN) Dec 28 10:03:01 dss-so92la05 squid[26940]: Rebuilding storage in /apps/squid/cache2 (CLEAN) Dec 28 10:03:01 dss-so92la05 squid[26940]: Rebuilding storage in /apps/squid/cache3 (CLEAN) Dec 28 10:03:01 dss-so92la05 squid[26940]: Rebuilding storage in /apps/squid/cache4 (CLEAN) Dec 28 10:03:01 dss-so92la05 squid[26940]: Using Least Load store dir selection Dec 28 10:03:01 dss-so92la05 squid[26940]: Current Directory is / Dec 28 10:03:01 dss-so92la05 squid[26940]: Loaded Icons. Dec 28 10:03:01 dss-so92la05 squid[26940]: Accepting proxy HTTP connections at 10.120.100.205, port 8080, FD 48. Dec 28 10:03:01 dss-so92la05 squid[26940]: Accepting ICP messages at 0.0.0.0, port 3130, FD 49. Dec 28 10:03:01 dss-so92la05 squid[26940]: WCCP Disabled. Dec 28 10:03:01 dss-so92la05 squid[26940]: Configuring 10.120.9.80 Parent 10.120.9.80/8080/3130 Dec 28 10:03:01 dss-so92la05 squid[26940]: Configuring 10.120.9.100 Parent 10.120.9.100/8080/3130 Dec 28 10:03:01 dss-so92la05 squid[26940]: Ready to serve requests. Dec 28 10:03:01 dss-so92la05 squid[26940]: Store rebuilding is 27.8% complete Dec 28 10:03:01 dss-so92la05 squid[26940]: Done reading /apps/squid/cache4 swaplog (13075 entries) Dec 28 10:03:01 dss-so92la05 squid[26940]: Done reading /apps/squid/cache1 swaplog (14731 entries) Dec 28 10:03:01 dss-so92la05 squid[26940]: Done reading /apps/squid/cache3 swaplog (14779 entries) Dec 28 10:03:01 dss-so92la05 squid[26940]: Done reading /apps/squid/cache2 swaplog (15337 entries) Dec 28 10:03:01 dss-so92la05 squid[26940]: Finished rebuilding storage from disk. Dec 28 10:03:01 dss-so92la05 squid[26940]: 57922 Entries scanned Dec 28 10:03:01 dss-so92la05 squid[26940]: 0 Invalid entries. Dec 28 10:03:01 dss-so92la05 squid[26940]: 0 With invalid flags. Dec 28 10:03:01 dss-so92la05 squid[26940]: 57922 Objects loaded. Dec 28 10:03:01 dss-so92la05 squid[26940]: 0 Objects expired. Dec 28 10:03:01 dss-so92la05 squid[26940]: 0 Objects cancelled. Dec 28 10:03:01 dss-so92la05 squid[26940]: 0 Duplicate URLs purged. Dec 28 10:03:01 dss-so92la05 squid[26940]: 0 Swapfile clashes avoided. Dec 28 10:03:01 dss-so92la05 squid[26940]: Took 0.5 seconds (121961.6 objects/sec). Dec 28 10:03:01 dss-so92la05 squid[26940]: Beginning Validation Procedure Dec 28 10:03:01 dss-so92la05 squid[26940]: Completed Validation Procedure Dec 28 10:03:01 dss-so92la05 squid[26940]: Validated 57922 Entries Dec 28 10:03:01 dss-so92la05 squid[26940]: store_swap_size = 929412k Dec 28 10:03:01 dss-so92la05 squid[26940]: WARNING: All url_rewriter processes are busy. Dec 28 10:03:01 dss-so92la05 squid[26940]: WARNING: up to 30 pending requests queued Dec 28 10:03:01 dss-so92la05 squid[26940]: storeLateRelease: released 0 objects Dec 28 10:03:31 dss-so92la05 squid[26940]: WARNING: All url_rewriter processes are busy. Dec 28 10:03:31 dss-so92la05 squid[26940]: WARNING: up to 154 pending requests queued Dec 28 10:03:31 dss-so92la05 squid[26940]: storeDirWriteCleanLogs: Starting... Dec 28 10:03:31 dss-so92la05 squid[26940]: WARNING: Closing open FD 48 Dec 28 10:03:31 dss-so92la05 squid[26940]: commSetEvents: epoll_ctl(EPOLL_CTL_DEL): failed on fd=48: (1) Operation not permitted Dec 28 10:03:31 dss-so92la05 squid[26940]: WARNING: Closing open FD 49 Dec 28 10:03:31 dss-so92la05 squid[26940]: commSetEvents:
[squid-users] client: ERROR: Cannot connect to localhost:3128: Connection refused
I'm trying to issue this command: squidclient -m PURGE http://www.yahoo.com and get the following error: client: ERROR: Cannot connect to localhost:3128: Connection refused I'm using squid-2.7.STABLE6-1 on SLES 10. I'm not even sure what is supposed to be running on port 3128. I've tried running this w/ the software firewall turned off and always get the error. Any ideas?
Re: [squid-users] client: ERROR: Cannot connect to localhost:3128:Connection refused
A. Thanks!
On Tue, Jul 7, 2009 at 4:07 PM, in message 4a53b8f8.4050...@gci.net,
Chris
Robertson crobert...@gci.net wrote:
Ryan McCain wrote:
I'm trying to issue this command:
squidclient -m PURGE http://www.yahoo.com
and get the following error:
client: ERROR: Cannot connect to localhost:3128: Connection refused
I'm using squid-2.7.STABLE6-1 on SLES 10. I'm not even sure what is
supposed
to be running on port 3128. I've tried running this w/ the software firewall
turned off and always get the error.
Any ideas?
Use...
squidclient -p ${Port-Squid-Listens-On} -m PURGE http://www.yahoo.com/
...if you don't have Squid listening on (the default) port 3128.
Chris
[squid-users] What 3rd party tools do you guys use?
For trend analysis, alerting, log parsing, configuration, etc. etc.? The only 3rd party tool we currently use is SARG. Ryan
Re: [squid-users] Squid and NTLM Authentication
On Wed, Mar 4, 2009 at 5:22 PM, in message eb2a55e07ade8fe1700dc079b76b687c.squir...@webmail.treenet.co.nz, Amos Jeffries squ...@treenet.co.nz wrote: Ah SLES. They have actually managed to be slower than RedHat on updating their software. Okay, from what I can tell you're pretty much screwed. Unless you are a guru with package building and installing on SLES, or willing to change OS. The faster solution may be to check and change the authentication type required by IIS. For the record, yes the latest 2.6 and 2.7 support pass-thru for NTLM and kerberos negotiation, one of which I believe is causing your problem. Amos I was able to install Squid 3.x and the result is still the same.. Any ideas? Which 3.x? 3.0 is based on 2.5 and does not support it either. Try the 2.7 for stable version, or 3.1 for beta release. Amos Will do .. Thanks for the heads up. Ryan
Re: [squid-users] Squid and NTLM Authentication
I was able to install Squid 3.x and the result is still the same.. Any ideas? Which 3.x? 3.0 is based on 2.5 and does not support it either. Try the 2.7 for stable version, or 3.1 for beta release. Amos Amos, 2.7 worked like a charm. Any idea what version will ship with SLES 11? Thanks..
Re: [squid-users] Squid and NTLM Authentication
Ah SLES. They have actually managed to be slower than RedHat on updating their software. Okay, from what I can tell you're pretty much screwed. Unless you are a guru with package building and installing on SLES, or willing to change OS. The faster solution may be to check and change the authentication type required by IIS. For the record, yes the latest 2.6 and 2.7 support pass-thru for NTLM and kerberos negotiation, one of which I believe is causing your problem. Amos I was able to install Squid 3.x and the result is still the same.. Any ideas?
Re: [squid-users] Squid and NTLM Authentication
On Mon, Mar 2, 2009 at 5:36 PM, in message dbbdfe40eac962f012c18cc3b7582856.squir...@webmail.treenet.co.nz, Amos Jeffries squ...@treenet.co.nz wrote: We are using squid-2.5.STABLE12-18.12 Please use a newer more capable Squid. There have been MANY improvements since 2.5 was made obsolete. Amos The only reason we are using that version is because it's the latest version supported w/ SLES 10. Does this version or a newer version support the scenario I described? Thanks..
[squid-users] Squid and NTLM Authentication
We are using squid-2.5.STABLE12-18.12 When trying to access this web page from home it prompts me for NTLM Authentication credentials: http://www.allianceenterprises.com/AWAREInfo --- When I do it from work (behind Squid), I get this error: You are not authorized to view this page You do not have permission to view this directory or page due to the access control list (ACL) that is configured for this resource on the Web server. Please try the following: * Contact the Web site administrator if you believe you should be able to view this directory or page. * Click the Refresh button to try again with different credentials. HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource. Internet Information Services (IIS) Technical Information (for support personnel) * Go to Microsoft Product Support Services and perform a title search for the words HTTP and 401. * Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled About Security, Access Control, and About Custom Error Messages. I'm thinking that Squid doesn't know how to handle NTLM authentication? Any ideas?
[squid-users] Having to login multiple times??
hello, we are just starting with squid. when a user opens a web browser it will ask them to login if they go to yahoo.com, or whatever. if they open a new browser session and go to another site, it will ask them again for their user credentials. is it possible to have the login credentials to the squid server somehow cached so the users won't have to login everytime the open a new instance of IE or firefox. we are running squid v2.5x on SLES 9. any help or pointers to documentation would be helpful.
