RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 853714 - DNS Server (bind) sometimes hang .......
Summary: DNS Server (bind) sometimes hang .......
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bind
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Tomáš Hozza
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-02 11:06 UTC by davidyangyi
Modified: 2023-09-14 01:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-04 13:38:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description davidyangyi 2012-09-02 11:06:30 UTC 
Description of problem:

DNS Server (bind) sometimes hang wich errors:

# service named status
rndc: connect failed: 127.0.0.1#953: connection refused
named (pid  20043) running...

Clients cannot resolve hostname. no response.
and I cannot stop it with "service named stop". I must kill -9 and start again. and become normal.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Adam Tkac 2012-09-05 11:39:32 UTC 
(In reply to comment #0)
> Description of problem:
> 
> DNS Server (bind) sometimes hang wich errors:
> 
> # service named status
> rndc: connect failed: 127.0.0.1#953: connection refused
> named (pid  20043) running...
> 
> Clients cannot resolve hostname. no response.
> and I cannot stop it with "service named stop". I must kill -9 and start
> again. and become normal.

Can you please attach more information?

1. attach your /var/log/messages when your named hangs to bugzilla
2. install bind-debuginfo
3. attach named process with gdb (gdb attach <named_pid>)
4. in gdb run "t a a bt full" and attach output

You can attach both outputs as "private attachment" if it contains private data. They will be invisible for other users.

Thank you in advance!
Comment 5 RHEL Program Management 2013-10-14 00:29:23 UTC 
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 unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 6 Tomáš Hozza 2014-03-04 13:38:54 UTC 
Due to lack of response and too little information to investigate this Bug,
I'm closing it as INSUFFICIENT_DATA.

If you run into the same situation in the future, feel free to reopen it and
please provide additional information using steps described in comment #2.

Thank you.
Comment 7 Red Hat Bugzilla 2023-09-14 01:37:01 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.