Maybe I missed something but:
Is there any bug report in the bugzilla?
It is better tracked this way.
What was the original issue? CPU SPIKES? how many users?
Not related to hardware issues but what are the specs of the machine?
Why 3.1.19? have you considered that one cpu cannot take the load by any
chance?
Eliezer
On 03/27/2014 03:55 PM, a.afach@xxxxxxxxxxxxx wrote:
Dear Amos
returning to our problem CPU Spikes on squid 3.1.19 or 2.7.9 i see this
bug in gdb
while ((t_off + p.len) < offset)
and other while loops like ( while L ) and hanging
and some errors like : 0x00007f4e932c8103 in epoll_wait () from
/lib64/libc.so.6
this errors rises CPU to 100% for random time and comes down back to the
normal value
i dont think there is a hardware issue because the problem occurs in any
time even when squid is not loaded
as a notice i have 4 servers one of them is having such problem . the
only difference that the server with the issue has new kernel
Linux proxy4 3.10.25-gentoo SMP
gcc version 4.5.4 (Gentoo 4.5.4 p1.2, pie-0.4.7)
while the other servers have
Linux proxy91 3.4.9-gentoo
gcc version 4.5.4 (Gentoo 4.5.4 p1.0, pie-0.4.7)
i had compile errors on proxy 4 for squid 3.1 so i added this to configure
CC=x86_64-pc-linux-gnu-gcc CFLAGS=-O2 -pipe -m64 -mtune=generic
LDFLAGS=-Wl,-O1 -Wl,--as-needed CXXFLAGS= --cache-file=/dev/null --srcdir=.
does these cause these C loops
Thanks Amos
