From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 Description of problem: When upgrading to bind-9.2.4-EL3_10 via up2date, the chroot'ed environment doesn't upgrade correctly. In the aftermath, /etc/sysconfig/network needs to be fixed, as well as /var/named/chroot/etc/*. Also, the init script's named-checkconf line doesn't look for the named.conf in the chrooted environment. Version-Release number of selected component (if applicable): Upgrade to bind-9.2.4-EL3_10 How reproducible: Always Steps to Reproduce: 1. Update bind via up2date (possibly via 'rpm -U' command-line as well) 2. Watch the init script complain of a missing "/etc/named.conf" script and fail to start the named service. 3. Actual Results: Named didn't start at all Expected Results: Named would start in a chroot'ed environment Additional info:
Yes, sorry - this bug has been found before: bug #131803 . The problem was with the bind-chroot-9.2.2-21 %postun script, which removes these files under the chroot during upgrade: etc/named.conf, etc/rndc.key, and some dev/ files. The fix is to restore your named.conf (which should be saved as named.conf.rpmsave) and rndc key, and then upgrade to the fix for RHEL-3-U3, which will be in RHEL-3-U4, but which meanwhile is at: http://people.redhat.com/jvdias/bind/RHEL-3/9.2.4rc7-12_EL3 *** This bug has been marked as a duplicate of 131803 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.