FW: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory

2011-06-11 Thread Jenny Lee

I also cannot shut down squid when workers are enabled.
 
squid -k shutdown gives No Running Copy
 
I have to run a killall -9 squid
 
Also what happens when I have 2 cores but start 7 workers?
 
Jenny


 From: bodycar...@live.com
 To: squid-users@squid-cache.org
 Date: Sun, 12 Jun 2011 04:17:41 +
 Subject: [squid-users] WORKERS: Any compile option to enable? commBind: 
 Cannot bind socket FD 13 to [::]: (2) No such file or directory


 I can't get the workers work. They are started fine. However I get:

 kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or 
 directory
 kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or 
 directory
 kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or directory

 Is there a compile option to enable/disable workers that I am missing?

 The ports below work fine on mono squid.

 ---
 workers 2

 if ${process_number} = 1
 http_port 1.1.1.1:3128
 else
 http_port 1.1.1.1:3129
 endif
 ---

 Thanks

 Jenny


 RHEL6 x64
 Squid 3.2.0.7


 Compile:
 --disable-carp \
 --disable-wccp \
 --disable-wccpv2 \
 --disable-snmp \
 --disable-htcp \
 --disable-ident-lookups \
 --disable-unlinkd \
 --disable-translation \
 --disable-auto-locale \
 --disable-loadable-modules \
 --disable-esi \
 --disable-disk-io \
 --disable-eui \
 --disable-storeio \
 --disable-auth-ntlm \
 --disable-auth-negotiate \
 --disable-auth-digest \
 --disable-cache-digests \
 --disable-ntlm-auth-helpers \
 --disable-negotiate-auth-helpers \
 --disable-digest-auth-helpers \
 --disable-ipfw-transparent \
 --disable-ipf-transparent \
 --disable-pf-transparent \
 --disable-linux-tproxy \
 --disable-linux-netfilter \
 --without-netfilter-conntrack \
 --disable-url-rewrite-helpers \
 --disable-win32-service \
 --disable-zph-qos \
 --disable-icap-client \
 --disable-ecap \
 --disable-useragent-log \
 --disable-referer-log \
 --disable-eui \
 --disable-poll \
 --disable-select \
 --disable-kqueue \
 --disable-icmp \
 --disable-gnuregex \
 --disable-cpu-profiling \
 --disable-kill-parent-hack \
 --disable-follow-x-forwarded-for \
 --disable-forw-via-db \
 --without-valgrind-debug \
 --without-ipv6-split-stack \
 --without-po2html   

Re: FW: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory

2011-06-11 Thread Amos Jeffries
Again. cc'ing squid-dev where the people actually working on these 
features can see the report.


On 12/06/11 16:30, Jenny Lee wrote:


I also cannot shut down squid when workers are enabled.

squid -k shutdown gives No Running Copy

I have to run a killall -9 squid


One side effect of: --disable-kill-parent-hack

Though it may be due to other things. There was a patch proposed some 
weeks back.




Also what happens when I have 2 cores but start 7 workers?


They share cores as separate instances do. Potentially getting in each 
others way grabbing CPU cycles. This may or may not be a problem.



Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.12
  Beta testers wanted for 3.2.0.8 and 3.1.12.2