fre 2007-01-19 klockan 18:02 -0500 skrev Nguyen, Khanh, INFOT:
> In cache.log has some queue congestion prior to SO_FAIL appearance and
> during SO_FAIL appearance:
>
> 2007/01/18 14:08:27| squidaio_queue_request: WARNING - Queue congestion
No other warnings?
> Should I try to lower the thread
[mailto:[EMAIL PROTECTED]
Sent: Friday, January 19, 2007 5:11 PM
To: Nguyen, Khanh, INFOT
Cc: squid-users@squid-cache.org
Subject: Re: [squid-users] SO_FAIL in store_log under high load
fre 2007-01-19 klockan 16:45 -0500 skrev Nguyen, Khanh, INFOT:
> 1) what has caused the swap failure? Is it due
fre 2007-01-19 klockan 16:45 -0500 skrev Nguyen, Khanh, INFOT:
> 1) what has caused the swap failure? Is it due to async threads or disk
> failure?
Anything in cache.log?
> 2) what is the optimum thread value that should one choose when compile
> under async-io?
Depends a bit on the hardware. Y
>...
>...
> >`updist`/src/squid -v
>
> This returned STABLE7. Still good. But squid -v with out
> /src/ returns
> STABELE6
>
>
Well hard to say, but that simply means that the new binary,
didn't go to where it was supposed to be by make install.
As stated by others, make sure tha
On Wed, 9 Feb 2005, Brad Taylor wrote:
I tried to install 2.5STABLE7 but after doing .configure, make and make
install I run squid -v and still STABLE6. I checked to config.log file
and these look to be the only errors:
How did you install 2.5.STABLE6?
You need to install 2.5.STABLE7 in the exact
> - check whether squid was build ; should be in relative
>to your unpacked distribution root :
>
>`updist`/src/squid (so to speak)
This is there. So far so good.
>Check then for instance :
>
>`updist`/src/squid -v
This returned STABLE7. Still good. But squid -v with out /sr
>
> >> What is the best approach to upgrade to 2.5.STABLE7 from
> 2.5.STABLE6?
> I
> >> see info on how to apply patches but not a new STABLE release.
>
> >Just install the new version ontop of the old and restart Squid. Same
> as
> >when patching except that there is no doubt in what Squid
>> What is the best approach to upgrade to 2.5.STABLE7 from 2.5.STABLE6?
I
>> see info on how to apply patches but not a new STABLE release.
>Just install the new version ontop of the old and restart Squid. Same
as
>when patching except that there is no doubt in what Squid version you
are
>using
On Mon, 7 Feb 2005, Brad Taylor wrote:
What is the best approach to upgrade to 2.5.STABLE7 from 2.5.STABLE6? I
see info on how to apply patches but not a new STABLE release.
Just install the new version ontop of the old and restart Squid. Same as
when patching except that there is no doubt in wha
> You need to use the latest stable release (2.5.STABLE7) to avoid this
> issue.
What is the best approach to upgrade to 2.5.STABLE7 from 2.5.STABLE6? I
see info on how to apply patches but not a new STABLE release.
Is this really the only option? I can't fix STABLE7?
B
>
> I've searched the archives and looked in the definitive guide
> but can't
> find any solutions to SO_Fail -1 for all image files I see in my
> store.log file. I know that this means squid could not save
> the object
> to disk. I'm trying to just cache images but my access log is showing
On Thu, 19 Aug 2004, Glatzel Tino wrote:
Hello
Squid does not save internetfiles on the harddisk.
In the store.log, i see the following messages:
1092911664.677 SO_FAIL -1 AA5601EB2B243693AFEAFAEF68C230BF 200
1092911664 1092815319-1 text/html 15488/13312 GET
My system is a Debian
Hi
Can you give a brief copy and paste of the access.log
And too your conf file.
Kind Regards
Brent Clark
-Original Message-
From: Glatzel Tino [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 19, 2004 12:54 PM
To: '[EMAIL PROTECTED]'
Subject: [squid-users] SO_FAIL
Hello
Squid does
Quoting Henrik Nordstrom <[EMAIL PROTECTED]>:
>
> > Now this may be due to my misunderstanding of how "cache_replacement_policy heap
> > LFUDA" is supposed to work, but the comments in the config say this about it:
> >
> > # The heap LFUDA policy keeps popular objects in cache regardless of
Now this may be due to my misunderstanding of how "cache_replacement_policy heap
LFUDA" is supposed to work, but the comments in the config say this about it:
# The heap LFUDA policy keeps popular objects in cache regardless of
# their size and thus optimizes byte hit rate at the expen
Quoting [EMAIL PROTECTED]:
> Quoting Henrik Nordstrom <[EMAIL PROTECTED]>:
>
> > On Wed, 7 Jul 2004, Sunil Mohan Ranta wrote:
> >
> > >
> > > i am getting SO_FAIL messages in store.log
> > > and no cache is being created on my system
> > > the size of of cache_dir is constant at 17MB
> >
> > Any e
Quoting Henrik Nordstrom <[EMAIL PROTECTED]>:
> On Wed, 7 Jul 2004, Sunil Mohan Ranta wrote:
>
> >
> > i am getting SO_FAIL messages in store.log
> > and no cache is being created on my system
> > the size of of cache_dir is constant at 17MB
>
> Any error messages in cache.log?
>
> REgards
> Henri
On Wed, 7 Jul 2004, Sunil Mohan Ranta wrote:
>
> i am getting SO_FAIL messages in store.log
> and no cache is being created on my system
> the size of of cache_dir is constant at 17MB
Any error messages in cache.log?
REgards
Henrik
> actuall i had stable1 and it use to work fine.
> i upgrated to stable5, and got this problem
It seems that I have the same or a very similar problem:
No problems using squid-2.5.STABLE4-20040120 and before. Object are written
on disk and logged with SWAPOUT in store.log.
Using squid-2.5.STABLE
>
> problem details
>
> system : fc2
> squid : stable squid/2.5.STABLE5-20040629
> lots of free space,
>
> actuall i had stable1 and it use to work fine.
> i upgrated to stable5, and got this problem
>
> cache_dir is owned by squid:squid is has ug+rwx
>
> tail store.log
>
> 1089299522.640
help please no related links found in google
problem details
system : fc2
squid : stable squid/2.5.STABLE5-20040629
lots of free space,
actuall i had stable1 and it use to work fine.
i upgrated to stable5, and got this problem
cache_dir is owned by squid:squid is has ug+rwx
tail store.log
10892
>
>
> i am getting SO_FAIL messages in store.log
> and no cache is being created on my system
> the size of of cache_dir is constant at 17MB
>
- Check squid's cache.log for more info.
- Check your system logs too, watchout for system messages
concerning for instance disk space, disk I/O,
My first suggestion would be to look at the permissions of the cache
directory.
Does the squid user have write permissions to it?
Regards,
Tim Rainier
"Sunil Mohan Ranta" <[EMAIL PROTECTED]>
07/07/2004 02:20 PM
To: [EMAIL PROTECTED]
cc:
Subject:[squid
23 matches
Mail list logo