Hello,
I have a problem here with:
[root@ablprx01 squid]# cat /etc/*release CentOS release 5.2 (Final) [root@ablprx01 squid]# rpm -qa|grep -i squid squid-2.6.STABLE6-5.el5_1.3
The web proxy process (used by 300-400 users) seems to run ok:
[root@ablprx01 squid]# ps uawwwx|grep squid root 2304 0.0 0.0 7792 1268 ? Ss 08:45 0:00 squid -D squid 3082 27.7 0.9 46912 37068 ? R 10:21 32:18 (squid) -D squid 3083 0.0 0.0 1508 232 ? Ss 10:21 0:00 (unlinkd)
[root@ablprx01 squid]# netstat -an|grep LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN .........
but periodically it will stop working (web pages can't be displayed).
The "service squid restart" command will display a lot of dots ..... but doesn't help and I have to reboot.
I've checked /var/log/messages and also /var/log/squid/* but don't see any warning there.
ifconfig doesn't report any errors:
[root@ablprx01 squid]# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:35:5B:39:AE inet addr:10.121.42.32 Bcast:10.121.255.255 Mask:255.255.0.0 inet6 addr: fe80::216:35ff:fe5b:39ae/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:989588 errors:0 dropped:0 overruns:0 frame:0 TX packets:1150056 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:590019020 (562.6 MiB) TX bytes:639895003 (610.2 MiB) Interrupt:185
and the disk space is plenty.
Has anybody had a similar problem and how would you debug it please?
Thank you for any hints Alex
PS: Below my config file:
[root@ablprx01 squid]# grep -v ^# /etc/squid/squid.conf | grep -v ^$ http_port 3128 http_port 8080 hierarchy_stoplist cgi-bin ? acl QUERY urlpath_regex cgi-bin ? cache deny QUERY acl apache rep_header Server ^Apache broken_vary_encoding allow apache cache_dir ufs /var/spool/squid 40000 16 256 access_log /var/log/squid/access.log squid dns_defnames on refresh_pattern ^ftp: 1440 20% 10080 refresh_pattern ^gopher: 1440 0% 1440 refresh_pattern . 0 20% 4320 acl all src 0.0.0.0/0.0.0.0 acl manager proto cache_object acl localhost src 127.0.0.1/255.255.255.255 acl to_localhost dst 127.0.0.0/8 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT http_access allow manager localhost http_access deny manager http_access deny !Safe_ports http_access deny CONNECT !SSL_ports acl our_networks src 10.121.0.0/16 172.25.0.0/16 10.122.1.0/24 http_access allow our_networks http_access allow localhost http_access deny all http_reply_access allow all icp_access allow all cache_mgr it@XXXXXX.com coredump_dir /var/spool/squid
From: Alexander Farber alexander.farber@gmail.com
[root@ablprx01 squid]# rpm -qa|grep -i squid squid-2.6.STABLE6-5.el5_1.3
Sadly, CentOS squid packages are quite old. Squid recent releases are: 2.7.STABLE5 and 3.0.STABLE12... Latest 2.6 is STABLE22
I've checked /var/log/messages and also /var/log/squid/* but don't see any warning there.
The last lines to the log files would be helpful.
Try also the squid mailing list... But they are going to tell you your version is very old and you should compile the latest stable...
JD
Thank you,
On Mon, Feb 2, 2009 at 3:32 PM, John Doe jdmls@yahoo.com wrote:
From: Alexander Farber alexander.farber@gmail.com
[root@ablprx01 squid]# rpm -qa|grep -i squid squid-2.6.STABLE6-5.el5_1.3
Sadly, CentOS squid packages are quite old. Squid recent releases are: 2.7.STABLE5 and 3.0.STABLE12... Latest 2.6 is STABLE22 .... Try also the squid mailing list... But they are going to tell you your version is very old and you should compile the latest stable...
this explains, why OpenBSD+Squid worked well for us at the same server - I guess OpenBSD's Squid package is better maintained.
Does anybody know of good Squid rpm's?
For example I use this for Postgres and it works well, wonder if there are similar repositories for Squid:
$ cat /etc/yum.repos.d/pgdg-82-centos.repo [pgdg82] name=PostgreSQL 8.2 $releasever - $basearch baseurl=http://yum.pgsqlrpms.org/8.2/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG
[pgdg82-source] name=PostgreSQL 8.2 $releasever - $basearch - Source failovermethod=priority baseurl=http://yum.pgsqlrpms.org/srpms/8.2/redhat/rhel-$releasever-$basearch enabled=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG
Regards Alex
Alexander Farber wrote:
Hello,
On Mon, Feb 2, 2009 at 3:32 PM, John Doe jdmls@yahoo.com wrote:
From: Alexander Farber alexander.farber@gmail.com
[root@ablprx01 squid]# rpm -qa|grep -i squid squid-2.6.STABLE6-5.el5_1.3
Sadly, CentOS squid packages are quite old. Squid recent releases are: 2.7.STABLE5 and 3.0.STABLE12... Latest 2.6 is STABLE22
Does anybody know of good Squid rpm's?
squid-2.6.STABLE22-1.fc8 here works on CentOS 5.2 home server (2 users).
regards Olaf
Alexander Farber wrote:
Does anybody know of good Squid rpm's?
I have sourced our 2.6 packages from http://people.redhat.com/mnagy/squid/ for the last few years without problems.
Dean
Alexander Farber wrote on Wed, 4 Feb 2009 09:20:49 +0100:
this explains, why OpenBSD+Squid worked well for us at the same server - I guess OpenBSD's Squid package is better maintained.
CentOS supplied Squid is running just fine here.
Kai
this explains, why OpenBSD+Squid worked well for us at the same server - I guess OpenBSD's Squid package is better maintained.
CentOS supplied Squid is running just fine here.
Talking about squid versions: Advisory SQUID-2009:1 "Due to an internal error Squid is vulnerable to a denial of service attack when processing specially crafted requests." "This bug is fixed by Squid versions 2.7.STABLE6, 3.0.STABLE13, and 3.1.0.5."
JD
Uh oh http://people.redhat.com/mnagy/squid/ doesn't have them yet...
On Wed, Feb 4, 2009 at 1:06 PM, John Doe jdmls@yahoo.com wrote:
Talking about squid versions: Advisory SQUID-2009:1 "Due to an internal error Squid is vulnerable to a denial of service attack when processing specially crafted requests." "This bug is fixed by Squid versions 2.7.STABLE6, 3.0.STABLE13, and 3.1.0.5."
John Doe wrote on Wed, 4 Feb 2009 04:06:28 -0800 (PST):
Talking about squid versions: Advisory SQUID-2009:1 "Due to an internal error Squid is vulnerable to a denial of service attack when processing specially crafted requests." "This bug is fixed by Squid versions 2.7.STABLE6, 3.0.STABLE13, and 3.1.0.5."
So, did you check if Red Hat or CentOS is aware of this and there's already a bug ticket? And if not did you submit one?
Kai
Ramon Nieto wrote:
CentOS supplied Squid is running just fine here.
Here too, 1300+ users, 80+ acl's and squidguard.
Likewise here, working as an internal cache for data used by a very busy web server farm with somewhere around 100 requests/second for most of the day. Are you sure you aren't just running out of memory or something?
On Wed, Feb 4, 2009 at 5:16 PM, Les Mikesell lesmikesell@gmail.com wrote:
Ramon Nieto wrote:
CentOS supplied Squid is running just fine here.
Here too, 1300+ users, 80+ acl's and squidguard.
Likewise here, working as an internal cache for data used by a very busy web server farm with somewhere around 100 requests/second for most of the day. Are you sure you aren't just running out of memory or something?
No, it's HP Proliant DL345 with 4GB and neither CPU nor Memory are exhausted
Regards Alex
Alexander Farber wrote:
On Wed, Feb 4, 2009 at 5:16 PM, Les Mikesell lesmikesell@gmail.com wrote:
Ramon Nieto wrote:
CentOS supplied Squid is running just fine here.
Here too, 1300+ users, 80+ acl's and squidguard.
Likewise here, working as an internal cache for data used by a very busy web server farm with somewhere around 100 requests/second for most of the day. Are you sure you aren't just running out of memory or something?
No, it's HP Proliant DL345 with 4GB and neither CPU nor Memory are exhausted
x86_64? Or could you be hitting the 2 gig process limit on a 32 bit machine?
Alexander Farber wrote:
Sadly, CentOS squid packages are quite old. Squid recent releases are: 2.7.STABLE5 and 3.0.STABLE12...
this explains, why OpenBSD+Squid worked well for us at the same server - I guess OpenBSD's Squid package is better maintained.
Except you cannot really say, just based on the version. Since CentOS is an enterprise distro there will be backported patches that is not indicated in the version of the package itself.
Backported patches will typically only relate to security and stability problems.
-
Alexander Farber -
John Doe -
Kai Schaetzl -
Les Mikesell -
Morten Torstensen -
Olaf Mueller -
Plant, Dean -
Ramon Nieto