So here were the final instructions for getting a core file.
1. added ulimit -c unlimited to the init.d script.
2. installed debug squid rpm package.
3. echo 1 /proc/sys/kernel/core_uses_pid
4. echo /corefiles/core-%e-%p-%t /proc/sys/kernel/core_pattern
Now I have the file:
-rw--- 1
Here was the output from the traceback.
(gdb) backtrace
#0 0x7f9f063ff215 in raise () from /lib64/libc.so.6
#1 0x7f9f06400cc0 in abort () from /lib64/libc.so.6
#2 0x7f9f083fa9cf in death (sig=value optimized out) at tools.cc:402
#3 signal handler called
#4 0x7f9f06448f4c in
On Tue, Dec 22, 2009 at 8:54 PM, Dusten Splan dsp...@myyearbook.com wrote:
I'm seeing my squid processes die and restart. I think it's related
to a bad cache file but I am unsure how to track it down. I have
rebuilt the cache by removing the swap.state file and starting squid
back up.
So looking in my conf file I see that my core dumps are going to /tmp.
coredump_dir /tmp
but when looking in that location I do not see any core dumps. Are
there any other places I should be looking?
Dusten
On Wed, Dec 23, 2009 at 03:41, Kinkie gkin...@gmail.com wrote:
On Tue, Dec 22, 2009
I just noticed that my ulimit for core dumps was set to 0. I have
changed it to unlimited and I hope to see a core file on the next
crash.
Just as a note so if others have the same issue.
To see the ulimit settings
ulimit -a
To set the core limit
ulimit -c unlimited
Dusten
On Wed, Dec 23,
I'm seeing my squid processes die and restart. I think it's related
to a bad cache file but I am unsure how to track it down. I have
rebuilt the cache by removing the swap.state file and starting squid
back up.
Here's what I'm seeing in my logs.
2009/12/21 22:07:01| WARNING: 1 swapin MD5
