Re: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
On 30/11/10 04:33, Ming Fu wrote:
The cache_dir setting in the if..else ..endif does not seem to take effect.
Squid -z does create the cache subdirectory without issue, but the squid seems
to use the default cache directory as if didn't see the if statement.
= squid.conf
workers 2
if ${process_number} = 1
cache_dir aufs /usr/local/squid/var/a 500 16 256
else
cache_dir aufs /usr/local/squid/var/b 500 16 256
endif
==
=logs===
2010/11/29 15:23:56 kid1| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/29 15:23:56 kid1| Set Current Directory to /usr/local/squid/var/cache
2010/11/29 15:23:58 kid1| basic/basicScheme.cc(64) done: Basic authentication
Schema Detached.
2010/11/29 15:23:58 kid3| basic/basicScheme.cc(64) done: Basic authentication
Schema Detached.
Hmm, Schema Detatch is not good. It means any change to basic auth will
need a full restart instead of a reconfigure. That limit is no longer
normal in squid-3.2+.
2010/11/29 15:27:04 kid3| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/29 15:27:04 kid2| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/29 15:27:04 kid1| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/29 15:27:04 kid3| Set Current Directory to /usr/local/squid/var/cache
2010/11/29 15:27:04 kid1| Set Current Directory to /usr/local/squid/var/cache
2010/11/29 15:27:04 kid2| Set Current Directory to /usr/local/squid/var/cache
Note how .../var/cache is not in your config at all. It is a default
home location for the core dumps etc.
FATAL: kid2 registration timed out
... something else is causing the worker process not to make contact
with the coordinator process.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.9
Beta testers wanted for 3.2.0.3
RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
-Original Message- 2010/11/29 15:27:04 kid3| Set Current Directory to /usr/local/squid/var/cache 2010/11/29 15:27:04 kid1| Set Current Directory to /usr/local/squid/var/cache 2010/11/29 15:27:04 kid2| Set Current Directory to /usr/local/squid/var/cache Note how .../var/cache is not in your config at all. It is a default home location for the core dumps etc. FATAL: kid2 registration timed out ... something else is causing the worker process not to make contact with the coordinator process. Any hint on how can I find out the problem source. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.9 Beta testers wanted for 3.2.0.3
RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
Hi Henrik, Thanks for point out that I need to use the if..else--endif statement, however, I can't find the condition macros for the if to test. For example, If first worker Cache_dir here ... Else Cache_dir there ... Endif How do I say the first worker? Ming -Original Message- From: Henrik Nordström [mailto:hen...@henriknordstrom.net] Sent: November-27-10 4:34 AM To: Ming Fu Cc: squid-users@squid-cache.org; Squid Developers Subject: RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored fre 2010-11-26 klockan 21:08 + skrev Ming Fu: Ktrace shown that the bind failed because it try to open unix socket in /usr/local/squid/var/run and it does not have the permission. So it is easy to fix. After the permission is corrected, I run into other problem, here is the log snip: 2010/11/26 20:55:35 kid2| Starting Squid Cache version 3.2.0.3 for amd64-unknown-freebsd8.1... 2010/11/26 20:55:35 kid3| Starting Squid Cache version 3.2.0.3 for amd64-unknown-freebsd8.1... 2010/11/26 20:55:35 kid1| Starting Squid Cache version 3.2.0.3 for amd64-unknown-freebsd8.1... 2010/11/26 20:55:35 kid3| Set Current Directory to /usr/local/squid/var/cache 2010/11/26 20:55:35 kid2| Set Current Directory to /usr/local/squid/var/cache 2010/11/26 20:55:35 kid1| Set Current Directory to /usr/local/squid/var/cache Each worker need their own cache location. http://www.squid-cache.org/Versions/v3/3.2/RELEASENOTES.html#ss2.1 Regards Henrik
Re: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
On 30/11/10 02:41, Ming Fu wrote:
Hi Henrik,
Thanks for point out that I need to use the if..else--endif statement, however,
I can't find the condition macros for the if to test.
For example,
If first worker
Cache_dir here ...
Else
Cache_dir there ...
Endif
How do I say the first worker?
if ${process_number} = 1
...
else
...
endif
Another method if you want a cache_dir for each is to have a numbered
subdirectory for each worker:
cache_dir aufs /var/cache/${process_number} ...
Then squid -z to create as usual. Just remember that this will take up N
times the configured directory size.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.9
Beta testers wanted for 3.2.0.3
RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
The cache_dir setting in the if..else ..endif does not seem to take effect.
Squid -z does create the cache subdirectory without issue, but the squid seems
to use the default cache directory as if didn't see the if statement.
= squid.conf
workers 2
if ${process_number} = 1
cache_dir aufs /usr/local/squid/var/a 500 16 256
else
cache_dir aufs /usr/local/squid/var/b 500 16 256
endif
==
=logs===
2010/11/29 15:23:56 kid1| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/29 15:23:56 kid1| Set Current Directory to /usr/local/squid/var/cache
2010/11/29 15:23:58 kid1| basic/basicScheme.cc(64) done: Basic authentication
Schema Detached.
2010/11/29 15:23:58 kid3| basic/basicScheme.cc(64) done: Basic authentication
Schema Detached.
2010/11/29 15:27:04 kid3| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/29 15:27:04 kid2| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/29 15:27:04 kid1| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/29 15:27:04 kid3| Set Current Directory to /usr/local/squid/var/cache
2010/11/29 15:27:04 kid1| Set Current Directory to /usr/local/squid/var/cache
2010/11/29 15:27:04 kid2| Set Current Directory to /usr/local/squid/var/cache
FATAL: kid2 registration timed out
Squid Cache (Version 3.2.0.3): Terminated abnormally.
CPU Usage: 0.024 seconds = 0.016 user + 0.008 sys
Maximum Resident Size: 10312 KB
Page faults with physical i/o: 0
FATAL: kid1 registration timed out
Squid Cache (Version 3.2.0.3): Terminated abnormally.
CPU Usage: 0.024 seconds = 0.012 user + 0.012 sys
Maximum Resident Size: 10524 KB
Page faults with physical i/o: 0
Ming
-Original Message-
From: Amos Jeffries [mailto:squ...@treenet.co.nz]
Sent: November-29-10 9:08 AM
To: squid-users@squid-cache.org
Subject: Re: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers'
(from 1 to 2) is not supported and ignored
On 30/11/10 02:41, Ming Fu wrote:
Hi Henrik,
Thanks for point out that I need to use the if..else--endif statement,
however, I can't find the condition macros for the if to test.
For example,
If first worker
Cache_dir here ...
Else
Cache_dir there ...
Endif
How do I say the first worker?
if ${process_number} = 1
...
else
...
endif
Another method if you want a cache_dir for each is to have a numbered
subdirectory for each worker:
cache_dir aufs /var/cache/${process_number} ...
Then squid -z to create as usual. Just remember that this will take up N
times the configured directory size.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.9
Beta testers wanted for 3.2.0.3
RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
fre 2010-11-26 klockan 21:08 + skrev Ming Fu: Ktrace shown that the bind failed because it try to open unix socket in /usr/local/squid/var/run and it does not have the permission. So it is easy to fix. After the permission is corrected, I run into other problem, here is the log snip: 2010/11/26 20:55:35 kid2| Starting Squid Cache version 3.2.0.3 for amd64-unknown-freebsd8.1... 2010/11/26 20:55:35 kid3| Starting Squid Cache version 3.2.0.3 for amd64-unknown-freebsd8.1... 2010/11/26 20:55:35 kid1| Starting Squid Cache version 3.2.0.3 for amd64-unknown-freebsd8.1... 2010/11/26 20:55:35 kid3| Set Current Directory to /usr/local/squid/var/cache 2010/11/26 20:55:35 kid2| Set Current Directory to /usr/local/squid/var/cache 2010/11/26 20:55:35 kid1| Set Current Directory to /usr/local/squid/var/cache Each worker need their own cache location. http://www.squid-cache.org/Versions/v3/3.2/RELEASENOTES.html#ss2.1 Regards Henrik
RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
Ktrace shown that the bind failed because it try to open unix socket in
/usr/local/squid/var/run and it does not have the permission. So it is easy to
fix.
After the permission is corrected, I run into other problem, here is the log
snip:
2010/11/26 20:55:35 kid2| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/26 20:55:35 kid3| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/26 20:55:35 kid1| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/26 20:55:35 kid3| Set Current Directory to /usr/local/squid/var/cache
2010/11/26 20:55:35 kid2| Set Current Directory to /usr/local/squid/var/cache
2010/11/26 20:55:35 kid1| Set Current Directory to /usr/local/squid/var/cache
FATAL: commonUfsDirCloseTmpSwapLog: rename failed
Squid Cache (Version 3.2.0.3): Terminated abnormally.
CPU Usage: 0.043 seconds = 0.000 user + 0.043 sys
Maximum Resident Size: 10416 KB
Page faults with physical i/o: 0
2010/11/26 20:55:38 kid1| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/26 20:55:38 kid1| Set Current Directory to /usr/local/squid/var/cache
FATAL: kid2 registration timed out
Squid Cache (Version 3.2.0.3): Terminated abnormally.
CPU Usage: 0.041 seconds = 0.010 user + 0.031 sys
Maximum Resident Size: 10324 KB
Page faults with physical i/o: 0
2010/11/26 20:55:46 kid2| Starting Squid Cache version 3.2.0.3 for
amd64-unknown-freebsd8.1...
2010/11/26 20:55:47 kid2| Set Current Directory to /usr/local/squid/var/cache
FATAL: kid1 registration timed out
Squid Cache (Version 3.2.0.3): Terminated abnormally.
===
Here is the trace log for the error
==
35092 initial thread CALL rename(0x80283f460,0x80283f430)
35092 initial thread NAMI /usr/local/squid/var/cache/swap.state.new
35092 initial thread RET rename -1 errno 2 No such file or directory
35092 initial thread CALL setgroups(0x1,0x89ccac)
35092 initial thread RET setgroups -1 errno 1 Operation not permitted
35092 initial thread CALL setgid(0)
35092 initial thread RET setgid 0
35092 initial thread CALL geteuid
35092 initial thread RET geteuid 65534/0xfffe
35092 initial thread CALL clock_gettime(0xd,0x7fffd980)
35092 initial thread RET clock_gettime 0
35092 initial thread CALL socket(PF_LOCAL,SOCK_DGRAM,0)
35092 initial thread RET socket 12/0xc
35092 initial thread CALL fcntl(0xc,F_SETFD,FD_CLOEXEC)
35092 initial thread RET fcntl 0
35092 initial thread CALL connect(0xc,0x7fffd8f0,0x6a)
35092 initial thread STRU struct sockaddr { AF_LOCAL, /var/run/logpriv }
35092 initial thread NAMI /var/run/logpriv
35092 initial thread RET connect -1 errno 13 Permission denied
35092 initial thread CALL connect(0xc,0x7fffd8f0,0x6a)
35092 initial thread STRU struct sockaddr { AF_LOCAL, /var/run/log }
35092 initial thread NAMI /var/run/log
35092 initial thread RET connect 0
35092 initial thread CALL sendto(0xc,0x7fffda10,0x48,0,0,0)
35092 initial thread GIO fd 12 wrote 72 bytes
9Nov 26 20:55:35 (squid-1): commonUfsDirCloseTmpSwapLog: rename
failed
=
What is squid trying to do here?
Also I was wondering if I run 2 workers, should I see two cache directories,
one for each worker?
Ming
-Original Message-
From: Ming Fu [mailto:ming...@watchguard.com]
Sent: November-22-10 2:55 PM
To: squid-users@squid-cache.org; Squid Developers
Subject: RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers'
(from 1 to 2) is not supported and ignored
Hi Amos,
Is there any news for this problem. I tested squid 3.2.0.3. The problem is
still there. I am using FreeBSD 8.1.
Regards,
Ming
-Original Message-
From: Amos Jeffries [mailto:squ...@treenet.co.nz]
Sent: August-04-10 9:56 AM
To: squid-users@squid-cache.org; Squid Developers
Subject: Re: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers'
(from 1 to 2) is not supported and ignored
Zeller, Jan (ID) wrote:
It looks like that message only occurs on a reconfigure. Does -k
restart
after the config change work?
Amos
hmm the change applies once squid is restarted but now I am getting :
010/08/04 08:21:20 kid3| commBind: Cannot bind socket FD 12 to [::]: (13)
Permission denied
.
.
squid is running as
cache_effective_user proxy
cache_effective_group proxy
squid processes are running but no listening port. Any clue why this happens
?
Nothing I know about should lead to a kidN using bind on [::] or 0.0.0.0.
Maybe Alex has a clue.
cc'ing to squid-dev where beta release problems really need to be
discussed. Please followup there.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.6
RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
Hi Amos, Is there any news for this problem. I tested squid 3.2.0.3. The problem is still there. I am using FreeBSD 8.1. Regards, Ming -Original Message- From: Amos Jeffries [mailto:squ...@treenet.co.nz] Sent: August-04-10 9:56 AM To: squid-users@squid-cache.org; Squid Developers Subject: Re: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored Zeller, Jan (ID) wrote: It looks like that message only occurs on a reconfigure. Does -k restart after the config change work? Amos hmm the change applies once squid is restarted but now I am getting : 010/08/04 08:21:20 kid3| commBind: Cannot bind socket FD 12 to [::]: (13) Permission denied . . squid is running as cache_effective_user proxy cache_effective_group proxy squid processes are running but no listening port. Any clue why this happens ? Nothing I know about should lead to a kidN using bind on [::] or 0.0.0.0. Maybe Alex has a clue. cc'ing to squid-dev where beta release problems really need to be discussed. Please followup there. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.6 Beta testers wanted for 3.2.0.1 No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.851 / Virus Database: 271.1.1/3050 - Release Date: 08/04/10 00:45:00
Re: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
On Wednesday 04 August 2010 16:55:46 Amos Jeffries wrote: Zeller, Jan (ID) wrote: It looks like that message only occurs on a reconfigure. Does -k restart after the config change work? Amos hmm the change applies once squid is restarted but now I am getting : 010/08/04 08:21:20 kid3| commBind: Cannot bind socket FD 12 to [::]: (13) Permission denied . . squid is running as cache_effective_user proxy cache_effective_group proxy squid processes are running but no listening port. Any clue why this happens ? Nothing I know about should lead to a kidN using bind on [::] or 0.0.0.0. Maybe Alex has a clue. cc'ing to squid-dev where beta release problems really need to be discussed. Please followup there. Amos Sorry for bumping this thread but I see the same with 3.2.0.2-20101016. Something is trying to bind to [::] and the proxy is refuzing conections. The thread title suggests that the 'workers' setting is ignored but I guess it's not as I see the 4 squid processes with ps. -- Arthur Titeica PharmEc Software Constanta Mobil: +40 729 290 969 Tel: +40 241 616 747 Fax: +40 341 815 963 signature.asc Description: This is a digitally signed message part.
RE: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
It looks like that message only occurs on a reconfigure. Does -k restart after the config change work? Amos hmm the change applies once squid is restarted but now I am getting : 010/08/04 08:21:20 kid3| commBind: Cannot bind socket FD 12 to [::]: (13) Permission denied . . squid is running as cache_effective_user proxy cache_effective_group proxy squid processes are running but no listening port. Any clue why this happens ? --- Jan
Re: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
Zeller, Jan (ID) wrote: It looks like that message only occurs on a reconfigure. Does -k restart after the config change work? Amos hmm the change applies once squid is restarted but now I am getting : 010/08/04 08:21:20 kid3| commBind: Cannot bind socket FD 12 to [::]: (13) Permission denied . . squid is running as cache_effective_user proxy cache_effective_group proxy squid processes are running but no listening port. Any clue why this happens ? Nothing I know about should lead to a kidN using bind on [::] or 0.0.0.0. Maybe Alex has a clue. cc'ing to squid-dev where beta release problems really need to be discussed. Please followup there. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.6 Beta testers wanted for 3.2.0.1
Re: [squid-users] Beta testers wanted for 3.2.0.1 - Changing 'workers' (from 1 to 2) is not supported and ignored
On Tue, 3 Aug 2010 16:51:30 +0200, Zeller, Jan \(ID\) jan.zel...@id.unibe.ch wrote: dear squid list, i'd like to use the new 'worker' feature in squid-3.2 According to http://www.squid-cache.org/Versions/v3/3.2/cfgman/workers.html default is to have only one 'worker'. Now I'd like to have at least two workers. Unfortunately it doesn't work squid[32350]: WARNING: Changing 'workers' (from 1 to 2) is not supported and ignored What am I doing wrong ? Any new compile option I ignored ? It looks like that message only occurs on a reconfigure. Does -k restart after the config change work? Amos
