On 26/06/2014 4:37 p.m., Mike wrote:
I am looking for suggestions on a newer or slightly altered startup
script for use with squid 3.4.5 and CentOS based system (Scientific
Linux 6.5).
The issue is after a system reboot, during startup the ssl_crtd helpers
are crashing causing squid to not
On 26/06/2014 11:53 a.m., Matthew Ceroni wrote:
Amos:
Thanks for the info. I am using workers so that explains why the
output of mgr:info shows such a high number of file descriptors.
If you don't mind I need some further clarification on the output of
mgr:info. Just to summarize I have a
On 26/06/2014 1:06 a.m., Jasper Van Der Westhuizen wrote:
Hi all
I'm running a compiled version of Squid 3.4.4 and I'm having some
strange behavior lately. I have a two node cluster load balancing via a
F5 LB and at times one of the two servers will simply not complete a
connection. Squid
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.4.6 release!
This release is a bug fix release resolving memory leaks and portability
issues found in the prior Squid releases.
The major changes to be aware of:
* Regression logging custom time formats
The
Are you using SMP workers with an AUFS, UFS or diskd cache_dir?
UFS/AUFS/diskd are not SMP-aware and this is how it shows up when two
or more workers are over-writing cache disk files and corrupting each
others records.
Amos
Hi Amos
No, I don't make use of multiple SMP workers.
Yes we always disable selinux or at least change to the non-blocking
permissive mode until server is ready for development.
Mike
On 6/26/2014 12:57 AM, Eliezer Croitoru wrote:
Can you verify if SELINUX is enabled\enforced?
If so change it to disabled as a basic test to the ssl_crtd issue.
On 06/25/2014 04:06 PM, Jasper Van Der Westhuizen wrote:
As a matter of interest, in my cache logs I see many lines like these
2014/06/25 14:52:58 kid1| WARNING: swapfile header inconsistent with
available data
2014/06/25 14:53:28 kid1| WARNING: swapfile header inconsistent with
available data
OS is CentOS based Scientific Linux 6.5. Squid is version 3.4.6 (updated
today) but was happening as well with 3.4.5.
This happens only after a reboot, so there has to be an issue in the
/etc/init.d/squid startup script causing this. Something on initial
startup is causing it to start and
* Various memory leaks
After some deeper digging, it seems selinux was only temporarily
disabled (via echo 0 /selinux/enforce), not disabled in the primary
config file. But this actually allowed me to track down a fix to keep
using selinux (which we definitely need for server security). I am going
to add it here
So, I added those and restarted...still get the your computer may be
sending automated queries error form google.
I then set x forwarded for to off, no change.
Then commented out via, no change.
Current conf:
auth_param basic realm AAA proxy server
auth_param basic credentialsttl 2 hours
Hi everyone --
I recently ran into a strange condition within my Squid access logs which
is making importing the events into a database a bit more difficult.
Note, I am not logging directly to a database, but rather parsing event
into a centralized database via batch/cron.
Events in the access
So, I added those and restarted...still get the your computer may be
sending automated queries error form google.
I then set x forwarded for to off, no change.
Then commented out via, no change.
Current conf:
auth_param basic realm AAA proxy server
auth_param basic credentialsttl 2 hours
How about contacting google for advise?
They are the one that forces you to the issue.
They don't like it that you have a 1k clients behind your IP address.
They should tell you what to do.
You can tell them that you are using squid as a forward proxy to enforce
usage acls on users inside the
Hi,
I have 2 WANs and would like to loadbalance the traffic by configuring
tcp_outgoing_address based on source IPs. Squid version is 3.1.20
running on FreeBSD 8.3-release-p11 (pfSense 2.1-RELEASE).
I have tried this:
acl even src 0.0.0.0/0.0.0.1
tcp_outgoing_address wan1 even
On 27/06/2014 4:07 p.m., Nishant Sharma wrote:
Hi,
I have 2 WANs and would like to loadbalance the traffic by configuring
tcp_outgoing_address based on source IPs. Squid version is 3.1.20
running on FreeBSD 8.3-release-p11 (pfSense 2.1-RELEASE).
I have tried this:
acl even src
On 27/06/2014 2:35 p.m., Eliezer Croitoru wrote:
How about contacting google for advise?
They are the one that forces you to the issue.
They don't like it that you have a 1k clients behind your IP address.
They should tell you what to do.
You can tell them that you are using squid as a
On 27/06/2014 7:20 a.m., Alexandre wrote:
* Various memory leaks
?? are you enjoying 3.4.6 or something?
Amos
On 27/06/2014 11:25 a.m., Mark DeCheser wrote:
Hi everyone --
I recently ran into a strange condition within my Squid access logs which
is making importing the events into a database a bit more difficult.
Note, I am not logging directly to a database, but rather parsing event
into a
19 matches
Mail list logo
