Zeller, Jan (ID) wrote:
Hi,
i have the same problem but was unable to fix it.
http://marc.info/?l=squid-users&m=127537675726600&w=2
---
Jan
-----Original Message-----
From: John Horne [mailto:john.horne@xxxxxxxxxxxxxx]
Sent: Montag, 19. Juli 2010 16:08
To: Squid users
Subject: ICP is disabled?
Hello,
I have just upgraded one of our Squid 2.7 stable 9 servers to 3.1.4. I
modified the squid.conf file slightly to cater for changes that
occurred
in the upgrade. However, in my cache.log file I am getting the message:
2010/07/19 15:02:09| ICP is disabled! Cannot send ICP request to
peer.
This seems to occur every few minutes. I have not modified any ICP
config lines, so I am a bit lost as to why this is happening. Our
config
shows:
==========================================================
cache_peer wwwcache1.plymouth.ac.uk sibling 3128 3130 proxy-only
no-delay no-netdb-exchange
#cache_peer wwwcache2.plymouth.ac.uk sibling 3128 3130 proxy-only
no-delay no-netdb-exchange
cache_peer wwwcache3.plymouth.ac.uk sibling 3128 3130 proxy-only
no-delay no-netdb-exchange
acl plym_src_IP src 141.163.0.0/16 10.0.0.0/8 192.168.0.0/16
172.16.0.0/12
icp_access allow plym_src_IP
icp_access deny all
==========================================================
This worked fine at 2.7, but I cannot see why 3.1 doesn't like it and
says that ICP is disabled. Any ideas?
Your listed config does not include the icp_port setting. The default
for all port types is to be closed unless configured open.
If a port was configured, then Squid was unable to open it for some
reason. Check the cache.log startup messages.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.5
