[squid-users] Squid 3.2.0.13 beta is available
The Squid HTTP Proxy team is very pleased to announce the availability of the Squid-3.2.0.13 beta release! This release adds SMP support to the cache storage when running with multiple workers. It also brings bug fixes resolving several more regressions found in the prior releases. There are some few regressions still remaining to be found. SMP storage and caching Expect some new storage bugs to arrive and some to die mysteriously. * installations with no workers are expected to only see small benefits (at most) via the existing storage code streamlining and bug fixes. There are probably more new bugs than improvements if you are not into SMP caching, especially in corner cases. Non-SMP setups were not the focus of this work. * installations with workers will automatically get the SMP shared memory caching. This seems to be the newest most experimental of the whole update. So fair warning: expect new bugs in this area. If you use SMP caching and do not want shared memory caching, see memory_cache_shared in squid.conf. * installations choosing to explicitly configure "rock" cache_dir type get shared disk database-style caching. This is available for both SMP and non-SMP builds. This is the older part with prior production use as a 3.1 branch. The underlying database design and Store API code is mostly the same, but v3.1 code used blocking I/O within the same Squid process. The now-official code is meant for use with disker kid processes, which means a lot of new internal changes and complications. We are currently working through the bugs resulting from that. There are also quite a few feature holes. For example, Rock cache_dir hot reconfiguration is not yet supported. Statistics is lacking. Squid uses a lot more memory for shared I/O pages than it needs. Project details are http://wiki.squid-cache.org/Features/RockStore. * If you use multiple Rock store, use round-robin cache_dir selector. * If you use Rock store and your disks are close to 100% utilized, you probably need to use max-swap-rate and swap-timeout options. Remember that diskers cannot slow down workers so they can be overwhelmed with swap requests. Also, hiding in the background of all that some unrelated bugs have also been found and fixed since earlier releases: * IPF interception is now had a fix and tests out well. * ext_session_acl helper upgraded to version 1.1 * never_direct and always_direct have been fixed to resolve some regressions since 3.2.0.11. * A regression in --with-swapdir option stops it being ignored by some parts of Squid. * dynamic certificate generation has several database fixes. Resolving several unwanted error or hung connection events. * adaptation_service directive has had some updates to the parameter defaults an configuration style. Use "squid -k parse" to see if your configuration is affected. * dynamic helper assertions on reconfigure are resolved. * Digest authentication bugs with backslash (\) in URLs are resolved. As usual this release contains all the fixes passed on to 3.1 series alongside its own changes. See the ChangeLog for the list of other minor changes in this release. Users who have been staying with 2.7 releases due to lack of COSS support in 3.x series are encouraged to assist testing of the rock storage which is designed as an advancement from COSS. All users interested in 3.2 features are encouraged to assist testing this release. Please refer to the release notes at http://www.squid-cache.org/Versions/v3/3.2/RELEASENOTES.html when you are ready to make the switch to Squid-3.2 Upgrade tip: "squid -k parse" is starting to display even more useful hints about squid.conf changes. This new release can be downloaded from our HTTP or FTP servers http://www.squid-cache.org/Versions/v3/3.2/ ftp://ftp.squid-cache.org/pub/squid/ ftp://ftp.squid-cache.org/pub/archive/3.2/ or the mirrors. For a list of mirror sites see http://www.squid-cache.org/Download/http-mirrors.html http://www.squid-cache.org/Download/mirrors.html If you encounter any issues with this release please file a bug report. http://bugs.squid-cache.org/ Amos Jeffries
Re: [squid-users] Again: Compile problem with squid-3.1.15
On 14/10/11 21:07, Erich Titl wrote: Hi Folks at 14.10.2011 09:37, Erich Titl wrote: on 13.10.2011 16:46, John Doe wrote: From: Erich Titl I am still trying to compile 3.1.15. I still get the following /usr/lib/libcrypto.a(c_zlib.o): In function `bio_zlib_free': (.text+0x4f): undefined reference to `inflateEnd' I used your flags and configure on my 32-bits CentOS and 3.1.16 compiled fine... Maybe make sure you have all the "devel" packages. Did you check the configure output to see if it detected everything (zlib, ssl...)? I would guess so, anyway compiling with 3.2.0.12 goes without a hitch. Will try with 3.1.16 to see if anything changes. No changes as expected, 3.1.16 fails compilation just the same. Is it possible that 3.1 does not play well with openssl 1.0.0x Very possible. They seems to have had no fear of changing the header files definitions across the 1.0.0* series. I'm particularly looking now for details like that 'x' in correlation to particular build errors. So we can use it to target our workarounds as we encounter problems. Since you seem to have a working and non-working build. Can you provide the g++ command line for both 3.2 and 3.1 series build of the broken file? You provided a 3.1 trace alone earlier. I'm looking for what is detected differently or ordered differently in the link sequence. A diff of the include/autoconf.h file which is generated by ./configure for each of those builds would also be helpful. And please lets get a bugzilla entry to track all this now. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.15 Beta testers wanted for 3.2.0.12
[squid-users] Squid latency?
Two quick questions: I have big latency on the Squid box. It takes about 5 seconds from the time I enter URL address until the page loads. When the page loads it loads very quickly. DNS queries to WAN are <2ms, average ISP tracert and ping latencies are around 20ms. Tracert and ping from LAN to the proxy are <1ms. Is there something in the Squid (an option, log, or util) that would help me figure this out? This is less important but I see lots these messages in the log. Is this something I should be concerned about? 1318650368.497 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650374.794 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650381.041 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650387.434 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650393.880 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650400.340 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650406.872 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650418.189 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650424.487 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650430.685 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650436.982 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html 1318650443.326 0 IP-address-removed NONE/400 3371 +?AO tqyU - NONE/- text/html Squid Cache: Version 3.1.6 Debian 6.1 Linux 2.6.32-5-686-bigmem 250GB SATA, 8GB memory, 3GHz dual-core
[squid-users] Squid 3.1.16 is available
The Squid HTTP Proxy team is very pleased to announce the availability of the Squid-3.1.16 release! This release brings bug fixes for earlier releases and several enhancements to improve bug finding in 3.1. Bug 3326: miss_access incorrect default. If you use miss_access in your configuration it is important that you upgrade to this release or apply the patch provided in 3.1.16 changesets archive. http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10373.patch A review of the miss_access controls in your configuration maybe required after the update. Documentation of this directive has also been clarified in this release to express what it actually does during the request handling process in Squid. Several of the 'bugs' were related to misunderstandings about miss_access correct usage and behaviour. Bug 3368: Unhandled exceptions are not logged (workaround) In the last few releases there have been a growing number of reports about exception crashes. This release seeks to report those a lot better for debugging. If you are experiencing any such problems, please test with this release to get better bug report traces and a faster problem resolution. Updated OpenSSL 1.0.0 version checks. This resolves several compile issues we were hearing about with openssl v1.0.0a to 1.0.0d. There are still some issues remaining. If you are experiencing errors building Squid against openssl 1.0.0 please use this release as now the minimum required version for bug reports and updates. Bug #3241: squid_kerb_auth cross compilation fix The resolves the last known issue with cross-compilation in 3.1 kerberos authentication helpers. See the ChangeLog for the list of other minor changes in this release. All users of Squid-3 are encouraged to upgrade as soon as possible. Please refer to the release notes at http://www.squid-cache.org/Versions/v3/3.1/RELEASENOTES.html when you are ready to make the switch to Squid-3.1 This new release can be downloaded from our HTTP or FTP servers http://www.squid-cache.org/Versions/v3/3.1/ ftp://ftp.squid-cache.org/pub/squid/ ftp://ftp.squid-cache.org/pub/archive/3.1/ or the mirrors. For a list of mirror sites see http://www.squid-cache.org/Download/http-mirrors.html http://www.squid-cache.org/Download/mirrors.html If you encounter any issues with this release please file a bug report. http://bugs.squid-cache.org/ Amos Jeffries
Re: [squid-users] facebook upload DOS's squid?
Hallo, hunter, Du meintest am 14.10.11: > when uploading a 540m video to facebook, it seems like squid ends up > caching(maybe not the right word) the whole thing. Does "squid" control uploading? Viele Gruesse! Helmut
[squid-users] facebook upload DOS's squid?
when uploading a 540m video to facebook, it seems like squid ends up caching(maybe not the right word) the whole thing. my 512m ram is full (478/488m) and its swapping heavily(dont know how to test except hd light is almost solid and system is not responding well - load avg 3.5) cpu is only 13% for squid and mem is 90%. can anyone help shed light on this behavior? i cant do anything after it gets to 90% uploaded and i stopped the transfer and restarted squid to keep from waiting until i die to regain responsiveness.
Re: [squid-users] Banners in Webpages
2011/10/14 senthil kumar : > Hello Team, > > In our office we have about 100 users using transparent proxy. > > Can anyone recommend the best strategy to add banners, advertisements > in the web pages users browse? > > I think it can be done by using ICAP. Is there any ICAP server which > is effective in doing it? > > Thanks, > Senthil > This question is very coommon, i've already answered some days ago. I paste answer: if yo have c/c++ skils you may program a c-icap module. There is an easier way, but this isno squid's. I remember apache has an foot_page module that does exactly what you want, you can use it in combination with squid to add your code. LD http://www.twitter.com/ldlq
[squid-users] Re: Banners in Webpages
qlproxy is good in ERASING banners :) best regards sich On 10/14/2011 11:31 AM, senthil kumar wrote: Hello Team, In our office we have about 100 users using transparent proxy. Can anyone recommend the best strategy to add banners, advertisements in the web pages users browse? I think it can be done by using ICAP. Is there any ICAP server which is effective in doing it? Thanks, Senthil
Re: [squid-users] Banners in Webpages
On Fri, 14 Oct 2011, senthil kumar wrote: Hello Team, In our office we have about 100 users using transparent proxy. Can anyone recommend the best strategy to add banners, advertisements in the web pages users browse? I swear I simply cannot understand the desire to inject ads into content, and I hope that Squid never makes doing that easy. You really want to spam your office? -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- Gun Control laws cannot reduce violent crime, because gun control laws assume a violent criminal will obey the law. --- 309 days since the first successful private orbital launch (SpaceX)
[squid-users] Banners in Webpages
Hello Team, In our office we have about 100 users using transparent proxy. Can anyone recommend the best strategy to add banners, advertisements in the web pages users browse? I think it can be done by using ICAP. Is there any ICAP server which is effective in doing it? Thanks, Senthil
Re: [squid-users] Again: Compile problem with squid-3.1.15
Hi Folks at 14.10.2011 09:37, Erich Titl wrote: > on 13.10.2011 16:46, John Doe wrote: >> From: Erich Titl >> >>> I am still trying to compile 3.1.15. I still get the following >>> /usr/lib/libcrypto.a(c_zlib.o): In function `bio_zlib_free': >>> (.text+0x4f): undefined reference to `inflateEnd' >> >> I used your flags and configure on my 32-bits CentOS and 3.1.16 compiled >> fine... >> Maybe make sure you have all the "devel" packages. >> Did you check the configure output to see if it detected everything (zlib, >> ssl...)? > > I would guess so, anyway compiling with 3.2.0.12 goes without a hitch. > Will try with 3.1.16 to see if anything changes. No changes as expected, 3.1.16 fails compilation just the same. Is it possible that 3.1 does not play well with openssl 1.0.0x cheers Erich smime.p7s Description: S/MIME Kryptografische Unterschrift
[squid-users] Re: squid-2.7Stable8 hangup
Hi I am facing the same problem but with different messages, any help on this matter will be highly appreciated. As I am just a beginner at using squid and linux and I am not even sure where to dig for the solution. Is it a squid problem or a kernel problem or some driver problem. Any help will be highly appreciated. I am using the same setup as described above by Mr.Felipe (Bridge+squid+tproxy on an ISP network). I am using squid 3.2.0.8 with kernel 2.6.38-8 on ubuntu. /kernel: [271296.882782] [ cut here ] kernel: [271296.882794] WARNING: at /build/buildd/linux-2.6.38/net/ipv4/tcp_input.c:2964 tcp_fastretrans_alert+0x391/0xba0() kernel: [271296.882800] Hardware name: ProLiant ML110 G6 kernel: [271296.882803] Modules linked in: ebt_redirect ebt_ip ebtable_broute ebtables xt_TPROXY nf_tproxy_core xt_tcpudp xt_socket nf_defrag_ipv4 ip6_tables nf_defrag_ipv6 xt_mark iptable_mangle ip_tables x_tables vesafb bridge stp bpctl_mod lp parport usbhid hid tcp_westwood ahci libahci igb tg3 dca kernel: [271296.882836] Pid: 965, comm: squid Tainted: GW 2.6.38-8-server #42-Ubuntu kernel: [271296.882840] Call Trace: kernel: [271296.882842][] ? warn_slowpath_common+0x7f/0xc0 kernel: [271296.882855] [] ? warn_slowpath_null+0x1a/0x20 kernel: [271296.882861] [] ? tcp_fastretrans_alert+0x391/0xba0 kernel: [271296.882866] [] ? tcp_ack+0x334/0x660 kernel: [271296.882871] [] ? tcp_rcv_established+0x342/0x720 kernel: [271296.882878] [] ? tcp_v4_do_rcv+0xb1/0x1c0 kernel: [271296.882884] [] ? tcp_v4_rcv+0x646/0x900 kernel: [271296.882891] [] ? ip_local_deliver_finish+0x0/0x280 kernel: [271296.882897] [] ? ip_local_deliver_finish+0xdd/0x280 kernel: [271296.882903] [] ? ip_local_deliver+0x88/0x90 kernel: [271296.882908] [] ? ip_rcv_finish+0x145/0x3c0 kernel: [271296.882913] [] ? ip_rcv+0x23c/0x300 kernel: [271296.882919] [] ? spin_unlock+0xe/0x20 kernel: [271296.882926] [] ? __netif_receive_skb+0x3e3/0x580 kernel: [271296.882932] [] ? netif_receive_skb+0x58/0x80 kernel: [271296.882938] [] ? napi_skb_finish+0x50/0x70 kernel: [271296.882944] [] ? napi_gro_receive+0xb5/0xc0 kernel: [271296.882954] [] ? igb_clean_rx_irq_adv+0x524/0x660 [igb] kernel: [271296.882961] [] ? handle_irq+0x22/0x40 kernel: [271296.882969] [] ? igb_poll+0x70/0x150 [igb] kernel: [271296.882975] [] ? net_rx_action+0x128/0x270 kernel: [271296.882981] [] ? __do_softirq+0xa8/0x1c0 kernel: [271296.882986] [] ? call_softirq+0x1c/0x30 kernel: [271296.882991] [] ? do_softirq+0x65/0xa0 kernel: [271296.882995] [] ? irq_exit+0x85/0x90 kernel: [271296.883001] [] ? do_IRQ+0x66/0xe0 kernel: [271296.883007] [] ? ret_from_intr+0x0/0x15 kernel: [271296.883010][] ? intel_idle+0xca/0x120 kernel: [271296.883020] [] ? intel_idle+0xa9/0x120 kernel: [271296.883027] [] ? cpuidle_idle_call+0xaa/0x1b0 kernel: [271296.883034] [] ? cpu_idle+0xa6/0xf0 kernel: [271296.883040] [] ? rest_init+0x75/0x80 kernel: [271296.883046] [] ? start_kernel+0x3f5/0x400 kernel: [271296.883051] [] ? x86_64_start_reservations+0x132/0x136 kernel: [271296.883056] [] ? zap_identity_mappings+0x3e/0x41 kernel: [271296.883061] [] ? x86_64_start_kernel+0xcc/0xdb kernel: [271296.883065] ---[ end trace 44593438a59a953b ]--- / -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/squid-2-7Stable8-hangup-tp2282741p3904068.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Again: Compile problem with squid-3.1.15
on 13.10.2011 16:46, John Doe wrote: > From: Erich Titl > >> I am still trying to compile 3.1.15. I still get the following >> /usr/lib/libcrypto.a(c_zlib.o): In function `bio_zlib_free': >> (.text+0x4f): undefined reference to `inflateEnd' > > I used your flags and configure on my 32-bits CentOS and 3.1.16 compiled > fine... > Maybe make sure you have all the "devel" packages. > Did you check the configure output to see if it detected everything (zlib, > ssl...)? I would guess so, anyway compiling with 3.2.0.12 goes without a hitch. Will try with 3.1.16 to see if anything changes. Thanks Erich smime.p7s Description: S/MIME Kryptografische Unterschrift
