Re: [squid-users] squid 2.7 TPROXY not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 6:55 p.m., saleh madi wrote: Hello, I have compiled squid 2.7stable9 with TPROXY patch, but the TPROXY seem not working. Er, yes. The TPROXY patch is not a Squid patch, it is a Linux kernel patch adding TPROXY/cttproxy support to the extremely old Linux kernel v2.2 and v2.4. Squid-2.7 does not need any patching to work with kernels that have been appropriately patched, but does not work with any newer kernels. Please note that all the software you will need to play with to get Squid-2.7 to do TPROXY was obsoleted 5-10 years ago, including Squid-2.7. Finding people who even remember it is getting hard. You would do better to upgrade to TPROXYv4, which should be available in all modern Linux OS and is supported by current Squid-3 releases. http://wiki.squid-cache.org/Features/Tproxy4#Minimum_Requirements_.28IPv6_and_IPv4.29 If you really want to stick with the old version, good luck. The concepts outlined in the wiki page and Troubleshooting remain unchanged. Just the specific configuration details are very different. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURfspAAoJELJo5wb/XPRj7aUIALPnNV3iI3vSKbGok9Kmtixj 2+KsKFVr+aebnZboMDOuWEBSmvXSc+jLMYtH8qacJXuJdRoN9ee8mKP6bZVDX7ZW IxcQrceQ3uX6JmINYU4ZKUoZYZwgotUBTj84d+CVEzvwbSNyauqCNpnbRBHdDLSp CZbDAYNF+eqym+I9FmARL2KrEY/cOU1c4sdSdl8llDq6qWwFp9i0CGNjVpU1yC2X scrdYQ2mkdgAS+KqpGE88die6M2q0sOQr/Y9T3y9v27vAI+tk63UGHLYXB+V0E/F A/EjhCGD8djcPGqDm73mqZL/P6JaJvA0o4j01nQLKO3If0H4G3ACU2EDKTuWe9c= =vw+9 -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
[squid-users] Question about compiling and loading ecap-adapter module on windows
Hi. I‘m coming again. Now, I have compiled squid-3.3.3 with --enable-ecap option successfully on cygwin and run it successfully on windows. But, there are another question about compiling ecap-adapter module？ I'm not sure that I should ask this question here, maybe I should ask eCAP developer. but I think that I should try it firstly. OK! Question 1: Does it need compile ecap-adapter module as .dll file if I want use ecap-adapter module on windows. Question 2: If it need, How to do it and do I shoud ask eCAP developer? Now, when I compile ecap-adapter module(ecap_adapter_sample-0.2.1.tar.gz) directly on cygwin. I just get .a .la file. Here is some output message when I make it. --output message--- Making all in src make[1]: Entering directory '/usr/src/ecap_adapter_sample-0.2.1/src' make all-am make[2]: Entering directory '/usr/src/ecap_adapter_sample-0.2.1/src' /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I../src -I/usr/local/include -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -pipe -MT adapter_minimal.lo -MD -MP -MF .deps/adapter_minimal.Tpo -c -o adapter_minimal.lo adapter_minimal.cc libtool: compile: g++ -DHAVE_CONFIG_H -I../src -I/usr/local/include -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -pipe -MT adapter_minimal.lo -MD -MP -MF .deps/adapter_minimal.Tpo -c adapter_minimal.cc -DDLL_EXPORT -DPIC -o .libs/adapter_minimal.o libtool: compile: g++ -DHAVE_CONFIG_H -I../src -I/usr/local/include -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -pipe -MT adapter_minimal.lo -MD -MP -MF .deps/adapter_minimal.Tpo -c adapter_minimal.cc -o adapter_minimal.o /dev/null 21 mv -f .deps/adapter_minimal.Tpo .deps/adapter_minimal.Plo /bin/sh ../libtool --tag=CXX --mode=link g++ -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -pipe -module -avoid-version -L/usr/local/lib -lecap -o ecap_adapter_minimal.la -rpath /usr/local/lib adapter_minimal.lo *** Warning: This system can not link to static lib archive /usr/local/lib/libecap.la. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have. *** But as you try to build a module library, libtool will still create *** a static module, that should work as long as the dlopening application *** is linked with the -dlopen flag to resolve symbols at runtime. libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin shared libraries libtool: link: /usr/bin/ar cru .libs/ecap_adapter_minimal.a adapter_minimal.o libtool: link: ranlib .libs/ecap_adapter_minimal.a libtool: link: ( cd .libs rm -f ecap_adapter_minimal.la ln -s ../ecap_adapter_minimal.la ecap_adapter_minimal.la ) --output message end--- Please give some help. Thank you. HDM1991 lionx...@gmail.com ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] squid 2.7 TPROXY not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 7:36 p.m., saleh madi wrote: Hello Amos, Many thanks for your reply. Before two years I have tested squid 2.7 it's very stable and in the high http traffic request is very stable no crash. But for squid-3 I see too many different releases 3.0.x , 3.1.x, 3.2.x, 3.3.x and the current 3.4.x. What is the stable release in squid-3, that work with TPROXY and can carry more high http traffic request without crash in compare with squid 2.7 and In summary: The latest you can get (aka 3.4.8) The long answer: http://www.squid-cache.org/Versions/ has the answers you seek about what Squid versions are most current stable. That page says Stable releases - 3.4, clicking the 3.4 link goes to a page saying: Latest 3.4 series release - 3.4.8. (** we are having trouble with some of our mirror servers at present, please check the final page says 3.4.8. If not refresh or use west.squid-cache.org domain name. **) Squid-3 has many packages because we have a monthly release schedule. All releases with two dots (x.y.z) are considered production ready stable releases. For any x.y series the higher the z number the better. So ... most of the time you should pick the one with latest number at the time when installing (the versions and package download pages can help there). Then can choose to stay with it (aka stable unchanging) until something major requires an upgrade, or you can follow the releases and stay on top of all sorts of small issues. Each month in the announcement I try to highlight what sort of criteria you need to consider when deciding. As of today the current stable is Squid-3.4.8, and there is also a Squid-3.5.0.1 beta for people wanting to try out some cool new features from the upcoming 3.5 series. Regarding your Question: * all the Squid versions 3.2 or later can handle more traffic than what Squid-2.7 could. Performance is a constant topic of ongoing improvement. * all releases since the *minimum* Squid package number (3.1.*) named in the TPROXYv4 wiki page support TPROXYv4. what is alternative for COSS in squid-3 for small index object for the high http traffic request. * Rock storage type has replaced COSS. That is a feature added in Squid-3.2 series. Although be aware the Squid-3.2 to Squid-3.4 series rock storage is limited by shared-memory design to only store 32KB or smaller objects. This is sufficient for most use-cases. If you have some important need for 32KB sized objects to be in the Rock store, you will need to use the 3.5 series (currently beta) where that limit has been removed. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURhOCAAoJELJo5wb/XPRjdggIAMrDu/ARrUhRCFMFbuivv5kU VKMpv/hbrZqPTwskpAVZxu8hFbUIko+CEzurLEcY2ybBlqX0HBsHqo2pGYLFC3As 4RqenWsF7jCeJIK9OhNMNLy3gNIQzcV6QVfRNG8PmspThhg9JOAj1r8tOuXUzB8q OrtNCyYQO8R5eYKB9nzniNzJLWYcEy6F1z1F5d7+SPGb3evORwxiHhpo1yGiqh+6 aqXwxLYZkE3hLB8JPXsGta5c4cMdU1YZSwTGgeJQER3+oszjJTXfQJt7mHDZSbcD 3Jc5Lk71NnatJGDh8nDUieiahkLwE56vK0WtrMVknGTP2UC+wD+lpDC2cj/5hHo= =N8xe -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Question about compiling and loading ecap-adapter module on windows
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 8:52 p.m., lionx...@gmail.com wrote: Hi. I‘m coming again. Now, I have compiled squid-3.3.3 with --enable-ecap option successfully on cygwin and run it successfully on windows. But, there are another question about compiling ecap-adapter module？ I'm not sure that I should ask this question here, maybe I should ask eCAP developer. but I think that I should try it firstly. Probably. But I'll give this a try at answering... OK! Question 1: Does it need compile ecap-adapter module as .dll file if I want use ecap-adapter module on windows. If it is running natively on Windows, the answer is yes. If it is running inside the cygwin environment (I suspect so) then the answer might be no. The cygwin people maybe could help there. Question 2: If it need, How to do it and do I shoud ask eCAP developer? Now, when I compile ecap-adapter module(ecap_adapter_sample-0.2.1.tar.gz) directly on cygwin. I just get .a .la file. Here is some output message when I make it. IF its necessary the .dll parts should be done by your compiler tools automatically. The error it produced gives a few obscure hints... --output message--- Making all in src make[1]: Entering directory '/usr/src/ecap_adapter_sample-0.2.1/src' make all-am make[2]: Entering directory '/usr/src/ecap_adapter_sample-0.2.1/src' /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I../src -I/usr/local/include -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -pipe -MT adapter_minimal.lo -MD -MP -MF .deps/adapter_minimal.Tpo -c -o adapter_minimal.lo adapter_minimal.cc libtool: compile: g++ -DHAVE_CONFIG_H -I../src -I/usr/local/include -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -pipe -MT adapter_minimal.lo -MD -MP -MF .deps/adapter_minimal.Tpo -c adapter_minimal.cc -DDLL_EXPORT -DPIC -o .libs/adapter_minimal.o libtool: compile: g++ -DHAVE_CONFIG_H -I../src -I/usr/local/include -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -pipe -MT adapter_minimal.lo -MD -MP -MF .deps/adapter_minimal.Tpo -c adapter_minimal.cc -o adapter_minimal.o /dev/null 21 mv -f .deps/adapter_minimal.Tpo .deps/adapter_minimal.Plo /bin/sh ../libtool --tag=CXX --mode=link g++ -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -pipe -module -avoid-version -L/usr/local/lib -lecap -o ecap_adapter_minimal.la -rpath /usr/local/lib adapter_minimal.lo *** Warning: This system can not link to static lib archive /usr/local/lib/libecap.la. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have. *** But as you try to build a module library, libtool will still create *** a static module, that should work as long as the dlopening application *** is linked with the -dlopen flag to resolve symbols at runtime. So, what its saying is that the libecap.la was built with -static compiler flag. But the app now being built requires it to be dynamic instead. If Squid is also built with the -dlopen flag (Squid should be) then the above warning does not matter. libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin shared libraries This warning might be more problematic, but given its just a warning and the earlier one said it was okay... in your place I would test the run-time behaviour to see if its really broken. HTH Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURhceAAoJELJo5wb/XPRjVcwIAJOmEMfuKIDltB4sZPvZaakH t77AwURtHd7R/zO4yAWVchrxUlaLOGyx9u2lykwA+zH28e9rPd3ukNND6v/43F9U xIzQtpW5BoGnYPWtviod8bVqkDqs7sueyxtdcn+AOuG4UXLAh+SD/6EF9c97/7h/ gZHyAHg08C0hQPokCTtXKhI9CiLzdh94cN7poWcQV//XZib4HL/NNC1e2fBZirZm ab4aEt+e8Asr53T278pMZ5AriawUiIi4N6wIQbSB6+1r90JVjcuf3ISbnTBS7IN7 u1epMhVnMsZx8KhzCsmIvQC/aLXZD3uUpkzaSgXzZ5lQy+Hr5/M9Y6iB+QLmcpY= =PnXT -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] squid 2.7 TPROXY not working
Hello Amos, For squid 3.4.8, In the server we have 2xssd 240GB and 4XHDD 2000GB, Internet bandwidth 600Mbits and four squid instances, please what is the suggestion settings for cache_dir for SSD and HDD to cover the high http traffic request. Thank you and Best Regards, Saleh - Original Message - From: Amos Jeffries squ...@treenet.co.nz To: saleh madi saleh.m...@hadara.ps Cc: squid-users@lists.squid-cache.org Sent: Tuesday, October 21, 2014 10:04:18 AM Subject: Re: [squid-users] squid 2.7 TPROXY not working -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 7:36 p.m., saleh madi wrote: Hello Amos, Many thanks for your reply. Before two years I have tested squid 2.7 it's very stable and in the high http traffic request is very stable no crash. But for squid-3 I see too many different releases 3.0.x , 3.1.x, 3.2.x, 3.3.x and the current 3.4.x. What is the stable release in squid-3, that work with TPROXY and can carry more high http traffic request without crash in compare with squid 2.7 and In summary: The latest you can get (aka 3.4.8) The long answer: http://www.squid-cache.org/Versions/ has the answers you seek about what Squid versions are most current stable. That page says Stable releases - 3.4, clicking the 3.4 link goes to a page saying: Latest 3.4 series release - 3.4.8. (** we are having trouble with some of our mirror servers at present, please check the final page says 3.4.8. If not refresh or use west.squid-cache.org domain name. **) Squid-3 has many packages because we have a monthly release schedule. All releases with two dots (x.y.z) are considered production ready stable releases. For any x.y series the higher the z number the better. So ... most of the time you should pick the one with latest number at the time when installing (the versions and package download pages can help there). Then can choose to stay with it (aka stable unchanging) until something major requires an upgrade, or you can follow the releases and stay on top of all sorts of small issues. Each month in the announcement I try to highlight what sort of criteria you need to consider when deciding. As of today the current stable is Squid-3.4.8, and there is also a Squid-3.5.0.1 beta for people wanting to try out some cool new features from the upcoming 3.5 series. Regarding your Question: * all the Squid versions 3.2 or later can handle more traffic than what Squid-2.7 could. Performance is a constant topic of ongoing improvement. * all releases since the *minimum* Squid package number (3.1.*) named in the TPROXYv4 wiki page support TPROXYv4. what is alternative for COSS in squid-3 for small index object for the high http traffic request. * Rock storage type has replaced COSS. That is a feature added in Squid-3.2 series. Although be aware the Squid-3.2 to Squid-3.4 series rock storage is limited by shared-memory design to only store 32KB or smaller objects. This is sufficient for most use-cases. If you have some important need for 32KB sized objects to be in the Rock store, you will need to use the 3.5 series (currently beta) where that limit has been removed. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURhOCAAoJELJo5wb/XPRjdggIAMrDu/ARrUhRCFMFbuivv5kU VKMpv/hbrZqPTwskpAVZxu8hFbUIko+CEzurLEcY2ybBlqX0HBsHqo2pGYLFC3As 4RqenWsF7jCeJIK9OhNMNLy3gNIQzcV6QVfRNG8PmspThhg9JOAj1r8tOuXUzB8q OrtNCyYQO8R5eYKB9nzniNzJLWYcEy6F1z1F5d7+SPGb3evORwxiHhpo1yGiqh+6 aqXwxLYZkE3hLB8JPXsGta5c4cMdU1YZSwTGgeJQER3+oszjJTXfQJt7mHDZSbcD 3Jc5Lk71NnatJGDh8nDUieiahkLwE56vK0WtrMVknGTP2UC+wD+lpDC2cj/5hHo= =N8xe -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] squid 2.7 TPROXY not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 9:32 p.m., saleh madi wrote: Hello Amos, For squid 3.4.8, In the server we have 2xssd 240GB and 4XHDD 2000GB, Internet bandwidth 600Mbits and four squid instances, please what is the suggestion settings for cache_dir for SSD and HDD to cover the high http traffic request. Is this a quad-core machine? Try a single Squid-3 instance with directive workers 4 in the config file, and same cache_dir layout you had for Squid-2. Using appropriate min-size/max-size changes for the 32KB limit of Rock dirs (actually use 32000 bytes limit to be safe). (If you want a squid.conf audit please post it.) Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURh8AAAoJELJo5wb/XPRjG4cH/2bcQ6MRr1+CjJNOWsqt7kkB TG6+nUZV7GV1LusUJ/1T+9xNiYlWvp2htONYMrf/LY12jWiAuG/sGjkdvK6wVt5z 4EjT6IQCO5xjNOxkLSPGCzF8azlLOO7Jnp+ZiHgYI8g5SdsM69zAjNi8LIXK+sDE 8sxLqO/Gf66m2RRTyv4nfqil+znR8p5vZ3O7kRy3L+3KduVrQiGof6FlKdmOtGwk JSeRMZri595JkOm38cttrSCmXm0z9ZFVB3pE1ZPzbebE6SMgMyOYpg+z83HG74lt erUBSXTQnw4/0Sp3QNdygFloZf+dK0TRM3grCoWRtDSFxk7v5mTQFyeqyWToWb4= =9UcO -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
[squid-users] assertion failed: lm_request-waiting
Hi. Is someone getting this too ? I get this with sad regularity: # grep lm_request /var/log/squid/cache.log 2014/10/06 14:32:12 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/07 16:06:10 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/16 16:28:48 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/17 14:32:34 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/17 14:33:09 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/21 12:25:18 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting each time squid crashes. I filed a http://bugs.squid-cache.org/show_bug.cgi?id=4104, but noone got interesed. I accept, this happens only on one of many installations. Probably someone knows a workaround ? Thanks. Eugene. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
[squid-users] Squid in captive portal and reconfigure
Hello, integrating squid in a captive portal environment, i have to setup different profiles in order to apply restrictions dinamically. The squid -k reconfigure kill active sessione/connections? I tried when downloading a file, it stops for one/two seconds and then continues download, but i am not sure if sessiones are dropped/renewed. Thank you, Francesco ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Question about squid 3.5.x and SSL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/10/2014 5:40 a.m., Mike wrote: I was reading through the release notes for squid 3.5, and in section 2.4 regarding HTTPS, it mentions When Squid is built with the GnuTLS encryption library the tool is able to open TLS (or SSL/3.0) connections to servers, and the wording makes me think that when openssl is in use, squid cannot open TLS/SSL connections to servers... So my question is if it will still properly able to open TLS/SSL connections to server when openssl is in use (like we currently are using with 3.4.6 and ssl_bump)? Or is gnutls recommended for use with squid 3.5.x (despite its massive bugs and vulnerabilities compared to openssl)? Squid is a small collection of related programs. There is a squid proxy binary, and also there is a separate squidclient binary which is a tool for manual command line or scripted HTTP requests. Somewhat like curl or wget but more oriented at debugging traffic. Section 2.4 applies *only* to that squidclient tool. The main squid and other binaries do not yet have any use of GnuTLS, which is mentioned in section 4.1 build options. That is planned to change, but timeline is flexible still as its one of my spare-time unpaid efforts. Regarding: the wording makes me think that when openssl is in use, squid cannot open TLS/SSL connections to servers... Correct, at least within the context of squidclient tool which section 2.4 is all about. When using only OpenSSL the squidclient tool does not have any HTTPS support. Never has. and my last question, regarding squid usage by people on HTTPS websites, what are some primary differences of using gnutls versus openssl? Primary difference as applies to Squid is that OpenSSL support has been present across most of the Squid code for years and GnuTLS support is only just now being added. The main reason for adding it is GnuTLS is popular, portable, feature compatible with what we use in OpenSSL, and also GPL license compatibile. By using it our downstream distributors are able to package HTTPS enabled binaries where previously they were prohibited by OpenSSL license conditions. PS. if you are building Squid I highly recommend you add libnettle and libgnutls to your build environment. Both of them should be easily available in any OS. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURwztAAoJELJo5wb/XPRj7rkH/32jQaVSVKRRAYywHtLbBbaW z+OVN6BwdoZES58JfZKupJFGb9RvOEb+wI+eCYb7RGXgFWOOqO7HUyZtCVDNYDpu 1pOoxIYiZ0pIsnjgLdSLTkffMIbywKWmSH7l4JGIna+UduJbYSIY1hCEqqGof96o 2kUE7aV2/Z9gNZtjK1/sJMgmrnnVV/ZHXWKcIiAsZBq2LxcLbtvmFutLUfBhoGw5 KzbocDh3dpUA95dwSYmNCji98YXCzo7Gz7qUeROdJj+ca9ReMAlmwU3975/T5hNY tEeynBvPZa1HWZm9XpXA2WvAhjRRm4TaKsBFLtpo3ojv9NvgePXMRw9Cha3OQfM= =8EVN -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] assertion failed: lm_request-waiting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/10/2014 5:11 a.m., Eugene M. Zheganin wrote: Hi. Is someone getting this too ? I get this with sad regularity: # grep lm_request /var/log/squid/cache.log 2014/10/06 14:32:12 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/07 16:06:10 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/16 16:28:48 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/17 14:32:34 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/17 14:33:09 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting 2014/10/21 12:25:18 kid1| assertion failed: UserRequest.cc:229: lm_request-waiting each time squid crashes. I filed a http://bugs.squid-cache.org/show_bug.cgi?id=4104, but noone got interesed. Sorry about that. The server outage in Sept meant a lot of things had to be triaged to low-priority, or relevant people did not get notified. The bug backlog is still being assessed. I accept, this happens only on one of many installations. Probably someone knows a workaround ? Followed up in the bug report. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURyZYAAoJELJo5wb/XPRjN+4IAN1Zm0YcA97ITN+tgLFVKmpy IrYOBtf4zm9ZF5+YRrNr5+ruvf+4mJnzLbeTikFvPlIt6hh3Z+2Hy4NNS1Q2g+N6 YG8Zbf9euMBL/VyoEqSs8busqMYdQ5jHlwDim7qASyyKENOqJLHS7NLsGNbcWrfs YMSHi1ITxhEeVafeu/d0Kea447mKAy10sv+SUvj4QtUqLLztQ5zkdSoESzwbQiK6 dAlSdDLdR1H6/Bq5eqG76cnFkTlgDgvSuNIxnYCfnqDJI+d3GGM7Fk3EzMBnfHQ0 GmTL5DM1mwZ1n/lqQH/0Ix4lsvqKiGUTbJaPcYGQLL9Y7psz3rYgzoiv/j+nec0= =hq1e -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
