+++ This bug was initially created as a clone of Bug #553334 +++
Description of problem:
Same symptoms as 553334. Bind 9.3.6-4.P1 crashes under high load on occassion.
Restarting the bind instance affected fixes the problem.
I obtained the gdb output requested from the previous ticket. It is attached.
--- Additional comment from firstname.lastname@example.org on 2010-03-30 08:36:28 EDT ---
Would it be possible to install bind-debuginfo package and get backtrace from hanged named process, please?
- run "gdb attach <named_pid>"
- in the gdb prompt run "t a a bt full"
- attach output here
No attachment is here... please add it.
Created attachment 489258 [details]
gdb bt from crash
(In reply to comment #2)
> Created attachment 489258 [details]
> gdb bt from crash
I cannot figure why named stops responding from backtrace. Can you please obtain following logs as well?
1. When named stops to respond to queries, attach it via strace, perform a query (via dig for example) and then attach strace output here, please.
2. Obtain verbose logs - set named as written in https://bugzilla.redhat.com/show_bug.cgi?id=584356#c11 and then attach named.run* files.
Thank you in advance.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Since there was no response for needinfo for more than 18 months and RHEL 5 is now in production phase 2 (only important/critical bugs are fixed), I'm closing this bug. Please either upgrade to RHEL-6 or install bind97 package which shouldn't crash.