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,0x7fffffffd980)
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,0x7fffffffd8f0,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,0x7fffffffd8f0,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,0x7fffffffda10,0x48,0,0,0)
35092 initial thread GIO fd 12 wrote 72 bytes
"<9>Nov 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.Fu@xxxxxxxxxxxxxx]
Sent: November-22-10 2:55 PM
To: squid-users@xxxxxxxxxxxxxxx; Squid Developers
Subject: RE: 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:squid3@xxxxxxxxxxxxx]
Sent: August-04-10 9:56 AM
To: squid-users@xxxxxxxxxxxxxxx; Squid Developers
Subject: Re: 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
