Red Hat Magazine

Tips and tricks: Failed dependencies

the editorial team — Thu, 07 Aug 2008 21:48:59 +0000

Question: I am trying to install a third-party application on my Red Hat Enterprise Linux system but I am getting failed dependencies error messages. I know that these dependencies are native to Red Hat Enterprise Linux but I do not know which package they belong to. How do I use my up2date agent to resolve these dependencies?

Answer: I am getting similar error messages regarding module dependencies when trying to install a third-party rpm package:

error: failed dependencies:
      libcap.so    is needed by VMware
      libcap.so.1  is needed by VMware
      libcap.so.1.10  is needed by vsftpd

If these module dependencies do exist in any of the packages in Red Hat Enterprise Linux, the following command to automatically resolve these dependencies and install the appropriate packages on your system.

up2date  --solvedeps=

Red Hat’s customer service and support teams receive technical support questions from users all over the world. Red Hat technicians add the questions and answers to Red Hat Knowledgebase on a daily basis. Access to Red Hat Knowledgebase is free. Red Hat Magazine offers a preview into the Red Hat Knowledgebase by highlighting some of the most recent entries. The information provided in this article is for your information only. The origin of this information may be internal or external to Red Hat. While Red Hat attempts to verify the validity of this information before it is posted, Red Hat makes no express or implied claims to its validity.

Tips and tricks: I am behind a firewall and can not connect to Red Hat Network (RHN). Is there an FTP site to get the Red Hat Enterprise Linux RPM’s from?

the editorial team — Mon, 04 Aug 2008 23:06:01 +0000

Unfortunately, there is no FTP server available to obtain updates from Red Hat Network (RHN). You can only get Red Hat Enterprise Linux RPM’s from RHN using up2date or by downloading the RPM’s from https://rhn.redhat.com/.

Alternatively, you can open your firewall to allow access for TCP/UDP connections on port 443 or you can look at purchasing RHN Proxy Server or RHN Satellite Server.

Note: Red Hat Enterprise Linux source RPMs are available from ftp.redhat.com.

Tips and tricks: Is there a way to transfer my subscription from one RHN account to another?

the editorial team — Fri, 01 Aug 2008 22:17:14 +0000

Customer entitlements and subscriptions (for Red Hat® Enterprise Linux® or other applications) can be transferred from one Red Hat Network (RHN) account to another by our Customer Service team. However, system profiles and associated Red Hat Network web login accounts cannot be transferred.

In order to transfer a system profile, the following must happen:

the entitlement for the system must first be transferred by Customer Service
the user must delete the system profile from the old account
the user must re-register the system with the desired account for updates

Please contact Customer Service with your desired RHN account information and entitlement transfer request. The request must originate from the email address registered on the original account and must cc the email address listed on the account where you wish to transfer your entitlements.

Tips and tricks: What are the options available in kickstart for controlling the behaviour of SELinux?

the editorial team — Mon, 28 Jul 2008 20:32:15 +0000

Release Found: Red Hat® Enterprise Linux® 4
The following options can be used in the kickstart configuration file to control SELinux behaviour in a kickstart installation.

1. selinux –enforcing: Enables SELinux with the default targeted policy being enforced.

2. selinux –permissive: Outputs warnings only based on the SELinux policy, but does not actually enforce the policy.

3. selinux –disabled: Disables SELinux completely on the system.

If any SELinux option is not present in the kickstart file then SELinux is enabled by default and set to –enforcing.

Note: The system-config-securitylevel-tui package is required for controlling the SELinux policies. If this package is removed from the kickstart configuration file, SELinux will set to –enforcing mode by default irrespective of the SELinux options.

It should be noted that Red Hat does not recommend disabling SELinux.

Tips and tricks: Why do I receive an error after updating to Red Hat Enterprise 3 update 4 using up2date?

the editorial team — Tue, 22 Jul 2008 00:37:04 +0000

Release Found: Red Hat® Enterprise Linux® 3, Update 4

Symptom:
After doing a complete update to Red Hat Enterprise Linux 3 Update 4, any further attempts to run up2date result in the following error:

