As long as you do not use parent proxy, no need for pinger. And, even in case
of parent, pinger is nice to have.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-not-listening-on-any-port-tp4667004p4667398.html
Sent from the Squid - Users mailing list
I have looked at the domain NS and it seems that 2 out of 4 are not
responsive at all.
If you are interested in clearing out the issue and more advanced dns
related issues you can try bind-us...@lists.isc.org list.
In the above list there are many dns administrators that can help and
consult
babajaga wrote
As long as you do not use parent proxy, no need for pinger. And, even in
case of parent, pinger is nice to have.
I don't. So that's ok.
Thanks!
--
View this message in context:
On 08/27/2014 09:31 AM, israelsilva1 wrote:
babajaga wrote
As long as you do not use parent proxy, no need for pinger. And, even in
case of parent, pinger is nice to have.
I don't. So that's ok.
Thanks!
Just make sure you have the sticky execution bit of a root user on the
pinger binary
Hey Maxim,
You should better ask about it in squid-dev list rather then squid users
list.
More knowledge about ICAP internals is there.
Eliezer
On 08/26/2014 12:12 PM, Maxim Kulikov wrote:
Hi All,
I develop ICAP server for squid. Occasionally squid closes connection to my
server, before
Hello.
Thanks for your reply.
DNS was also my first thought, but what surprises me is that on the same
server, nginx or direct are ok, but squid takes almost a minute. Also nslookup
and dig work fast.
And this happens everytime. But i'll look for DNS failures on the server
Anyone has any other
On 27/08/2014 8:50 p.m., Bruno Guerreiro wrote:
Hello.
Thanks for your reply.
DNS was also my first thought, but what surprises me is that on the same
server, nginx or direct are ok, but squid takes almost a minute. Also
nslookup and dig work fast.
And this happens everytime. But i'll look
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/08/2014 5:19 p.m., israelsilva1 wrote:
israelsilva1 wrote
babajaga wrote
1) Pinger exiting. You might try to disable pinger in
squid.conf pinger_enable off
Just for completeness: Pls, publish squid.conf, without
comments. Anonymized.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/08/2014 7:44 a.m., Markus Moeller wrote:
Hi Pavel,
Can you remove line 263 from support_krb5.cc and recompile ? It is
fixed in the trunk for 3.5.
The line is safe_free(principal_name);
Regards Markus
For the record, this fix is
squid exits with illegal instruction message
Squid Cache: Version 3.4.6-20140826-r13168
configure options: '--disable-auth' '--disable-auto-locale'
'--disable-cache-digests' '--disable-cpu-profiling'
'--disable-debug-cbdata' '--disable-delay-pools' '--disable-devpoll'
'--disable-ecap'
Please provide more details, like log output, or a coredump backtrace.
Thanks
2014-08-27 11:44 GMT-03:00 Alfredo Rezinovsky alfr...@fing.uncu.edu.ar:
squid exits with illegal instruction message
Squid Cache: Version 3.4.6-20140826-r13168
configure options: '--disable-auth'
There's no log output, it just exists. No coredump either. strace output
is useful ?
Please provide more details, like log output, or a coredump backtrace.
Thanks
2014-08-27 11:44 GMT-03:00 Alfredo Rezinovsky alfr...@fing.uncu.edu.ar:
squid exits with illegal instruction message
Squid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/08/2014 3:01 a.m., Alfredo Rezinovsky wrote:
There's no log output, it just exists. No coredump either. strace
output is useful ?
Not really for this kind of thing.
You wil have to run under a debugger, or enable core dumps in the OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.3.13 release!
This release is a security fix release resolving a major vulnerability
found in the prior Squid releases.
REMINDER: This and older releases are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
__
Squid Proxy Cache Security Update Advisory SQUID-2014:2
__
Advisory ID:SQUID-2014:2
Date:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.4.7 release!
This release is a security and bug fix release resolving a major
vulnerability and several other issues found in the prior Squid releases.
The major
Thanks!
I think I've noticed a typo in squid 3.4.7
# diff -u helpers/external_acl/kerberos_ldap_group/support_ldap.cc.orig
helpers/external_acl/kerberos_ldap_group/support_ldap.cc
--- helpers/external_acl/kerberos_ldap_group/support_ldap.cc.orig
2014-08-27 21:37:01.0 +0400
+++
Hello Squid Dev. Team and Users,
I need your advice on a Squid deployment scenario.
We have deployed on our network a physical machine with Squid 2.7 listening
on port 8080.
Proxy Auto-Discovery on our users browsers is able to get activated by a
wpad.dat file which transparently redirects our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/08/2014 7:28 a.m., Julian wrote:
Hello Squid Dev. Team and Users,
I need your advice on a Squid deployment scenario.
We have deployed on our network a physical machine with Squid 2.7
listening on port 8080. Proxy Auto-Discovery on our
19 matches
Mail list logo
