Re: [BUG] (13) Permission denied with workers | squid 3.2.3 and 3.3 rev 12500.
On 12/10/2012 5:42 PM, Alex Rousskov wrote: On 12/06/2012 12:54 PM, Eliezer Croitoru wrote: On cache log I am getting these: 2012/12/06 21:34:29.780 kid3| commBind: Cannot bind socket FD 10 to [::]: (13) Permission denied Have you see the following SMP troubleshooting hint? http://wiki.squid-cache.org/Features/SmpScale#Cannot_bind_socket_FD_NN_to_.5B::.5D:_.2813.29_Permission_denied Does it help? Alex. Thanks Alex, It helped! This is something worth better debugging description to understand that the problem is the IPC access rather then the socket binding. So now it works and I have seen in squid log: BUG #3329: Orphan Comm::Connection: local=0.0.0.0:3555 remote=[::] FD 18 flags=1 I will test performance later. Also I will need to change the RPM to match these ownership problems. Maybe even to validate it in the start-up script. Thanks, Eliezer -- Eliezer Croitoru https://www1.ngtech.co.il sip:ngt...@sip2sip.info IT consulting for Nonprofit organizations eliezer ngtech.co.il
Re: [BUG] (13) Permission denied with workers | squid 3.2.3 and 3.3 rev 12500.
On 12/06/2012 12:54 PM, Eliezer Croitoru wrote: > On cache log I am getting these: > 2012/12/06 21:34:29.780 kid3| commBind: Cannot bind socket FD 10 to > [::]: (13) Permission denied Have you see the following SMP troubleshooting hint? http://wiki.squid-cache.org/Features/SmpScale#Cannot_bind_socket_FD_NN_to_.5B::.5D:_.2813.29_Permission_denied Does it help? Alex.
Re: [BUG] (13) Permission denied with workers | squid 3.2.3 and 3.3 rev 12500.
On 12/10/2012 04:14 AM, Amos Jeffries wrote: > On 8/12/2012 3:48 a.m., Henrik Nordström wrote: >> tor 2012-12-06 klockan 21:54 +0200 skrev Eliezer Croitoru: >>> On cache log I am getting these: >>> 2012/12/06 21:34:29.780 kid3| commBind: Cannot bind socket FD 10 to >>> [::]: (13) Permission denied >> Odd.. the debug output indicates this is a request for assigning an >> ipv6:port. > For some reason these messages also occur when IPC socket opening fails. Which is what the above message is probably about. We have discussed making Ip::Address UDS-aware. This is one of the areas where that awareness is needed. Cheers, Alex.
Re: [BUG] (13) Permission denied with workers | squid 3.2.3 and 3.3 rev 12500.
On 12/10/2012 01:14 PM, Amos Jeffries wrote: On 8/12/2012 3:48 a.m., Henrik Nordström wrote: tor 2012-12-06 klockan 21:54 +0200 skrev Eliezer Croitoru: On cache log I am getting these: 2012/12/06 21:34:29.780 kid3| commBind: Cannot bind socket FD 10 to [::]: (13) Permission denied Odd.. the debug output indicates this is a request for assigning an ipv6:port. For some reason these messages also occur when IPC socket opening fails. Amos I will test and will try to get some strace data later this week. Since I had a small misfortune at home everything will take more time. By the way, what about the new helpers format for the helpers included in squid? Thanks, Eliezer
Re: [BUG] (13) Permission denied with workers | squid 3.2.3 and 3.3 rev 12500.
On 8/12/2012 3:48 a.m., Henrik Nordström wrote: tor 2012-12-06 klockan 21:54 +0200 skrev Eliezer Croitoru: On cache log I am getting these: 2012/12/06 21:34:29.780 kid3| commBind: Cannot bind socket FD 10 to [::]: (13) Permission denied Odd.. the debug output indicates this is a request for assigning an ipv6:port. For some reason these messages also occur when IPC socket opening fails. Amos
Re: [BUG] (13) Permission denied with workers | squid 3.2.3 and 3.3 rev 12500.
tor 2012-12-06 klockan 21:54 +0200 skrev Eliezer Croitoru: > On cache log I am getting these: > 2012/12/06 21:34:29.780 kid3| commBind: Cannot bind socket FD 10 to > [::]: (13) Permission denied Odd.. the debug output indicates this is a request for assigning an ipv6:port. What do strace say? > Since there are more users with workers out there, they dont have this > issue? I have some issues with workers, but have not seen this issue. Regards Henrik
[BUG] (13) Permission denied with workers | squid 3.2.3 and 3.3 rev 12500.
I am trying to work with workers and it seems to not bind the sockets. Basic settings with build options: Squid Cache: Version 3.HEAD-BZR configure options: '--prefix=/opt/squid33-12500' '--enable-delay-pools' '--enable-icap-client' '--disable-wccp' '--disable-wccpv2' '--enable-ssl' '--enable-linux-netfilter' '--disable-ipv6' '--disable-translation' '--disable-auto-locale' '--with-default-user=proxy' '--with-large-files' '--with-dl' '--enable-leakfinder' '--with-valgrind-debug' '--enable-ssl-crtd' On cache log I am getting these: 2012/12/06 21:34:29.780 kid3| commBind: Cannot bind socket FD 10 to [::]: (13) Permission denied 2012/12/06 21:34:29.806 kid2| commBind: Cannot bind socket FD 20 to [::]: (13) Permission denied 2012/12/06 21:34:29.812 kid1| commBind: Cannot bind socket FD 20 to [::]: (13) Permission denied 2012/12/06 21:34:52.210 kid2| commBind: Cannot bind socket FD 20 to [::]: (13) Permission denied And also rebuilding the cache etc. config basically is: workers 2 # more then 1 ... http_port 3127 intercept http_port 3128 http_port 3129 tproxy .. I was thinking of using debug section 5,9 to get some output but I am still not sure what and how. Since there are more users with workers out there, they dont have this issue? Linux localhost.localdomain 3.3.8-gentoo #4 SMP Fri Nov 2 15:04:14 IST 2012 x86_64 Intel(R) Atom(TM) CPU D525 @ 1.80GHz GenuineIntel GNU/Linux And also in a RedHat el6 64 bit with a xeon. No selinux at all. Thanks, Eliezer -- Eliezer Croitoru https://www1.ngtech.co.il sip:ngt...@sip2sip.info IT consulting for Nonprofit organizations eliezer ngtech.co.il
