Hi Eliezer,
SQUID started listening only after I run "ip6tables -P INPUT ACCEPT". I
had searched everywhere on the internet regarding this issue and no one
mentioned that IPV6 iptables rules could stop squid from listening on
TCP ports. And Squid just started without any complaint. To my
On Sun, 13 Mar 2022 18:38:05 -0400
Alex Rousskov wrote:
> > "kill -9" will definitely leave some things in an odd state. Try the
> > double-kill first.
>
> Just to add: kill -9 will not kill SMP Squid workers and other kid
> processes. To a large degree, Squid will just keep running as if
On 3/13/22 17:22, Amos Jeffries wrote:
On 14/03/22 08:48, Dave Blanchard wrote:
OK. Would there be any harm in using 'kill -9 '? 'kill '
seems to be interpreted as 'take your time, then quit whenever you're
ready.'
Indeed. Busy proxy may have many clients to finish talking to, so there
is a
On 14/03/22 08:48, Dave Blanchard wrote:
OK. Would there be any harm in using 'kill -9 '? 'kill ' seems to be
interpreted as 'take your time, then quit whenever you're ready.'
Indeed. Busy proxy may have many clients to finish talking to, so there
is a delay.
Sending the SIGHUP ('kill ') a
OK. Would there be any harm in using 'kill -9 '? 'kill ' seems to be
interpreted as 'take your time, then quit whenever you're ready.' As long as
kill -9 won't potentially cause any inconsistencies in state files or anything
like that, I guess I'll do it that way. Thanks.
--
Dave Blanchard
On 3/13/22 03:22, Dave Blanchard wrote:
If one has edited the config file and there is some kind of error in
the new config, 'squid -k interrupt' fails to kill Squid, but instead
complains about the broken config and exits. I think the correct
behavior should be for Squid to kill the running
Hey Ben,
The next step in this situation is to try and connect with netcat from a
remote host and also locally.
>From what I understood the issue was a firewall issue so Squid was
listening.
I can also assume that squid was listening.
Just For future reference:
Try to run the next commands:
sudo
Hello,
I've finally pinpointed the cause. It is my IPV6 iptables rules at
fault. Once I changed the INPUT policy from DROP to Accept, everything
works as expected! what a waste of so many hours! Thank you all
Hello,
It could be that squid doesn't like some of my packages(I'm not sure
which
Hello,
It could be that squid doesn't like some of my packages(I'm not sure
which one). I installed the following packages:
strongswan,nrpe, nagios-plugins
I also tweaked some kernel settings
net.ipv4.ip_forward = 1
net.ipv4.ip_local_port_range = 1 61000
net.ipv4.tcp_max_syn_backlog =
Hello,
It looks like that if I start installing it right after OS installation,
it works. But not if I install any packages, for example, make,
gcc,strongswan and so on. once it stop working, it will not work anymore
even if I remove all aforementioned packages. reboot also doesn't help.
I
10 matches
Mail list logo
