On 20.06.17 15:47, Eric C. Kom wrote:
Squid replied the above error:
erickom@proxy:/etc/squid3$ sudo squid3 -z
2017/06/20 15:37:37| ERROR: '.google.com' is a subdomain of 'google.com'
2017/06/20 15:37:37| ERROR: You need to remove '.google.com' from the ACL
named 'ban_list'
FATAL: Bungled
Sorry for not seen it.
Running fine now:
erickom@proxy:/etc/squid3$ sudo squid3 -z
2017/06/20 16:30:15| Squid is already running! Process ID 1584
But still the block websites are still accessible.
On 20 June 2017 at 16:24, Eric C. Kom wrote:
> Sorry for not seen
>
>
Sorry for not seen
On 20 June 2017 at 16:09, Ralf Hildebrandt
wrote:
> * Eric C. Kom :
> > Good day Folks,
> > Please I tried to block websites like youtube.com and facebook.com
> using
> > acl dstdomain directive without success.
> >
> >
* Eric C. Kom :
> Good day Folks,
> Please I tried to block websites like youtube.com and facebook.com using
> acl dstdomain directive without success.
>
> Squid replied the above error:
> erickom@proxy:/etc/squid3$ sudo squid3 -z
> 2017/06/20 15:37:37| ERROR: '.google.com'
Hi,
Today I've got this message from Squid:
You've encountered a fatal error in the Squid Cache version 3.2.0.14.
If a core file was created (possibly in the swap directory),
please execute 'gdb squid core' or 'dbx squid core', then type 'where',
and report the trace back to
On 23/12/2011 4:53 p.m., Nguyen Hai Nam wrote:
Hi,
Today I've got this message from Squid:
You've encountered a fatal error in the Squid Cache version 3.2.0.14.
If a core file was created (possibly in the swap directory),
please execute 'gdb squid core' or 'dbx squid core', then type 'where',
Hello,
thanks for the replies, I am using squidguard as a redirector, and
when I squidguard from the command line it died with 'filesize
exceeded', turned out squidguard's log had grown to 2.1GB and this was
killing squid.
Thanks,
Gavin
On 8/30/07, Amos Jeffries [EMAIL PROTECTED] wrote:
Hello,
I've been running squid-2.6stable6 quite happily for some time on a
32bit RHEL5 server. Today squid crashed and refused to come back up,
even after a reboot, with the error FATAL: the url_rewriter helpers
are crashing too rapidly, need help!
snip
Where can I start trying to figure
I receive the following email from squid sem-frequently:
From: squid
To: [EMAIL PROTECTED]
Subject: The Squid Cache (version 3.0-PRE3-20050510) died.
You've encountered a fatal error in the Squid Cache version
3.0-PRE3-20050510.
If a core file was created (possibly in the swap directory),
List,
I received this email from my squid cache:
From: squid
To: [EMAIL PROTECTED]
Subject: The Squid Cache (version 2.5.STABLE4-20040104) died.
You've encountered a fatal error in the Squid Cache version
2.5.STABLE4-20040104.
If a core file was created (possibly in the swap directory),
please
List,
I received this email from my squid cache:
From: squid
To: [EMAIL PROTECTED]
Subject: The Squid Cache (version 2.5.STABLE4-20040104) died.
You've encountered a fatal error in the Squid Cache version
2.5.STABLE4-20040104.
If a core file was created (possibly in the swap
On Thu, 6 May 2004 [EMAIL PROTECTED] wrote:
I have received two of the following emails from my squid server, but in
both cases I have not noticed any problems with the system. No disruption
in service or anything in cache.log.
Check your cache.log again.
These messages indicates your Squid
Greetings List,
I have received two of the following emails from my squid server, but in
both cases I have not noticed any problems with the system. No disruption
in service or anything in cache.log.
Is this a known issue or something I should be concerned about? Is there
something I should
Greetings List,
I have received two of the following emails from my squid
server, but in
both cases I have not noticed any problems with the system.
No disruption
in service or anything in cache.log.
Is this a known issue or something I should be concerned
about? Is there
FATAL: getpwnam failed to find userid for effective user 'squid'
Squid Cache (Version 2.4.STABLE7): Terminated abnormally.
CPU Usage: 0.010 seconds = 0.010 user + 0.000 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 317
Aborted
Problem is because of your
After
#squid -z
return this error
FATAL: getpwnam failed to find userid for effective user 'squid'
Squid Cache (Version 2.4.STABLE7): Terminated abnormally.
CPU Usage: 0.010 seconds = 0.010 user + 0.000 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 317
Aborted
What is the
Hi,
Using squid -k debug I get this error message, but I do not now what I should do to
resolv this problem, somone can help me ?
$ [EMAIL PROTECTED] tmp_logs]# tail -n 30 cache.log
$ 2003/12/03 10:00:16| Process ID 7206
$ 2003/12/03 10:00:16| With 1024 file descriptors available
$ 2003/12/03
On Monday 08 December 2003 10:43 am, Otávio Fernandes wrote:
Hi,
Using squid -k debug I get this error message, but I do not now what I
should do to resolv this problem, somone can help me ?
$ 2003/12/03 10:00:17| commBind: Cannot bind socket FD 16 to *:3128: (98)
$ FATAL: Cannot open HTTP
Sounds like you have a squid already running.
If you're on a Linux box then you can use lsof to find exactly which
process already has that port bound.
lsof is also available as a build-it-yourself for many other Unix
flavours from http://freshmeat.net/projects/lsof/
Chris
On Monday 08
19 matches
Mail list logo