Peers die when using tcp_outgoing_address.
38 views
Skip to first unread message
Maher Kassem
Nov 3, 2011, 10:28:40 AM11/3/11
to lusca-users
Hi everyone,
I am using tcp_outoing_address with ACL's while Peering with other
caches (Peering has nothing to do with ACL's). Unfortunately, whenever
I un-hash the tcp_outgoing_address rules I start to get these errors
in my log:
2011/11/03 16:21:39| TCP connection to Cache1 (XX.XX.XX.XX:3128)
failed
2011/11/03 16:21:39| TCP connection to Cache2 (XX.XX.XX.XX:3128)
failed
And I can no longer request files from my peer or forward requests to
my peers. Has anyone come across this before, and if so how did you
solve? I have already tried putting the no-tproxy option in the
peering. Any help is appreciated.
Sincerely,
Maher.
I am using tcp_outoing_address with ACL's while Peering with other
caches (Peering has nothing to do with ACL's). Unfortunately, whenever
I un-hash the tcp_outgoing_address rules I start to get these errors
in my log:
2011/11/03 16:21:39| TCP connection to Cache1 (XX.XX.XX.XX:3128)
failed
2011/11/03 16:21:39| TCP connection to Cache2 (XX.XX.XX.XX:3128)
failed
And I can no longer request files from my peer or forward requests to
my peers. Has anyone come across this before, and if so how did you
solve? I have already tried putting the no-tproxy option in the
peering. Any help is appreciated.
Sincerely,
Maher.
Maher Kassem
Nov 25, 2011, 3:09:21 AM11/25/11
to lusca-users
Resolved.
Thanks Adrian.
Adrian Chadd
Nov 27, 2011, 1:41:51 AM11/27/11
to lusca...@googlegroups.com
Your'e welcome!
Adrian
Reply all
Reply to author
Forward
0 new messages