Account Links: Cart | Your Account | Logout

Skip to content

Red Hat Knowledgebase

Red Hat Knowledgebase Search:

Updated Within the Last:

New Solutions within the last day New Solutions within the last week New Solutions within the last month

Browse by topics:


Click to View a Topic
Red Hat Enterprise Linux > AS/ES/WS v. 4 > Issue <<  44 of 627 >>

Solution Tools:


Email a Solution Postcard Printer version Submit a comment on this answer Update notifications Request an answer Back

Article Reference

Article ID: 8622
Last update: 08-09-06
Issue:
When I update the bind nameserver package on my server, the service does not function properly and the bind-libs package version doesn't match the bind package version. What should I do?
Resolution:

This is a known issue which can occur when the bind package is updated using a command such as up2date bind or up2date -u bind. Currently the main bind nameserver package does not list the bind-libs package as an RPM dependency, so if a command such as up2date bind is executed, the bind and bind-libs package versions can become unsychronized and cause problems with the service functioning properly after the bind package update is completed.

This issue will be corrected in a future update of the bind packages.

This problem will not occur if the up2date command used either explicitly includes the bind-libs package on the command line, or a command such as up2date -u is used.

The command up2date -u will cause ALL packages that updates exist for in the Red Hat Network (RHN) channels a system is subscribed to be updated except packages which are named in the up2date utility's package skip list.

If the up2date utility has been configured to skip updating bind and bind related packages on the server, it will be necessary to add the -f option to the up2date command line to force the specified packages to be updated.

Solution:
If this situation has occurred, the best way to solve this problem is to explicitly update all bind related packages on the system. While it should only be necessary to explicitly update the bind-libs package, updating all existing bind packages on the system will ensure they are all the same version afterwards even if newer updated packages have been released to the channel again.

First, determine which bind related packages are currently installed on the system. Example output is provided below:


# rpm -qa | egrep "^bind"
bind-libs-9.2.4-7_EL3
bind-9.2.4-14_EL3
bind-utils-9.2.4-7_EL3

Then explicitly update these packages:

# up2date -f bind bind-libs bind-utils

Fetching Obsoletes list for channel: rhel-i386-as-3...

Fetching Obsoletes list for channel: rhel-i386-as-3-extras...

Fetching Obsoletes list for channel: rhel-i386-as-3-cluster...

Name                                    Version        Rel
----------------------------------------------------------
bind-libs                               9.2.4          14_EL3            i386
bind-utils                              9.2.4          14_EL3            i386


Testing package set / solving RPM inter-dependencies...
########################################
bind-libs-9.2.4-14_EL3.i386 ########################## Done.
bind-utils-9.2.4-14_EL3.i38 ########################## Done.
Preparing              ########################################### [100%]

Installing...
   1:bind-libs              ########################################### [100%]
   2:bind-utils             ########################################### [100%]
#

Bind should function properly afterwards.


How well did this entry answer your question?


good wrong incomplete out of date
Red Hat Enterprise Linux > AS/ES/WS v. 4 > Issue <<   44  of  627  >>