Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-19 Thread Alex Rousskov
On 8/19/19 1:58 PM, Tom Karches wrote: > It looks like connections are going out but not coming back : > > 2019/08/19 13:17:38.576 kid1| 33,2| client_side.cc(817) swanSong: > local=152.7.114.135:3128 remote=10.50.54.22:57230 flags=1 > 2019/08/19 13:17:52.050 kid1| 33,2| client_side.cc(817) swanSo

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-19 Thread Tom Karches
I thought that this was being caused by a firewall because I was seeing (requests go out, but blocked coming back) so I had the ports over 1024 opened : No. Time SourceDestination Protocol Length Info 156 16.493132 152.7.114.135 140.211.169.

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-10 Thread Alex Rousskov
On 8/9/19 4:32 PM, Tom Karches wrote: > Right now my debug is set to ALL,1 33,2. Is there a better set of > options to provide me more visibility of what might be wrong? In theory, yes: You can increase verbosity levels to see exactly what is going on. However, most people get lost in the debuggin

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-10 Thread Amos Jeffries
On 10/08/19 8:32 am, Tom Karches wrote: > > > On Fri, Aug 9, 2019 at 2:37 PM Alex Rousskov wrote: > > On 8/9/19 1:37 PM, Tom Karches wrote: > > On Fri, Aug 9, 2019 at 11:38 AM Alex Rousskov wrote: > > > Ok, here is the info from the real trace. First time with > #dns_v4_first >

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-09 Thread Tom Karches
On Fri, Aug 9, 2019 at 2:37 PM Alex Rousskov < rouss...@measurement-factory.com> wrote: > On 8/9/19 1:37 PM, Tom Karches wrote: > > On Fri, Aug 9, 2019 at 11:38 AM Alex Rousskov wrote: > > > Ok, here is the info from the real trace. First time with #dns_v4_first > > on commented out, 2nd time "dn

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-09 Thread Alex Rousskov
On 8/9/19 1:37 PM, Tom Karches wrote: > On Fri, Aug 9, 2019 at 11:38 AM Alex Rousskov wrote: > Ok, here is the info from the real trace. First time with #dns_v4_first > on  commented out, 2nd time "dns_v4_ first on" is active. Difference is > with no "dns_v4_first on" directive, I get a RR_CONNECT

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-09 Thread Tom Karches
On Fri, Aug 9, 2019 at 11:38 AM Alex Rousskov < rouss...@measurement-factory.com> wrote: > On 8/9/19 9:59 AM, Tom Karches wrote: > > > With this command : > > $curl --trace --proxy http://127.0.0.1:3128 https://www.google.com > > > Invalid URL > > Yeah, that command does not do what you think it d

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-09 Thread Alex Rousskov
On 8/9/19 9:59 AM, Tom Karches wrote: > With this command : > $curl --trace --proxy http://127.0.0.1:3128 https://www.google.com > Invalid URL Yeah, that command does not do what you think it does. This has bitten me many times. You may want to remove the file name "--proxy" now :-). Hint: The

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-09 Thread Tom Karches
> > > On 8/8/19 3:29 PM, Tom Karches wrote: > > > I am in the process of upgrading our Squid proxy server from 3.1 (on > > RHEL6) to 3.3 (on RHEL7). > > It could have been worse! For example, you could ask a question about > upgrading Squid from v1.0 to v2.0... I will try to help, but I do not > re

Re: [squid-users] Problems with squid 3.1 to 3.3 upgrade

2019-08-08 Thread Alex Rousskov
On 8/8/19 3:29 PM, Tom Karches wrote: > I am in the process of upgrading our Squid proxy server from 3.1 (on > RHEL6) to 3.3 (on RHEL7). It could have been worse! For example, you could ask a question about upgrading Squid from v1.0 to v2.0... I will try to help, but I do not remember much about