HI all,
I forgot I still have the issue in the subject bugging me too. Is the
below backtrace of any use or do I need to provide more?
Thanks
Alex
On 07/02/14 10:41, Alex Crow wrote:
Hi
Thanks for that - I did get a backtrace today...
Program terminated with signal 6, Aborted.
#0 0x00007fa89b3fb1b5 in raise () from /lib/libc.so.6
(gdb) backtrace
#0 0x00007fa89b3fb1b5 in raise () from /lib/libc.so.6
#1 0x00007fa89b3fdfc0 in abort () from /lib/libc.so.6
#2 0x00007fa89bc8fdc5 in __gnu_cxx::__verbose_terminate_handler() ()
from /usr/lib/libstdc++.so.6
#3 0x00007fa89bc8e166 in ?? () from /usr/lib/libstdc++.so.6
#4 0x00007fa89bc8e193 in std::terminate() () from
/usr/lib/libstdc++.so.6
#5 0x00007fa89bc8e216 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#6 0x00000000005d457c in SquidMainSafe (argc=<value optimized out>,
argv=<value optimized out>) at main.cc:1246
#7 main (argc=<value optimized out>, argv=<value optimized out>) at
main.cc:1234
Thanks
Alex
Hi,
Is this of any help?
Also I've had to go back to 3.2.11 as 3.4.x is still using way too
much CPU, I get users (about 350) complaining about extreme slowness
by lunchtime, and squid is using >90% CPU. In 3.2.11 it's always
around 15%.
Request are fairly low:
Average HTTP requests per minute since start: 2647.4
Cheers
Alex
