[squid-users] Corrupted files with delay pools active
Hi ! I'm having problems while downloading files. The files "sometimes" ends corrupted , and other times don't. When i download a file about +-5Mb, it's ok. When the size is +-17 Mb , it's not. If i disable "delay pools" , the file downloads ok!. I'm running SUSE 10.1 , Squid 2.5 STABLE 12. My delay pool parameters are : delay_class 1 3 delay_parameters 1 65536/131072 -1/-1 10240/30720 Thanks. Augusto
[squid-users] Delay pools problem
Hi everyone. I'm having delay pools issues. I've had declared 3 delay pools , and i'had made 3 different groups in 3 text files, each file contains the name of the user corresponding to the navegation speed I'had declared INFO as the highest privilege group, GRAL as standard navegation group , and REST as restricted navegation group. My problem , is that apparently my rule is not work, as all the users ara allowed in the delay_pool 1, and nobody are allowed in the other 2 delay_pools. I guess the problem is in the delay_access section...? My squid.conf section : delay_pools 3 delay_class 1 3 delay_class 2 3 delay_class 3 3 delay_access 1 allow info !gral !rest delay_access 1 deny gral rest delay_access 2 allow gral !rest delay_access 2 deny rest delay_access 3 allow rest delay_access 3 deny all delay_parameters 1 -1/-1 -1/1024000 15000/512000 delay_parameters 2 -1/-1 3/1024000 7000/512000 delay_parameters 3 -1/-1 3/1024000 3000/512000 acl info proxy_auth_regex -i "/etc/squid/info.txt" REQUIRED acl gral proxy_auth_regex -i "/etc/squid/gral.txt" REQUIRED acl rest proxy_auth_regex -i "/etc/squid/rest.txt" REQUIRED Thanks in advice !
Re: [squid-users] Delay pools problem - SOLVED
Thanks Amos and Chris, problem solved. I've removed the REQUIRED statement, and simplified que expressions (INFO !GRAL !REST)... Thank you very much! 2009/9/10 Amos Jeffries : > Chris Robertson wrote: >> >> Augusto Casagrande wrote: >>> >>> Hi everyone. >>> I'm having delay pools issues. >>> I've had declared 3 delay pools , and i'had made 3 different groups in >>> 3 text files, each file contains the name of the user corresponding to >>> the navegation speed >>> I'had declared INFO as the highest privilege group, GRAL as standard >>> navegation group , and REST as restricted navegation group. >>> My problem , is that apparently my rule is not work, as all the users >>> ara allowed in the delay_pool 1, and nobody are allowed in the other 2 >>> delay_pools. >>> I guess the problem is in the delay_access section...? >>> >>> My squid.conf section : >>> >>> delay_pools 3 >>> >>> delay_class 1 3 >>> delay_class 2 3 >>> delay_class 3 3 >>> >>> delay_access 1 allow info !gral !rest >>> >> >> While explicit as it is, this line would be better expressed (and simpler >> for Squid to parse) as... >> >> delay_access 1 allow info >> >> ...assuming "info", "gral" and "rest" don't have any overlap. If there is >> overlap, the original is fine. >> >>> delay_access 1 deny gral rest >>> >> >> This line says deny access to delay pool 1 for the intersection of gral >> AND rest. >> Since there are no further delay_access rules for pool 1, there is an >> implicit "delay_access 1 allow all" after. What you should have is... >> >> delay_access 1 deny all >> >>> delay_access 2 allow gral !rest >>> >> >> delay_access 2 allow gral >> >>> delay_access 2 deny rest >>> >> >> delay_access 2 deny all >> >>> delay_access 3 allow rest >>> delay_access 3 deny all >>> >>> delay_parameters 1 -1/-1 -1/1024000 15000/512000 >>> delay_parameters 2 -1/-1 3/1024000 7000/512000 >>> delay_parameters 3 -1/-1 3/1024000 3000/512000 >>> >>> acl info proxy_auth_regex -i "/etc/squid/info.txt" REQUIRED >>> acl gral proxy_auth_regex -i "/etc/squid/gral.txt" REQUIRED >>> acl rest proxy_auth_regex -i "/etc/squid/rest.txt" REQUIRED >>> > > That should be: > > acl ... proxy_auth REQUIRED > > or > acl ... proxy_auth -i list-of-usernames > > or > acl ... proxy_auth_regex -i list-of-usernames > > Not a combo of the three on one line. > > Using "REQUIRED" accepts _any_ valid usernames. It clashes with setting a > list of specific usernames which are allowed. > >> >> I have to imagine that the delay_parameters and ACLs are defined above the >> delay_access lines that reference them, as Squid reads the config file in a >> linear fashion. >> >>> Thanks in advice ! >>> >> >> Chris >> > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE6 or 3.0.STABLE18 > Current Beta Squid 3.1.0.13 >
[squid-users] Squid stops/starts
Hi, a new issue. I have noticed that Squid stops and starts automatically. My /var/log/messages shows : . . . . squid[20957]: assertion failed: ACLProxyAuth.cc:227: "authenticateUserAuthenticated(checklist->auth_user_request)" squid[13183]: Squid Parent: child process 20957 exited due to signal 6 squid[13183]: Squid Parent: child process 15196 started squid[15196]: Starting Squid Cache version 3.0.STABLE13 for i686-suse-linux... . . . My Squid version is Squid Cache: Version 3.0.STABLE13 Any ideas ? Thanks! Augusto.-
Re: [squid-users] Squid stops/starts - UPDATED
I've found another line in my /var/log/messages squid[15196]: CACHEMGR: @172.20.22.13 requesting 'active_requests' squid[15196]: assertion failed: ACLProxyAuth.cc:227: "authenticateUserAuthenticated(checklist->auth_user_request)" . . . I'm using an aplicattion ( sqstat ) to look in to the access.log file , it shows in real time what sites are being visited. 172.20.22.13 is the squid's ip. That line appears every time i update my sqstat status. Thanks! 2009/9/10 Henrik Nordstrom : > tor 2009-09-10 klockan 11:08 -0300 skrev Augusto Casagrande: >> Hi, a new issue. >> I have noticed that Squid stops and starts automatically. >> My /var/log/messages shows : >> . >> . >> . >> . >> squid[20957]: assertion failed: ACLProxyAuth.cc:227: >> "authenticateUserAuthenticated(checklist->auth_user_request)" > > Internal error in Squid. > >> squid[15196]: Starting Squid Cache version 3.0.STABLE13 for >> i686-suse-linux... > > 3.0.STABLE13 is pretty old with countless number of fixes. May be worth > trying to upgrade. Current 3.0 release is 3.0.STABLE19. > > If the problem persists please file a bug report. Remember to include a > stack backtrace (see Squid FAQ on how to report bug if not sure what > that is about). > > Regards > Henrik > >
Re: [squid-users] My sarg broke
Hi, aparently its an error of Webmin. I've a similar problem Sarg 2.2.5 on Squid 3.0.STABLE19 and Webmin 1.490. I've reported the error in a Webmin's forum, and it's maybe a Webmin error. It will be fixed in the next (1.500) release. Augusto 2009/10/6 ant2ne : > > I like Webmin and Sarg. Something recently has broken it. I don't care if I > loose all old logs, but I need to generate new ones. > > Here is the error I get > Now generating Sarg report from Squid log file /var/log/squid/access.log and > all rotated versions .. > sarg -l /var/log/squid/access.log.1 -d 05/10/2009-06/10/2009 > SARG: No records found > SARG: End > sarg -l /var/log/squid/access.log.2.gz -d 05/10/2009-06/10/2009 > SARG: Decompressing log file: /var/log/squid/access.log.2.gz > > /tmp/sarg-file.in (zcat) > SARG: No records found > SARG: End > .. Sarg finished, but no report was generated. See the output above for > details. > > Here is some Back Story, along with my current squid.conf > http://www.nabble.com/not-caching-enough-td25530445.html#a25553196 > -- > View this message in context: > http://www.nabble.com/My-sarg-broke-tp25775972p25775972.html > Sent from the Squid - Users mailing list archive at Nabble.com. > >
[squid-users] Postmap question
Hi, I´, planning to use body_checks option to block emails containing pages of suspicius viruses , worms The list have this type-content : /http:\/\/(.+@)?01\.yan11\.com.*/ DISCARD MBL-121649 /http:\/\/(.+@)?02fgu145501\.cn\/gdgte.*/ DISCARD MBL-121650 /http:\/\/(.+@)?031\.9d3f\.cn\/hb.*/ DISCARD MBL-121060 /http:\/\/(.+@)?0519qq\.cn\/zzx.*/ DISCARD MBL-109634 /http:\/\/(.+@)?1\.77177\.cn\:88\/22.*/ DISCARD MBL-122252 /http:\/\/(.+@)?109438129432\.cn.*/ DISCARD MBL-115033 . . . . . My question is , should i use postmap to make a binary file of this list ? Or it's not compatible with body_checks ??? Thaks you so much! Regards!
[squid-users] Squid crashes, restart
Hi, today i noticed that squid restart from normal operations. Here is the log --- squid[4374]: assertion failed: ACLProxyAuth.cc:227: "authenticateUserAuthenticated(checklist->auth_user_request)" --- I'm running SUSE 10.1 and Squid Cache Version 3.0.STABLE19 Any suggestion? Thanks!
[squid-users] Windows Live , with proxy auth
Hi, I'm runnig Squid 3.0.STABLE19 , using plain proxy auth (auth_param basic program /usr/sbin/pam_auth). Some time ago , I had troubles when trying to login to Windows Live Messenger. It began to causing problems when i enable the proxy auth. I could not make it work. My solution was installing Pidgin http://pidgin.im/ . In Microsoft's page http://support.microsoft.com/?scid=kb%3Ben-us%3B927847&x=1&y=8 , quote : Users behind some authenticating proxy servers may experience sign-in issues. They might have to configure the proxy servers to force authentication for the following User Agent string: MSN Explorer/9.0 (MSN 8.0; TmstmpExt). To do this, users should see the documentation for their proxy server or contact their network administrator. Is this the fix for this issue? How can i implement it? Thanks!
Re: [squid-users] Can someone check a site?
Loaded ok. Squid Cache: Version 3.0.STABLE19 2010/3/26 Marcello Romani : > Ivan . ha scritto: >> >> Hi, >> >> Can someone running Squid v2.6 STABLE21 check this site for me? >> http://www.usp.ac.fj >> >> Nothing in the access.log to give me a hint as to where the issue is. >> >> I can access it direct, but through Squid it just hangs there after >> the inital TCP handshake? >> >> [r...@proxy squid]# tcpdump -vvv host 144.120.8.2 >> tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size >> 65535 bytes >> 21:35:24.227005 IP (tos 0x0, ttl 64, id 7227, offset 0, flags [DF], >> proto: TCP (6), length: 60) xxx.xxx.xxx.xxx.33151 > >> belo.usp.ac.fj.http: S, cksum 0xb78a (correct), >> 2265843403:2265843403(0) win 5840 > 0,nop,wscale 7> >> 21:35:24.488001 IP (tos 0x0, ttl 53, id 0, offset 0, flags [DF], >> proto: TCP (6), length: 60) belo.usp.ac.fj.http > >> xxx.xxx.xxx.xxx.33151: S, cksum 0x1a89 (correct), >> 2369822436:2369822436(0) ack 2265843404 win 5792 > 1460,sackOK,timestamp 159278980 992156400,nop,wscale 0> >> 21:35:24.488013 IP (tos 0x0, ttl 64, id 7228, offset 0, flags [DF], >> proto: TCP (6), length: 52) xxx.xxx.xxx.xxx.33151 > >> belo.usp.ac.fj.http: ., cksum 0x5ebb (correct), 1:1(0) ack 1 win 46 >> >> 21:35:24.488077 IP (tos 0x0, ttl 64, id 7229, offset 0, flags [DF], >> proto: TCP (6), length: 482) xxx.xxx.xxx.xxx.33151 > >> belo.usp.ac.fj.http: P, cksum 0x15be (incorrect (-> 0x870c), >> 1:431(430) ack 1 win 46 >> 21:35:24.729001 IP (tos 0x0, ttl 53, id 63867, offset 0, flags [DF], >> proto: TCP (6), length: 52) belo.usp.ac.fj.http > >> xxx.xxx.xxx.xxx.33151: ., cksum 0x4401 (correct), 1:1(0) ack 431 win >> 6432 >> >> thanks >> Ivan > > > The home page loads just fine. > > > serverdebian:~# squid -v > Squid Cache: Version 2.7.STABLE3 > configure options: '--prefix=/usr' '--exec_prefix=/usr' > '--bindir=/usr/sbin' '--sbindir=/usr/sbin' '--libexecdir=/usr/lib/squid' > '--sysconfdir=/etc/squid' '--localstatedir=/var/spool/squid' > '--datadir=/usr/share/squid' '--enable-async-io' '--with-pthreads' > '--enable-storeio=ufs,aufs,coss,diskd,null' '--enable-linux-netfilter' > '--enable-arp-acl' '--enable-epoll' '--enable-removal-policies=lru,heap' > '--enable-snmp' '--enable-delay-pools' '--enable-htcp' > '--enable-cache-digests' '--enable-underscores' '--enable-referer-log' > '--enable-useragent-log' '--enable-auth=basic,digest,ntlm,negotiate' > '--enable-negotiate-auth-helpers=squid_kerb_auth' '--enable-carp' > '--enable-follow-x-forwarded-for' '--with-large-files' '--with-maxfd=65536' > 'amd64-debian-linux' 'build_alias=amd64-debian-linux' > 'host_alias=amd64-debian-linux' 'target_alias=amd64-debian-linux' > 'CFLAGS=-Wall -g -O2' 'LDFLAGS=' 'CPPFLAGS=' > > > -- > Marcello Romani >