# up2date --dry-run
Traceback (most recent call last):
  File "/usr/sbin/up2date", line 1174, in ?
    sys.exit(main() or 0)
  File "/usr/sbin/up2date", line 668, in main
    up2dateAuth.updateLoginInfo()
  File "up2dateAuth.py", line 151, in updateLoginInfo
  File "up2dateAuth.py", line 105, in login
  File "up2dateAuth.py", line 49, in maybeUpdateVersion
  File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 228,
    in getVersion
    release, version = getOSVersionAndRelease()
  File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 221,
    in getOSVersionAndRelease
    raise up2dateErrors.RpmError(
up2date_client.up2dateErrors.RpmError: RPM error.  The message was:
Could not determine what version of Red Hat Linux you are running.
If you get this error, try running 

                rpm --rebuilddb

Solution:

Additional articles in the Red Hat Knowledgebase provide information on how to remove the locks from the RPM database.

You will need to either download the redhat-release package for your system from Red Hat Network (RHN) or if the RPM package is available install it from the /var/spool/up2date directory with the command:

# rpm -Uvh /var/spool/up2date/redhat-release*.rpm

You may have to add the –nodeps option to the above command if the provided options fails to execute.

Finally, sync your system profile with Red Hat Network:

# up2date -p

Once these steps are completed, the system will be able continue to update from Red Hat Network.

Tips and tricks: How do I setup device-mapper multipathing in Red Hat Enterprise Linux 4?

the editorial team — Thu, 17 Jul 2008 23:17:13 +0000

Release Found: Red Hat Enterprise Linux 4 Update 2 and later

In order to setup device-mapper-multipathing an updated system with the package device-mapper-multipath is recommended.

This functionality does not exist in releases of Red Hat Enterprise Linux 4 prior to Update 2.

To set up device-mapper multipathing, edit the /etc/multipath.conf file. Comment out the following lines at the top of the file:

devnode_blacklist {
        devnode "*"
}

For example:

# devnode_blacklist {
#        devnode "*"
# }

This section keeps device-mapper multipathing from scanning all of the devices. Uncomment the following section of the /etc/multipath.conf file:

defaults {
       multipath_tool  "/sbin/multipath -v0"
       udev_dir        /dev
       polling_interval 10
       default_selector        "round-robin 0"
       default_path_grouping_policy    multibus
       default_getuid_callout  "/sbin/scsi_id -g -u -s /block/%n"
       default_prio_callout    "/bin/true"
       default_features        "0"
       rr_min_io              100
       failback                immediate
}
blacklist {
        wwid 26353900f02796769
       devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
       devnode "^hd[a-z][[0-9]*]"
       devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
}

This sets the default device-mapper behavior and filters out all the devices that are not normally multipathed, such as IDE hard drives and floppy drives.

In order to use simple failover behaviour, the default_path_grouping_policy option in the defaults section should be changed to failover as illustrated by the sample below:

defaults {
       multipath_tool  "/sbin/multipath -v0"
       udev_dir        /dev
       polling_interval 10
       default_selector        "round-robin 0"
       default_path_grouping_policy    failover
       default_getuid_callout  “/sbin/scsi_id -g -u -s /block/%n”
       default_prio_callout    “/bin/true”
       default_features        “0″
       rr_min_io              100
       failback                immediate
}

Save the configuration file and exit the editor. Execute the following commands:

modprobe dm-multipath
modprobe dm-round-robin
service multipathd start
multipath -v2

The multipath -v2 command prints out multipathed paths that show which devices are multipathed. If the command does not print anything out, ensure that all SAN connections are set up properly and the system is multipathed. Execute this command to make sure that the multipath daemon starts on bootup:

chkconfig multipathd on

The devices will be created as /dev/mapper/mpath#, where # is the multipathed group. If /dev/sda is the only multipathed device, /dev/mapper/mpath0 will be the multipathed device for /dev/sda and /dev/sdb. Note that fdisk cannot be used with /dev/dm-# devices. Use fdisk on the underlying disks and execute the following command when device-mapper multipath maps the device to create a /dev/mapper/mpath# device for the partition:

kpartx -a /dev/mapper/mpath#

Note: dmsetup ls –target=multipath is a command that helps determine multipath devices assignments on a system.

If the hardware is not mentioned in the multipathing database, please view the article “How can I add more products into the mutipathing database?” in the Recommended FAQs section.

For an updated sample configuration file, see /usr/share/doc/device-mapper-multipath-/multipath.conf.annotated

Tips and tricks: What is the procedure to resize an LVM2 logical volume and the ext2 or ext3 filesystem?

the editorial team — Thu, 17 Jul 2008 00:05:07 +0000

It is recommended that a resizing procedure be tested before performing it on a filesystem that contains critical data. It is also strongly recommended that data backups are created and verified before resizing filesystems. To assist the reader in becoming familiar with the resizing procedure, the rest of this article describes a scenario in which un-partitioned disk space is used to test logical volume and ext3 filesystem resizing.

In this test procedure, first we create a new partition (/dev/hda2) using un-partitioned disk space. A new volume group (TestVG) and logical volume (TestLV) are then created using a physical volume created on the partition. An ext3 filesystem is then created on the logical volume, it is checked, and then mounted. A new physical volume (/dev/hda3) using the rest of the un-partioned disk space is then created and added to the volume group and logical volume. Finally, the filesystem on the logical volume is resized, and the integrity of the filesystem is checked.

In this test procedure, the parted, lvm, mount, mkfs.ext3, df, e2fsck and ext2online programs are used. The reader is encouraged to become familiar with these programs by consulting the manual pages. For example:

# man parted

PARTED(8)                          GNU Parted Manual          PARTED(8)

NAME
       GNU Parted - a partition manipulation program

SYNOPSIS
       parted [options] [device [command [options...]...]]
...

The parted and lvm programs can be run in either interactive or non-interactive mode. This article restricts all the examples to non-interactive modes. The reader is also encouraged to consult the parted and lvm online help available for all their built in commands to understand the command syntax for these programs.

Creating a new partition for the new physical volume

The parted program can be used to verify that un-partitioned disk space is available using the print command:

# parted /dev/hda print
Disk geometry for /dev/hda: 0.000-76318.054 megabytes
Disk label type: msdos
Minor    Start       End     Type      Filesystem  Flags
1          0.031    101.975  primary   ext3        boot
4      31118.093  76316.594  extended
5      31220.099  76316.594  logical   ext3        lvm
Information: Don't forget to update /etc/fstab, if necessary.

In this case the output of the parted print command shows that there is unallocated space between 101.975 (At the end of partition 1) to 31118.093 (The beginning of partition 4) on the /dev/hda device.

A new partition is created using only some of the available disk space, using the parted mkpart command, then the print command is used to verify:

# parted /dev/hda "mkpart primary 101.976 2500"
Information: Don't forget to update /etc/fstab, if necessary.

# parted /dev/hda print
Disk geometry for /dev/hda: 0.000-76318.054 megabytes
Disk label type: msdos
Minor    Start       End     Type      Filesystem  Flags
1          0.031    101.975  primary   ext3        boot
2        101.975   2502.312  primary   ext3
4      31118.093  76316.594  extended
5      31220.099  76316.594  logical   ext3        lvm
Information: Don't forget to update /etc/fstab, if necessary.

Create the new physical volume on the new partition

The lvm program is used to manipulate LVM2 volume groups, logical volumes and physical volumes. First use the lvm pvs command to list the physical volumes already present. Then the pvcreate command is used to create the new physical volume using the new partition, and the pvs again to verify the new physical volume:

# lvm pvs
  PV         VG         Fmt  Attr PSize  PFree
  /dev/hda5  VolGroup00 lvm2 a-   44.03G    0

# lvm pvcreate /dev/hda2
  Physical volume "/dev/hda2" successfully created

# lvm pvs
  PV         VG         Fmt  Attr PSize  PFree
  /dev/hda2             lvm2 --    2.34G 2.34G

  /dev/hda5  VolGroup00 lvm2 a-   44.03G    0

Create a new volume group for a new logical volume

When creating a new volume group, at least one physical volume must be available. That physical volume must be used to create the new volume group. Notice that a volume group called ‘VolGrouop00′ already exists:

# lvm vgs
  VG         #PV #LV #SN Attr  VSize  VFree
  VolGroup00   1   2   0 wz--n 44.03G    0

# lvm vgcreate TestVG /dev/hda2
  Volume group "TestVG" successfully created

# lvm vgs
  VG         #PV #LV #SN Attr  VSize  VFree
  TestVG       1   0   0 wz--n  2.34G 2.34G
  VolGroup00   1   2   0 wz--n 44.03G    0

Note that new volume groups must be activated using the lvm vgchange -a y command:

# lvm vgchange -a y TestVG
  0 logical volume(s) in volume group "TestVG" now active

Now there is a new directory in /dev for the volume group:

# ls -ld /dev/TestVG
drwx------  2 root root 60 Jan 17 17:48 /dev/TestVG

Create a test logical volume in the new volume group

In this case I wish to allocate all of the volume group’s physical extent (available disk space) to a new logical volume. First I use the lvm vgdisplay command to show details of the TestVG volume group:

# lvm vgdisplay TestVG
  --- Volume group ---
  VG Name               TestVG
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  1
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                0
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               2.34 GB
  PE Size               4.00 MB
  Total PE              598
  Alloc PE / Size       0 / 0
  Free  PE / Size       598 / 2.34 GB
  VG UUID               ebStj9-3KYx-asoc-JBt3-N9kU-vONW-4VdpTB

The total free physical extent of the volume group is “Free PE / Size 598 / 2.34 GB”, so I will use the value 598 in the lvm lvcreate command to create the new logical volume:

# lvm lvs
  LV       VG         Attr   LSize  Origin Snap%  Move Copy%
  LogVol00 VolGroup00 -wi-ao 43.03G
  LogVol01 VolGroup00 -wi-ao  1.00G

# lvm lvcreate -l598 TestVG -nTestLV
  Logical volume "TestLV" created

# lvm lvs
  LV       VG         Attr   LSize  Origin Snap%  Move Copy%
  TestLV   TestVG     -wi-a-  2.34G
  LogVol00 VolGroup00 -wi-ao 43.03G
  LogVol01 VolGroup00 -wi-ao  1.00G

Now a new device has been added to the /dev/TestVG directory:

# ls -l /dev/TestVG
total 0
lrwxrwxrwx  1 root root 25 Jan 17 17:48 TestLV -> /dev/mapper/TestVG-TestLV

The new device is in fact a symbolic link to /dev/mapper/TestVG-TestLV which is the device node created by the device mapper.

Create a file system on the new logical volume

The new file system on the logical volume is created by using the mkfs.ext3 program:

# mkfs.ext3 /dev/TestVG/TestLV
mke2fs 1.35 (28-Feb-2004)
max_blocks 627048448, rsv_groups = 19136, rsv_gdb = 149
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
306432 inodes, 612352 blocks
30617 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=629145600
19 block groups
32768 blocks per group, 32768 fragments per group
16128 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912

Writing inode tables: done
inode.i_blocks = 7160, i_size = 4243456
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 35 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

Then check the file system using e2fsck program:

#  e2fsck -f /dev/TestVG/TestLV
e2fsck 1.35 (28-Feb-2004)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/TestVG/TestLV: 11/306432 files (9.1% non-contiguous), 18728/612352 blocks

Mount the new file system

Before mounting the new file system , I create a new mount point, then mount the new logical volume’s file system on that mount point. After mounting the file system, I ran the df program to verify the disk space available:

# mkdir /mnt/test
# mount /dev/TestVG/TestLV /mnt/test

# df -h /mnt/test
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/TestVG-TestLV
                      2.3G   36M  2.2G   2% /mnt/test

The resize test procedure

This is the general procedure to resize a filesystem. Begin by adding a new physical volume.

Create a new partition that will contain a new physical volume

Using parted as before, I run the print command to view the partitions, and then mkpart to create a new partition:

# parted /dev/hda print
Disk geometry for /dev/hda: 0.000-76318.054 megabytes
Disk label type: msdos
Minor    Start       End     Type      Filesystem  Flags
1          0.031    101.975  primary   ext3        boot
2        101.975   2502.312  primary   ext3
4      31118.093  76316.594  extended
5      31220.099  76316.594  logical   ext3        lvm
Information: Don't forget to update /etc/fstab, if necessary.

There is un-partitioned disk space available between 2502.312 (The end of partition 2) and 31118.093 (The beginning of partition 4):

# parted /dev/hda "mkpart primary 2502.313 31118.092"
Information: Don't forget to update /etc/fstab, if necessary.

# parted /dev/hda print
Disk geometry for /dev/hda: 0.000-76318.054 megabytes
Disk label type: msdos
Minor    Start       End     Type      Filesystem  Flags
1          0.031    101.975  primary   ext3        boot
2        101.975   2502.312  primary   ext3
3       2502.312  31118.093  primary
4      31118.093  76316.594  extended
5      31220.099  76316.594  logical   ext3        lvm
Information: Don't forget to update /etc/fstab, if necessary.

Create the physical volume

The new physical volume is created as before, by running the lvm pvcreate command. The new physical volume will be on /dev/hda3:

# lvm pvs
  PV         VG         Fmt  Attr PSize  PFree
  /dev/hda2  TestVG     lvm2 a-    2.34G    0
  /dev/hda5  VolGroup00 lvm2 a-   44.03G    0

# lvm pvcreate /dev/hda3
  Physical volume "/dev/hda3" successfully created

# lvm pvs
  PV         VG         Fmt  Attr PSize  PFree
  /dev/hda2  TestVG     lvm2 a-    2.34G     0
  /dev/hda3             lvm2 --   27.94G 27.94G
  /dev/hda5  VolGroup00 lvm2 a-   44.03G     0

Add the physical volume to the volume group

The physical volume is added to the TestVG volume group using the lvm vgextend command:

# lvm vgextend TestVG /dev/hda3
  Volume group "TestVG" successfully extended

# lvm pvs
  PV         VG         Fmt  Attr PSize  PFree
  /dev/hda2  TestVG     lvm2 a-    2.34G     0
  /dev/hda3  TestVG     lvm2 a-   27.94G 27.94G
  /dev/hda5  VolGroup00 lvm2 a-   44.03G     0

Extend the logical volume in the volume group

As before, first look at the physical extent of the volume group using the lvm vgdisplay command. It shows that TestVG has 7153 free extents in “Free PE / Size 7153 / 27.94 GB”:

# lvm vgdisplay TestVG
  --- Volume group ---
  VG Name               TestVG
  System ID
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  3
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               30.28 GB
  PE Size               4.00 MB
  Total PE              7751
  Alloc PE / Size       598 / 2.34 GB
  Free  PE / Size       7153 / 27.94 GB
  VG UUID               ebStj9-3KYx-asoc-JBt3-N9kU-vONW-4VdpTB

I wish to use all the free physical extents on the volume group. I do this using the lvm lvextend command with the option -l+7153 . This adds the 7153 free extents to the logical volume:

# lvm lvextend -l+7153 /dev/TestVG/TestLV
  Extending logical volume TestLV to 30.28 GB
  Logical volume TestLV successfully resized

The file system now has space on the logical volume in which to grow.

Resize the file system

After extending the volume group and the logical volume, it is now possible to resize the file system. This is done using ext2online. First I verify the file system size, perform the resize, and then verify the size again:

# df -h /mnt/test
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/TestVG-TestLV
                      2.3G   36M  2.2G   2% /mnt/test

# ext2online /dev/TestVG/TestLV
ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b

# df -h /mnt/test
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/TestVG-TestLV
                       30G   39M   29G   1% /mnt/test

Check the file system integrity after the resize

The file system should be un-mounted before doing a file system check:

#  e2fsck -f /dev/TestVG/TestLV
e2fsck 1.35 (28-Feb-2004)
/dev/TestVG/TestLV is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.

Do you really want to continue (y/n)? no

check aborted.

# umount /mnt/test

#  e2fsck -f /dev/TestVG/TestLV
e2fsck 1.35 (28-Feb-2004)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/TestVG/TestLV: 11/3919104 files (9.1% non-contiguous), 132827/7937024 blocks

Conclusion

The procedure to test online resizing of filesystems is quite complex. So it is important to practice the procedure and become familiar with the programs and commands. Once this is done, and reasonable precautions such as backing up important data are taken, it should be safe to resize your filesystems.

Tips and tricks: What is a Red Hat Enterprise Linux Installation Number and where do I get it?

the editorial team — Mon, 14 Jul 2008 20:23:14 +0000

The Red Hat Enterprise Linux 5 Installation Number is a 16-character hexadecimal text string used during the installation process. The installation number enables a user to install the full set of supported packages included with the subscription. For a limited set of Red Hat Enterprise Linux subscribers, the installation number is also used to activate subscriptions for additional Red Hat products and services. It replaces the Subscription Number from earlier versions of Red Hat Enterprise Linux.

Why use an installation number?

The Red Hat Enterprise Linux 5 installation trees and ISO images, in addition to the core operating system, contain a number of optional components. The Installation Number entered by the user during the installation process guides the Installer to include the correct components that match the user’s Red Hat Enterprise Linux Subscription. With certain types of Subscriptions it is also used to activate the Subscription in Red Hat Network. When registering the system to Red Hat Network (RHN), the Installation number is used to automatically subscribe the system to the right child channels. Finally it can be used by the customer to verify compliance to the subscription and might be requested by Red Hat Support when reporting an incident.

What about installation of multiple systems?

When installing multiple systems using a Kickstart file, the Installation Number can be embedded in that Kickstart file. As Installation Numbers identify the Subscription features, they are not unique per system. Thus an identical Installation Number can be used for several systems that share the same Subscription options including Variant and SLA.

Is the use of the Installation Number mandatory?

While not recommended to do, the user has the option to skip entering the installation number or to override it in a Kickstart file. In that case the Red Hat Enterprise Linux 5 installer will only offer the core operating system components for installation, a behavior similar to the installers in earlier versions of Red Hat Enterprise Linux.

The installation number for the Red Enterprise Linux 5 subscription can be found in several places, including:

The new subscription activation email, received by your Red Hat Network Organization Administrator (the user who first established the Red Hat account) or your company’s purchasing contact named on the order. The subject line for the new subscription activation email is the New Subscription Activation key of the product.
Red Hat Subscription Management:
http://www.redhat.com/apps/support/IN.html
Red Hat Customer Service:
http://www.redhat.com/about/contact/dir/#custservice

Tips and tricks: How do I apply package updates from Red Hat Network?

the editorial team — Wed, 09 Jul 2008 22:25:56 +0000

Before installing an update, make sure all previously released errata relevant to the system have been applied.

To use Red Hat Network (RHN) from Red Hat Enterprise Linux 2.1, 3, or 4, launch the interactive Red Hat Update Agent with the command:

# up2date

To find more information about the command line options available for up2date, use the command:

# man up2date

To use Red Hat Network (RHN) for Red Hat Enterprise Linux 5, launch the graphical Update tool with the command:

# pup

Alternatively, for a command-line interface, use the command:

# yum update

To find more information about the command line options available for yum, use the command:

# man yum

Tips and tricks: Create and register a new Red Hat Directory Server 8.0 instance on a remote configuration server

the editorial team — Mon, 07 Jul 2008 22:29:17 +0000

Product: Red Hat Directory Server
Version: 8.0 on Red Hat Enterprise Linux 4 Update 5

Creating new directory server instances can be done from the command line, with the script setup-ds-admin.pl as described in the Installation Guide, 6.2.1. Creating a New Directory Server Instance

If you are unable to register a new Red Hat Directory Server 8.0 instance with the script setup-ds-admin.pl to a remote configuration server, build
Red Hat-Directory/8.0.0 B2007.353.1757

And are getting this error message:

Error adding entry 'cn=Red Hat Directory Server, cn=Server Group,
cn=host.example.com, ou=example.com, o=NetscapeRoot'. Error: No such object
Could not register the directory server with the configuration directory server.

Create the following 2 entries on the configuration Directory Server:

Note: Replace example.com with the real domain and host.example.com with the real hostname.

dn: cn=host.example.com, ou=example.com, o=NetscapeRoot
objectclass: top
objectclass: nsHost
objectclass: groupOfUniqueNames
cn: host.example.com
nsosversion: output of uname -a on the machine
nshardwareplatform: arch e.g. i386 or x86_64 or ...
serverHostName: host.example.com

dn: cn=Server Group, cn=host.example.com, ou=example.com, o=NetscapeRoot
objectclass: top
objectclass: nsAdminGroup
objectclass: nsDirectoryInfo
objectclass: groupOfUniqueNames
nsAdminGroupName: Server Group
nsDirectoryInfoRef: cn=User Directory, ou=Global Preferences, ou=example.com,
o=NetscapeRoot

Bugzilla reference 431103