One day later...
Well, we have two identical squid servers (load balancing with DNS).
The patched squid doesn't present this, anymore.
On the other hand, the other one, unpatched, hunged some minutes ago, and after launching, it
presented again this message (hanged, killed and restarted with
FredB wrote:
Perhaps you can try a killall squid ? Because I saw that there is no problem
with clean cache
Look at Comment 10 -> http://bugs.squid-cache.org/show_bug.cgi?id=3441
OK, I've done... It found a dirty cache and rebuild it.
But well. Let's let it run for some time. Either way,
>
> I removed just the patch 10394. After a half hour, no more messages
> and the proxy works without
> problem. Just as reference, before, I usually got something like
>
> I'm not sure that this appeared just after start up or not. I should
> probably let it run for some
> longer time (one or t
Amos Jeffries wrote:
3.1 narrows it down to probably just these two patches:
www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10394.patch
www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10403.patch
The top one being more likely. If you are able to patch and test with
those sepa
I'm doing it... First removing 10394. I'll post the results after test.
Amos Jeffries wrote:
On 17/01/2012 3:00 a.m., Amos Jeffries wrote:
On 17/01/2012 2:43 a.m., Jose-Marcio Martins da Cruz wrote:
Amos Jeffries wrote:
On 11/01/2012 11:44 p.m., Jose-Marcio Martins da Cruz wrote:
I had thi
On 17/01/2012 3:00 a.m., Amos Jeffries wrote:
On 17/01/2012 2:43 a.m., Jose-Marcio Martins da Cruz wrote:
Amos Jeffries wrote:
On 11/01/2012 11:44 p.m., Jose-Marcio Martins da Cruz wrote:
I had this too. But with a 3.1.18 in a production server (under
solaris).
Sure that was 3.1.18? that c
On 17/01/2012 2:43 a.m., Jose-Marcio Martins da Cruz wrote:
Amos Jeffries wrote:
On 11/01/2012 11:44 p.m., Jose-Marcio Martins da Cruz wrote:
I had this too. But with a 3.1.18 in a production server (under
solaris).
Sure that was 3.1.18? that could narrow the diagnosis down a lot if its
tru
Amos Jeffries wrote:
On 11/01/2012 11:44 p.m., Jose-Marcio Martins da Cruz wrote:
I had this too. But with a 3.1.18 in a production server (under solaris).
Sure that was 3.1.18? that could narrow the diagnosis down a lot if its
true.
Yes. It's on a 3.1.18 on a Solaris box.
Tell me if I can
On 11/01/2012 11:44 p.m., Jose-Marcio Martins da Cruz wrote:
I had this too. But with a 3.1.18 in a production server (under solaris).
Sure that was 3.1.18? that could narrow the diagnosis down a lot if its
true.
Amos
2012/01/10 10:11:54| WARNING: Disk space over limit: 1644356946 KB >
- Mail original -
> De: "Amos Jeffries"
> À: squid-users@squid-cache.org
> Envoyé: Mercredi 11 Janvier 2012 11:45:33
> Objet: Re: [squid-users] Silly warning about over disk limits
>
> On 11/01/2012 11:24 p.m., alex sharaz wrote:
> > Getting the
On 11/01/2012 11:24 p.m., alex sharaz wrote:
Getting the following on my 3.2...79 snapshot:-
2012/01/11 10:18:30 kid2| NETDB state saved; 142 entries, 135 msec
2012/01/11 10:18:39 kid1| WARNING: Disk space over limit:
5258011484356608.00 KB > 1048576 KB
2012/01/11 10:18:50 kid1| WARNING: Disk
I had this too. But with a 3.1.18 in a production server (under solaris).
2012/01/10 10:11:54| WARNING: Disk space over limit: 1644356946 KB > 5120 KB
Sometimes the server hands and it seems to me that these are related but I haven't yet enough data
to say anything. I was just waiting more
Getting the following on my 3.2...79 snapshot:-
2012/01/11 10:18:30 kid2| NETDB state saved; 142 entries, 135 msec
2012/01/11 10:18:39 kid1| WARNING: Disk space over limit:
5258011484356608.00 KB > 1048576 KB
2012/01/11 10:18:50 kid1| WARNING: Disk space over limit:
5258011484356608.00 KB >
13 matches
Mail list logo
