Also another chunk of the same starce.
read(797, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(1773, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(2892, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(3323, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(3524, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(4058, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(4780, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(4817, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(5303, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(5387, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(6732, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(7457, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(8442, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(8528, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(9518, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(9580, 0x7fff24519990, 65535) = -1 EAGAIN (Resource temporarily
unavailable)
read(8975, "usel-first-button{background-pos"..., 4096) = 4096
read(2033, "oto\"><a
title=\"\316\210\316\272\316\270\316\265\317\203\316\267
\316\223\316\265"..., 4096) = 4096
read(5797, 0xec8c27c0, 4095) = -1 EAGAIN (Resource temporarily
unavailable)
read(2084,
"3\0\00033\0\377\0003\0\314\0003\0\231\0003\0f\0003\0003\0003\0\0\0003\0\377
\377"..., 4096) = 4096
read(5391, "", 4095) = 0
read(5391, "", 65535) = 0
read(8287, 0x12cfd1730, 4095) = -1 EAGAIN (Resource temporarily
unavailable)
read(5280, 0x1076bfe20, 4095) = -1 EAGAIN (Resource temporarily
unavailable)
read(8858, 0x1300c6270, 4095) = -1 EAGAIN (Resource temporarily
unavailable)
read(8482, "GET /Files/1/Vignettes/footer_ti"..., 4095) = 673
read(5032, "GET /Themes/1/Default/Media/Layo"..., 4095) = 1035
read(1621, "GET /ajax.aspx?m=Articles.Articl"..., 4095) = 958
read(7480, "", 4095) = 0
read(7480, "", 65535) = 0
read(2533, 0x12846f410, 4095) = -1 EAGAIN (Resource temporarily
unavailable)
read(1207, "GET /banners/AdmleftUfin.html HT"..., 4095) = 533
read(4904, "GET /Themes/1/Default/Media/anti"..., 4095) = 406
read(8970, "GET /ast/img/otetv.gif HTTP/1.1\r"..., 4095) = 743
Is that normal?
Thanks for the help..
-----Original Message-----
From: karj [mailto:gkaragiannidis@xxxxxxxxx]
Sent: Τετάρτη, 29 Φεβρουαρίου 2012 3:40 μμ
To: 'Sebastian Muniz'; squid-users@xxxxxxxxxxxxxxx
Subject: RE: squid "stops working" several times a day
I 'm able to ping the machines
The one thing that I observed is that
by the time of crisis squid process is using 100% of the CPU.
That's happening to every server which has the problem...
I 've tried to use strace but I've got no success since the strace output is
huge.
What else can I do to identify the problem.?
At the time of problem seems from cache.log that squid loses connectivity
with almost everybidy
2012/02/29 09:15:51| TCP connection to assets_servers (xxx.xxx.xxx.xxx:80)
failed
2012/02/29 09:15:51| TCP connection to typos_servers (xxx.xxx.xxx.xxx:80)
failed
2012/02/29 09:15:51| Detected DEAD Parent: tityros_servers
2012/02/29 09:15:51| TCP connection to assets_servers (xxx.xxx.xxx.xxx:80)
failed
2012/02/29 09:15:51| TCP connection to tityros_servers (xxx.xxx.xxx.xxx:80)
failed
2012/02/29 09:15:51| TCP connection to typos_servers (xxx.xxx.xxx.xxx:80)
failed
>From another sibling log at the same time
2012/02/29 09:15:51| Detected DEAD Sibling: xxx.xxx.xxx.xxx
Thanks in advance
Yiannis
-----Original Message-----
From: Sebastian Muniz [mailto:basurerosebita@xxxxxxxxx]
Sent: Τρίτη, 28 Φεβρουαρίου 2012 11:52 μμ
To: squid-users@xxxxxxxxxxxxxxx
Subject: Re: squid "stops working" several times a day
On 2/28/2012 2:54 PM, karj wrote:
> Hi All,
> I have a problem with my squid's.
> Squid "stops working" several times a day.
> The only thing that warns me that something is wrong in cache.log is
> the "Detected DEAD Sibling: xxx.xx.xxx.xxx" message.
> After a few seconds everything goes back to normal.
> We are using 5 squids version (2.7.Stable 9) in Accelerator Mode which
> are sibling to each other.
> So we have 5 sibling squid in front of our web farms. Serving almost
> 7000/request per second at peak time, and an average of 4500/request
> per second.
> The problem occurs randomly in all servers...
Are you able to reach (telnet or ping or anything) the sibling during the
times that squid stops working?
What can you tell about the sibling logs? Specially the cache.log
Regards
Sebastian
