Hi Amos,
i added the needed infos to: http://bugs.squid-cache.org/show_bug.cgi?id=3696
thanks.
cheers,
Chris
-Ursprüngliche Nachricht-
Von: Amos Jeffries [mailto:squ...@treenet.co.nz]
Gesendet: Mittwoch, 30. Juli 2014 13:06
An: squid-users@squid-cache.org
Betreff: Re: [squid-users
Hi Amos,
> On 30/07/2014 10:44 p.m., Labusch, Christian (regio iT) wrote:
>> - OS: Linux debian 3.2.0-4-486 #1 Debian 3.2.60-1+deb7u1 i686 GNU/Linux
>> - Squid Cache: Version 3.4.6. (configure options: '--enable-delay-pools')
>>
>> Squid.conf (Limitation 1 Mbit/s):
>>
>> client_delay_pools 1
>> cl
On 30/07/2014 10:44 p.m., Labusch, Christian (regio iT) wrote:
> Hello all,
>
> i have a little Problem with the "new" Directive "client_delay_pools". Our
> old Config with the normal delay_classes works fine. But we need additional a
> Upload-Limit.
>
> Testmachine with very simple standard c
Hello all,
i have a little Problem with the "new" Directive "client_delay_pools". Our old
Config with the normal delay_classes works fine. But we need additional a
Upload-Limit.
Testmachine with very simple standard config:
- OS: Linux debian 3.2.0-4-486 #1 Debian 3.2.60-1+deb7u1 i686 GNU/Lin
Hi all,
we have two squid servers on a large enterprise LAN for caching internet
traffic.
we currently use squid 3.3.9 with these (relevant?) settings:
pipeline_prefetch on
shutdown_lifetime 1 second
## Cache Settings ##
cache_dir diskd /squid/cache/active 51200 20 512 Q1=288 Q2=256
cache_mem 81
Hey Dan,
What is the "squid -v" output?
"uname -a"
squid.conf content?
Did you had the chance to look at squid cache manager interface?
What is the size of the stress test?
the basic idea is that A connection should be usable for squid usage but
it is not from unknown reason.
Once we have more
On 22/05/2014 1:44 p.m., Dan Charlesworth wrote:
> We were just stress testing a forward proxy of ours, and suddenly received
> this error which made squid crash pretty hard, apparently.
>
> 2014/05/22 11:38:13 kid1| assertion failed: client_side.cc:1515:
> "connIsUsable(http->getConn())"
> 2014
We were just stress testing a forward proxy of ours, and suddenly received this
error which made squid crash pretty hard, apparently.
2014/05/22 11:38:13 kid1| assertion failed: client_side.cc:1515:
"connIsUsable(http->getConn())"
2014/05/22 11:38:18 kid1| Set Current Directory to /var/spool/squ
Well it happens that 8GB of memory will not be enough for 240GB of ufs
disk cache as far as I can tell.
Lets try to fix it one step at a time.
Since you are getting into a position which squid get's stuck we can go
from step A to B and then to C.
First decrease the number of ufs directories to
Hi Eliezer,
Thanks for your response, please find the answers below.
what are the machine specs?
Machine on which Squid is running, is VM having 2 cores and 8 GB of memory.
why are you using so many ufs cache dirs? is there a reason?
Yes, our purpose is to cache more than 50M json obje
Hey,
couple questions:
- what are the machine specs?
- why are you using so many ufs cache dirs? is there a reason?
Mainly this squid version is old and I suspect it's not supported anymore.
64 doubles 5.1 is above 240GB of cache which requires lots of memory.
Eliezer
On 05/03/2014 01:39 AM,
Hello,
I am running squid as http caching server, after running for few days
our squid server will stop responding to client requests.
When this occurs, I see below errors in cache.log.
2014/05/02 12:02:57| assertion failed: store_swapout.cc:315:
"mem->swapout.sio == self"
2014/05/02 12:03:01| S
Hi all
i Have this kind of network:
1) A Squid "client" 3.3.12 with ssl-bump enabled transparent method.
2) A Squid Proxy 3.3.12 act has "parent" that listens 8080 but not in
transparent mode. It is just designed to retreive content directly from
Internet.
Browser –> SSL –> Squid client +
On 2014-03-05 01:28, Nil Nik wrote:
I am using ICAP and squid 3.3.9
After some interval I got following messages in cache.log and squid get
stop.
2014/03/04 16:01:35 kid1| ACL::checklistMatches WARNING:
'http_denied_status' ACL is used but there is no HTTP reply -- not
matching.
2014/03/04 16:
I am using ICAP and squid 3.3.9
After some interval I got following messages in cache.log and squid get stop.
2014/03/04 16:01:35 kid1| ACL::checklistMatches WARNING: 'http_denied_status'
ACL is used but there is no HTTP reply -- not matching.
2014/03/04 16:01:35 kid1| ACL::checklistMatches WARNI
On 12/19/2013 02:12 AM, hdk...@hdkutz.de wrote:
> On Wed, Dec 18, 2013 at 11:03:13AM -0700, Alex Rousskov wrote:
>> On 12/18/2013 09:07 AM, hdk...@hdkutz.de wrote:
>>> I have a Problem on a Centos 6.4 64 Bit System running RPM Package
>>> squid-3.3.11-1.el6.x86_64.rpm
>>
>>> Any hints or tips on
>
On Wed, Dec 18, 2013 at 11:03:13AM -0700, Alex Rousskov wrote:
> On 12/18/2013 09:07 AM, hdk...@hdkutz.de wrote:
> > Hello List,
> > I have a Problem on a Centos 6.4 64 Bit System running RPM Package
> > squid-3.3.11-1.el6.x86_64.rpm
>
> > Any hints or tips on
> >
> > assertion failed: Server.cc
On 12/18/2013 09:07 AM, hdk...@hdkutz.de wrote:
> Hello List,
> I have a Problem on a Centos 6.4 64 Bit System running RPM Package
> squid-3.3.11-1.el6.x86_64.rpm
> Any hints or tips on
>
> assertion failed: Server.cc:245: "r->body_pipe != NULL"
>
> ?
Please see http://bugs.squid-cache.org/sho
Hello List,
I have a Problem on a Centos 6.4 64 Bit System running RPM Package
squid-3.3.11-1.el6.x86_64.rpm
My squid.conf:
http_port 172.25.254.50:80
http_port 127.0.0.1:3128
hierarchy_stoplist cgi-bin ?
visible_hostname blbla.domain.local
coredump_dir /var/spool/squid
ignore_unknown_nameservers
> I think you need to read this first:
>
> http://wiki.squid-cache.org/SquidFaq/SquidMemory
>
> You definitely want to put more memory in the machine, the more the
> better... (up to a point since you are using 32 bit).
The link was definitely helpful in helping me tune the config, but it did no
On 24/07/2013 6:29 p.m., mdeche...@comcast.net wrote:
Hello Squid Users --
I'm very new to running squid. I've quickly learned that there are many
parameters to configure and therefore many places problems can occur.
FYI: quite a few will be picked up by squid -k parse.
I am prototyping a
On Wed, Jul 24, 2013 at 06:29:26AM +, mdeche...@comcast.net wrote:
>
> My take on all this is that it appears the server may be starved for memory.
> I have seen other strange behaviors such mysqld, squid, and pptpd daemons
> dying randomly. I've seen squid daemon restart for reasons unknow
Hello Squid Users --
I'm very new to running squid. I've quickly learned that there are many
parameters to configure and therefore many places problems can occur.
I am prototyping a squid environment on a CentOS 6.4 32-bit system with 256MB
RAM. Presently, I'm observing strange behavior with
Hi,
In our SMP enabled environnement, I have one kid to start giving the
fooloowing assertion :
2013/04/18 04:03:43 kid1| assertion failed: ufs/ufscommon.cc:706: "sde"
I guess it is something related with the store / store rebuiding.
Maybe a malformed object in the cache store?
here the part of t
Hello Amm,
On Wed, Apr 10, Amm wrote:
> - Original Message -
> > From: Dieter Bloms
> > To: squid-users@squid-cache.org
> > Cc:
> > Sent: Wednesday, 10 April 2013 3:03 PM
> > Subject: [squid-users] assertion failed: Checklist.cc:287: "!needsAsync
- Original Message -
> From: Dieter Bloms
> To: squid-users@squid-cache.org
> Cc:
> Sent: Wednesday, 10 April 2013 3:03 PM
> Subject: [squid-users] assertion failed: Checklist.cc:287: "!needsAsync &&
> !matchFinished" after upgrade from squid 3.2.
Hi,
I run 3.2.7 squid successfully for some weeks now.
Yesterday I tried to upgrade to squid 3.3.3 and after a few minutes
squid exits and I get the following messages in my cache.log:
--snip--
2013/04/09 08:44:40| Starting Squid Cache version 3.3.3 for
x86_64-suse-linux-gnu...
2013/04/09 08:44:
Hi List,
I just install from sources the last 3.2.9 squid with ssl-bump feature.
It works fine, except that I get "random" crashes as you can see below:
[...]
2013/03/14 16:48:45 kid1| assertion failed: client_side.cc:3584:
"!switchedToHttps_"
2013/03/14 16:48:48 kid1| Starting Squid Cache vers
On Wed, Jan 30, 2013 at 06:41:07PM +1300, Amos Jeffries wrote:
> On 30/01/2013 5:24 a.m., John Hay wrote:
> >Hi Guys,
> >
> >I have been seeing this pretty often lately, with both 3.2.5 and 3.2.6.
> >I'm using FreeBSD 8.x in 64 bit mode and also IPv6.
> >
> >The message in cache.log is:
> >
> >2013
On 30/01/2013 5:24 a.m., John Hay wrote:
Hi Guys,
I have been seeing this pretty often lately, with both 3.2.5 and 3.2.6.
I'm using FreeBSD 8.x in 64 bit mode and also IPv6.
The message in cache.log is:
2013/01/29 17:23:39 kid1| assertion failed: Server.cc:244: "r->body_pipe !=
NULL"
2013/01/
Hi Guys,
I have been seeing this pretty often lately, with both 3.2.5 and 3.2.6.
I'm using FreeBSD 8.x in 64 bit mode and also IPv6.
The message in cache.log is:
2013/01/29 17:23:39 kid1| assertion failed: Server.cc:244: "r->body_pipe !=
NULL"
2013/01/29 17:23:42 kid1| Starting Squid Cache vers
Hi,
My squid 3.2.2 - R is failing after a reconfigure.
Not using SMP.
here is what I find in the logs :
2012/10/24 14:54:42 kid1| assertion failed: comm.cc:163:
"!fd_table[conn->fd].closing()"
2012/10/24 14:58:29 kid1| StoreEntry->ping_status: 2
2012/10/24 14:58:29 kid
Hello,
Squid has exited today in my server with this error in cache.log
2012/10/09 11:18:27| assertion failed: disk.cc:374: "fd >= 0"
squid3 -v
Squid Cache: Version 3.2.1
configure options: '--build=x86_64-linux-gnu' '--prefix=/usr'
'--includedir=${prefix}/include' '--mandir=${prefix}/s
Hi,
I am running Squid Object Cache: Version 3.1.20 and getting the following
error in cache.log.
assertion failed: cbdata.cc:422: "c->locks < 65535"
After this squid restarts and everything works fine.
Regards,
Sunil
Hi,
I have tried squid-3.2.0.17-20120611-r11586 and it still crash shortly
after starting.
So looking through the chnagelog for 3.2.0.17, the most likely culprit
seemed squid-3.2-11549.patch:
http://www.squid-cache.org/Versions/v3/3.2/changesets/squid-3.2-11549.patch
So I reversed that patch an
Hi,
When upgrading from 3.2.0.16 to 3.2.0.17 I ran into this:
2012/06/06 12:19:56 kid1| assertion failed: cbdata.cc:130: "cookie ==
((long)this ^ Cookie)"
I have also tried squid-3.2.0.17-20120527-r11561, but see the same problem.
I'll include my squid.conf, a piece of cache.log and the backtrac
az"
> À: squid-users@squid-cache.org
> Envoyé: Jeudi 12 Janvier 2012 11:48:08
> Objet: [squid-users] assertion failed: comm.cc:1255: "isOpen(fd)" when
> shutting down squid 3.2 snapshot
>
> Hi,
> excerpt from cache.log when running /usr/local/squid/sbin/squid -k
&
> Objet: [squid-users] Assertion failed error causing worker process to restart
>
> Hi,
> Running squid 3.2 snapshot starting up with -SYC and seeing
>
> 2012/01/12 16:06:30 kid8| Beginning Validation Procedure
> 2012/01/12 16:06:30 kid8| UFSSwapDir::doubleCheck: MISSING S
Hi,
Running squid 3.2 snapshot starting up with -SYC and seeing
2012/01/12 16:06:30 kid8| Beginning Validation Procedure
2012/01/12 16:06:30 kid8| UFSSwapDir::doubleCheck: MISSING SWAP FILE
2012/01/12 16:06:30 kid8| UFSSwapDir::dumpEntry: FILENO 0053D933
2012/01/12 16:06:30 kid8| UFSSwapDir::dum
Hi,
excerpt from cache.log when running /usr/local/squid/sbin/squid -k
shutdown
2012/01/12 10:45:59 kid7| Open FD READ/WRITE 82 apps.facebook.com:443
2012/01/12 10:45:59 kid7| Open FD READ/WRITE 83 apps.facebook.com:443
2012/01/12 10:45:59 kid7| Open FD READ/WRITE 84
http://s0.2mdn.net/
When I run my Kerberos polygraph patch against 3.2 trunk with
negotiate_kerberos_auth I get the following error:
2011/03/18 00:07:21 kid1| assertion failed: User.cc:103:
"from->RefCountCount() == 2"
Markus
On 11/02/11 01:57, Alex Sharaz wrote:
Hi,
Looking for hints as to how to resolve the above problem.
Occasionally I get
2011/02/10 09:25:42| assertion failed: htcp.cc:1350: "sz >= 0"
2011/02/10 09:25:52| Starting Squid Cache version 3.1.11 for
x86_64-unknown-linux-gnu...
Messages appearing in
Hi,
Looking for hints as to how to resolve the above problem.
Occasionally I get
2011/02/10 09:25:42| assertion failed: htcp.cc:1350: "sz >= 0"
2011/02/10 09:25:52| Starting Squid Cache version 3.1.11 for x86_64-
unknown-linux-gnu...
Messages appearing in my cache.log.
The server in questio
tor 2011-01-13 klockan 15:38 +0300 skrev Hasanen AL-Bana:
> Hi,
>
> I am getting these every few minutes causing squid process to restart
>
> 2011/01/08 17:30:20| assertion failed: coss/store_dir_coss.c:276:
> "curstripe == storeCossFilenoToStripe(cs, e->swap_filen)"
This is a bug.
A guess is t
> You are out on/past the edges of known configurations there already.
To boldly configure what nobody configured before: This is the mission
of Capt. Al-Bana :)
Hi Amos,
I already have other aufs disks in my configuration :
here is my full cache_dir config file : (i have cache_dir(s) is a
separate config file)
cache_dir coss /mnt/cachedisk1/coss/store1 5 max-size=100
maxfullbufs=4 membufs=20 block-size=4096
cache_dir coss /mnt/cachedisk1/coss/st
On 14/01/11 01:38, Hasanen AL-Bana wrote:
Hi,
I am getting these every few minutes causing squid process to restart
2011/01/08 17:30:20| assertion failed: coss/store_dir_coss.c:276:
"curstripe == storeCossFilenoToStripe(cs, e->swap_filen)"
2011/01/08 17:36:44| assertion failed: coss/store_dir_c
Hi,
I am getting these every few minutes causing squid process to restart
2011/01/08 17:30:20| assertion failed: coss/store_dir_coss.c:276:
"curstripe == storeCossFilenoToStripe(cs, e->swap_filen)"
2011/01/08 17:36:44| assertion failed: coss/store_dir_coss.c:276:
"curstripe == storeCossFilenoToSt
> -Original Message-
> From: Amos Jeffries
> To: Squid Users
> Subject: Re: [squid-users] assertion failed: forward.c:109
> Date: Thu, 18 Feb 2010 10:45:48 +1300
>
> On Wed, 17 Feb 2010 13:07:25 +0200, Thomas
> wrote:
>> Hi!
>>
>> I recent
tor 2010-02-18 klockan 00:41 +0200 skrev Thomas:
> Did I really post such a stupid question to receive such a sarcastic
> answer?
Was it? Quite a lot of bugs gets fixed in 1.5 years and no one keeps
track of them all. Memory of past bugs tends to fade after some months
at most, and as a result non
Did I really post such a stupid question to receive such a sarcastic
answer?
Thanks anyway.
Regards
Thomas
-Original Message-
From: Amos Jeffries
To: Squid Users
Subject: Re: [squid-users] assertion failed: forward.c:109
Date: Thu, 18 Feb 2010 10:45:48 +1300
On Wed, 17 Feb 2010 13
On Wed, 17 Feb 2010 13:07:25 +0200, Thomas
wrote:
> Hi!
>
> I recently installed Squid 2.7 Stable3 on a Ubuntu 8.10 Server (64-bit)
> box. However, since about two weeks ago, the following error started
> showing up (and it seems to appear more frequently now):
>
> 2010/02/17 12:06:14| squidaio_
Hi!
I recently installed Squid 2.7 Stable3 on a Ubuntu 8.10 Server (64-bit)
box. However, since about two weeks ago, the following error started
showing up (and it seems to appear more frequently now):
2010/02/17 12:06:14| squidaio_queue_request: WARNING - Queue congestion
2010/02/17 12:07:49| cl
Squid keeps restarting.
as soon as the store rebuilds,... squid reboots. Do i need to zip the
cache and starts clean ?
2009/10/16 09:17:14| assertion failed: store_swapout.cc:317: "mem-
>swapout.sio == self"
2009/10/16 09:17:19| Starting Squid Cache version 3.0.STABLE19 for
i686-apple-dar
Hello all.
I have a squid 3.0-15 running on a FreeBSD 7.1/64, with a average of
50 request/second.
Its running on a Dell PowerEdge 1950, with 8G/RAM - 2Xeon / 4cores - 2.3Ghz.
After a few hours in production the squid reload, with theses messages
in cachelog.
Bellow is a backtrace.
Anybody kno
Dear users,
I compiled squid 2.7S6 with following options
'--prefix=/usr/local/squid' '--enable-async-io'
'--enable-removal-policies=lru,heap' '--disable-delay-pools'
'--disable-wccp' '--enable-kill-parent-hack' '--enable-snmp'
'--enable-err-languages=English' '--enable-linux-netfilter'
'--disabl
File a bug report, preferably with a stack backtrace.
Regards
Henrik
lör 2008-11-29 klockan 03:24 +0200 skrev Marcel Grandemange:
> Looks like squid broke itself again.
> If anybody could advise me as to what's happening here it would be great.
>
> Im thinking the move to v3 has been disasterous
Does Squid-2.7.STABLE5 exhibit this issue?
Adrian
2008/11/28 Marcel Grandemange <[EMAIL PROTECTED]>:
> Looks like squid broke itself again.
> If anybody could advise me as to what's happening here it would be great.
>
> Im thinking the move to v3 has been disasterous so far.
>
> Every time is
Looks like squid broke itself again.
If anybody could advise me as to what's happening here it would be great.
Im thinking the move to v3 has been disasterous so far.
Every time is now use our main proxy the following happens..
2008/11/29 03:10:19| Validated 1285147 Entries
2008/11/29 03:10:19
Hi,
Friday, November 7, 2008, 9:48:16 PM, you wrote:
> File a bug report, preferably with a stack backtrace of the error.
Hm, since we use aufs cache_dir type, we cannot provide a stack
backtrace... :(
Dietmar
--
NetCologne Gesellschaft fuer Telekommunikation mbH
Am Coloneum 9, 50829 Koeln
Ges
On fre, 2008-11-07 at 13:40 +0100, Dietmar Braun wrote:
> we are using Squid 3.0 STABLE9. Once a day, we get a
>
> 2008/11/06 22:28:07| assertion failed: store_client.cc:430:
> "STORE_DISK_CLIENT == getType()"
>
> with a restart of Squid. Is this a known bug, can we do anything here?
File a bu
Hi,
we are using Squid 3.0 STABLE9. Once a day, we get a
2008/11/06 22:28:07| assertion failed: store_client.cc:430: "STORE_DISK_CLIENT
== getType()"
with a restart of Squid. Is this a known bug, can we do anything here?
Thanks,
Dietmar
--
NetCologne Gesellschaft fuer Telekommunikation mbH
A
Thursday, September 18, 2008, 2:27:58 PM, you wrote:
> Pretty much. I've just applied the patch to 3.0 codebase, so it will be
> out in the next snapshot, or the patch is listed at:
>http://www.squid-cache.org/Versions/v3/3.0/changesets/
cool, thank you. Just applied it and it seems to work fi
Dietmar Braun wrote:
Hi,
Wednesday, September 17, 2008, 5:28:45 PM, you wrote:
This is a known bug:
http://www.squid-cache.org/bugs/show_bug.cgi?id=2391
Thank you for the quick reply.
I have not investigated it myself, but the recommendation in the bug
report is to remove the assertion as i
Hi,
Wednesday, September 17, 2008, 5:28:45 PM, you wrote:
> This is a known bug:
> http://www.squid-cache.org/bugs/show_bug.cgi?id=2391
Thank you for the quick reply.
> I have not investigated it myself, but the recommendation in the bug
> report is to remove the assertion as it is incorrect.
D
On Wed, 2008-09-17 at 16:00 +0200, Dietmar Braun wrote:
> Hi,
>
> we were using Squid 3.0 STABLE8, now STABLE9. In both, we are
> experiencing squid dying with the following debug message:
>
> 2008/09/17 14:21:53| assertion failed: forward.cc:1209: "(fs->code ==
> HIER_DIRECT) == !fs->_peer"
> 2
Hi,
we were using Squid 3.0 STABLE8, now STABLE9. In both, we are
experiencing squid dying with the following debug message:
2008/09/17 14:21:53| assertion failed: forward.cc:1209: "(fs->code ==
HIER_DIRECT) == !fs->_peer"
2008/09/17 14:21:56| Squid is already running! Process ID 11415
2008/09/
On fre, 2008-08-01 at 15:56 +0900, hideck wrote:
> 2008/08/01 15:18:04| assertion failed: disk.cc:242: "fdd->write_q->len
> > fdd->write_q->buf_offset"
> 2008/08/01 15:18:07| Starting Squid Cache version 3.0.STABLE7 for
> i686-redhat-linux-gnu...
>
> I am using coss with squid3.0 STABLE7 on the R
Hi,
My squid box was restarted with following message in cache.log.
2008/08/01 15:18:04| assertion failed: disk.cc:242: "fdd->write_q->len
> fdd->write_q->buf_offset"
2008/08/01 15:18:07| Starting Squid Cache version 3.0.STABLE7 for
i686-redhat-linux-gnu...
I am using coss with squid3.0 STABLE7
Dear Henrik,
Thank you very much for your response.
I haven't try with 2.7-ST2. But now I will.
Regards,
Pritam
Henrik Nordstrom wrote:
Do you see the same with 2.7.STABLE2?
There is a suspicion one of the changes in 2.7.STABLE3 is causing
this... but nothing confirmed yet.
Regards
Henr
On mån, 2008-07-14 at 20:04 +0545, pritam wrote:
> Hi All,
>
> Knowing that it is a bug ( ..? ) I need yours help here.
>
> My squid is getting restarted often (2, 3 times a day) with following
> messages:
>
> 2008/07/14 07:56:47| assertion failed: store_client.c:172:
> "!EBIT_TEST(e->flags, E
Hi All,
Knowing that it is a bug ( ..? ) I need yours help here.
My squid is getting restarted often (2, 3 times a day) with following
messages:
2008/07/14 07:56:47| assertion failed: store_client.c:172:
"!EBIT_TEST(e->flags, ENTRY_ABORTED)"
2008/07/14 17:18:17| assertion failed: forward.c:1
I get this one too, sorry do not have a coredump of it though.
Henrik Nordstrom wrote:
On fre, 2008-07-11 at 00:27 +0545, Pritam wrote:
Hi,
My squid box was restarted with following message in cache.log.
httpReadReply: Excess data from "HEAD
http://dl_dir.qq.com/qqfile/ims/qqdoctor/tsfsca
On fre, 2008-07-11 at 00:27 +0545, Pritam wrote:
> Hi,
>
> My squid box was restarted with following message in cache.log.
>
> httpReadReply: Excess data from "HEAD
> http://dl_dir.qq.com/qqfile/ims/qqdoctor/tsfscan.dat";
> assertion failed: forward.c:109: "!EBIT_TEST(e->flags, ENTRY_FWD_HDR_WAI
Hi,
My squid box was restarted with following message in cache.log.
httpReadReply: Excess data from "HEAD
http://dl_dir.qq.com/qqfile/ims/qqdoctor/tsfscan.dat";
assertion failed: forward.c:109: "!EBIT_TEST(e->flags, ENTRY_FWD_HDR_WAIT)"
Starting Squid Cache version 2.7.STABLE3 for i686-pc-linu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Henrik,
On Thu, 06 Sep 2007 10:21:34 +0200
Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> On tor, 2007-09-06 at 13:55 +0545, Tek Bahadur Limbu wrote:
>
> > > 2.6.STABLE16 is out.
> > >
> > > Also there has been a patch available for this problem
On tor, 2007-09-06 at 13:55 +0545, Tek Bahadur Limbu wrote:
> > 2.6.STABLE16 is out.
> >
> > Also there has been a patch available for this problem the whole week..
> > http://www.squid-cache.org/Versions/v2/2.6/changesets/11635.patch
>
> Thanks for the patch. I will apply the patch later today.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Henrik,
On Thu, 06 Sep 2007 01:42:12 +0200
Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> On tis, 2007-09-04 at 18:49 +0545, Tek Bahadur Limbu wrote:
> > Adrian Chadd wrote:
> > > On Tue, Sep 04, 2007, Tek Bahadur Limbu wrote:
> > >> -BEGIN PGP
On tis, 2007-09-04 at 18:49 +0545, Tek Bahadur Limbu wrote:
> Adrian Chadd wrote:
> > On Tue, Sep 04, 2007, Tek Bahadur Limbu wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> Hi All,
> >>
> >> I recently upgraded from Squid-2.6.STABLE12 to Squid-2.6.STABLE15 on a
> >> FreeB
Adrian Chadd wrote:
On Tue, Sep 04, 2007, Tek Bahadur Limbu wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I recently upgraded from Squid-2.6.STABLE12 to Squid-2.6.STABLE15 on a
FreeBSD-6.1 amd64 machine. I am using the Diskd storage system.
The title says it all:
http://squi
On Tue, Sep 04, 2007, Tek Bahadur Limbu wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi All,
>
> I recently upgraded from Squid-2.6.STABLE12 to Squid-2.6.STABLE15 on a
> FreeBSD-6.1 amd64 machine. I am using the Diskd storage system.
The title says it all:
http://squidproxy.wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I recently upgraded from Squid-2.6.STABLE12 to Squid-2.6.STABLE15 on a
FreeBSD-6.1 amd64 machine. I am using the Diskd storage system.
I seem be to getting the following error causing Squid to crash and restart
itself.
2007/09/04 15:24:28|
mån 2007-05-21 klockan 12:05 +0800 skrev Yoseph Basri:
> Hi,
>
> My squid box got restart after receive assertion failed: forward.c:
>
> 2007/05/20 09:48:51| assertion failed: forward.c:742: "fd ==
> fwdState->server_fd"
> 2007/05/20 09:49:01| Starting Squid Cache version 2.5.STABLE14 for
> i686
Hi,
My squid box got restart after receive assertion failed: forward.c:
2007/05/20 09:48:51| assertion failed: forward.c:742: "fd ==
fwdState->server_fd"
2007/05/20 09:49:01| Starting Squid Cache version 2.5.STABLE14 for
i686-pc-linux-gnu...
2007/05/20 09:49:01| Process ID 18979
2007/05/20 09:4
On Thu, Feb 08, 2007, admin wrote:
> Our newly installed moderately loaded Squid 2.6+diskd has restarted
> itself twice for the last day with the same error message in cache.log:
Hiya,
Please submit a bug report through bugzilla.
In the meanwhile - FreeBSD's libthr should work fine with aufs; giv
Our newly installed moderately loaded Squid 2.6+diskd has restarted
itself twice for the last day with the same error message in cache.log:
assertion failed: diskd/store_io_diskd.c:384:
"!diskdstate->flags.close_request"
OS FreeBSD 6.2
Squid 2.6.STABLE9 + diskd'd cache_dir
Some random bits from
]
Sent: Tuesday, July 25, 2006 7:47 PM
To: Hamed Adel
Cc: squid-users@squid-cache.org
Subject: Re: [squid-users] assertion failed
tis 2006-07-25 klockan 10:33 +0300 skrev Hamed Adel:
> The errors:
> - assertion failed: client_side.c:2485: "i->prefix_size > 0"
The above is bu
tis 2006-07-25 klockan 10:33 +0300 skrev Hamed Adel:
> The errors:
> - assertion failed: client_side.c:2485: "i->prefix_size > 0"
The above is bug #1670
> - assertion failed: http.c:1182: "strstr(url, strBuf(request->urlpath))"
And this is bug #1660
Both will be fixed in the upcoming 2.6.STAB
Dear all
I run a new transparent proxy with WCCP v.2 and squid 2.6 and it run work
good but squid is restart always and when I checked the cache log I found
one of these two errors appear every time before the service start please
could any one inform me with the cause of this problem.
The errors
ons 2006-05-31 klockan 17:10 +0300 skrev Eugene:
> I've upgraded squid to stable14 yesterday and today it
> periodically dies with message in cache.log:
>
> 2006/05/31 09:08:17| assertion failed: HttpReply.c:105: "rep"
Please get a stack trace and file a bug report.
http://www.squid-cache.org
I've upgraded squid to stable14 yesterday and today it
periodically dies with message in cache.log:
2006/05/31 09:08:17| assertion failed: HttpReply.c:105: "rep"
2006/05/31 10:23:55| assertion failed: HttpReply.c:105: "rep"
2006/05/31 10:37:21| assertion failed: HttpReply.c:105: "rep"
2006/05/31 1
I've upgraded squid to stable14 yesterday and today it
periodically dies with message in cache.log:
2006/05/31 09:08:17| assertion failed: HttpReply.c:105: "rep"
--
Best regards,
Eugene mailto:[EMAIL PROTECTED]
> Hi,
>
> I'm new to this list, so first, hello there!
>
> I'm running with squid 3.0-PRE3-20060313 on a x86_64 arch and I often
> see the following message in my syslog:
>
> squid[11404]: assertion failed: ClientBody.cc:44: "conn-
> >body_size_left > 0"
> squid[10133]: Squid Parent: child proces
Hi,
I'm new to this list, so first, hello there!
I'm running with squid 3.0-PRE3-20060313 on a x86_64 arch and I often
see the following message in my syslog:
squid[11404]: assertion failed: ClientBody.cc:44: "conn-
>body_size_left > 0"
squid[10133]: Squid Parent: child process 11404 exite
On Wed, 1 Feb 2006, H wrote:
Hi another funny crash:
Feb 1 20:37:43 wco-val kernel: pid 2923 (squid), uid 1004: exited on signal 6
Feb 1 20:37:43 wco-val squid[2923]: assertion failed:
diskd/store_dir_diskd.c:868: "rb->flags.need_to_validate"
Internal error in Squid. File a bug report as pe
On Thursday 02 February 2006 05:23, Mark Elsen wrote:
> > o sorry forgot to mention
> > any 12 and higher up to latest daily release
> >
> > H.
>
> Make sure that none of your logfiles and or
> swap.state are over 2Gig (?)
>
\
this error appearently has to do with the swapfile age
I still had
On Thursday 02 February 2006 09:33, Edinilson J. Santos wrote:
> After migrate from Freebsd 4.8+Squid 2.5 Stable4 to Freebsd 6.0+Stable12 we
> are having the same problem here with DISKD (+- 45 minutos online and crash
> with the same error as described).
Hi
are you sure that it is diskd.c:868
y
-
ATINET-Professional Web Hosting
Tel Voz: (0xx11) 4412-0876
http://www.atinet.com.br
- Original Message -
From: "H" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, February 01, 2006 9:36 PM
Subject: [squid-users] assertion failed: diskd/s
>
> o sorry forgot to mention
> any 12 and higher up to latest daily release
>
> H.
>
Make sure that none of your logfiles and or
swap.state are over 2Gig (?)
M.
On Thursday 02 February 2006 05:07, you wrote:
> > Hi another funny crash:
> >
> > Feb 1 20:37:43 wco-val kernel: pid 2923 (squid), uid 1004: exited on
> > signal 6 Feb 1 20:37:43 wco-val squid[2923]: assertion failed:
> > diskd/store_dir_diskd.c:868: "rb->flags.need_to_validate"
>
> This is a f
1 - 100 of 160 matches
Mail list logo
