Bug 623122
| Summary: | can't stop bind | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Levente Farkas <lfarkas> | ||||
| Component: | bind | Assignee: | Adam Tkac <atkac> | ||||
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.0 | CC: | azelinka, mishu, mstevens, ovasik | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
under certain circumstances, "named" was entering a deadlock. Consequently, "named" could not be stopped using the "/etc/init.d/named stop". In this updated package, the deadlock no longer occurs, resolving this issue.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 643102 (view as bug list) | Environment: | |||||
| Last Closed: | 2011-05-19 12:58:13 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 672514 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Levente Farkas
2010-08-11 11:57:25 UTC
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** ok now bind simple unusable! we can't stop it and stop working randomly. imho it's a serious bug since it a basic service without it nothing is working! it's turn out to happened when i set forwarders in the config file. If I understand correctly when you don't set forwarders everything is OK? Would it be possible to check if it's something strange in the system log, please? Also try to disable DNSSEC validation (via `rndc validation off`, for example) and report if it helps, please. here is our named.conf. if you uncomment the the forward lines then it's happened on our firewall (with two interface external dhcp, internal static bridged network 10.30.0.1, plus 2 tun device for openvpn connection 10.20.0.1, 10.10.0.2)
-------------------------
acl internal {
10.30.0.0/24;
192.168.0.0;
10.20.0.1/24;
10.10.0.2/24;
};
acl dns {
127.0.0.1;
10.30.0.1;
192.168.208.1;
};
options {
listen-on port 53 {
127.0.0.1;
10.30.0.1;
10.20.0.1;
10.10.0.2;
};
// listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
// forward only;
// forwarders { 8.8.8.8; 8.8.4.4; };
// allow-query { internal; dns; };
// allow-transfer { dns; };
recursion yes;
dnssec-enable yes;
dnssec-validation yes;
dnssec-lookaside auto;
/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
zone "." IN {
type hint;
file "named.ca";
};
include "/etc/named.rfc1912.zones";
-------------------------
here comes a few local zones nothing else.
the truth is that i do not really like to play with this server as 10 people working at that office behind this firewall...
This is weird, I'm not able to reproduce this issue. Are you able to stop named via `rndc stop` command or via `kill -TERM <named_pid>`? Or the only way is to kill named via sigkill? the only way was a sigkill. We have exactly the same problem. If the named service is running more than a few hours, it's not possible to stop the named service. Exactly the same problem here and I also experience that RR are not updated so some services in the LAN that depend on it fail. This is a serious issue indeed! I've finally reproduced this issue and the solution is to replace patch called "bind97-rh576906.patch" by improved version, called "bind97-rh623122.patch". I will attach the improved patch. Created attachment 453503 [details]
Proposed patch
Replace bind97-rh576906.patch by this patch.
This seems to be solved now, I've not encountered this issue anymore on any of my systems. According to https://beaker.engineering.redhat.com/jobs/63067 - VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
it was impossible to stop named due deadlock in certain cases. Now it is possible.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-it was impossible to stop named due deadlock in certain cases. Now it is possible.+under certain circumstances, "named" was entering a deadlock. Consequently, "named" could not be stopped using the "/etc/init.d/named stop". In this updated package, the deadlock no longer occurs, resolving this issue.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0541.html |