Archive for the 'tips and tricks' category

Question: I got an error that stated: ‘error code 91: Red Hat software management exhausted’ what do I do?

Answer: This error is most commonly received when you are trying to use activation keys to connect a system profile to Red Hat Network (RHN) but you have exhausted all available management entitlements.

You would need to purchase additional Management level entitlements if you wish to continue using activation keys. Generally you will not get this error when using the up2date --register command unless you have previously created an activation key and designated it as the universal default key on your account. If you previously used an activation key flagged as the universal default, you would need to update the status on that Activation Key before you could create new profiles using the up2date --register command. » Read more

Yes, to achieve this, pass the shared disk with the w! option.

For example in /etc/xen/<config file for vm&gt do the following:

disk = [ "file:/var/lib/xen/images/hostOS.img,hda,w""file:/var/lib/xen/images/qdisk.img,sda,w!"

Make the setting, then boot up all nodes. Create qdisk fs, then check that all nodes can read the qdisk fs:

$ mkqdisk -L

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.

First, make sure that you have downloaded the correct files. For each distribution there are binary files and source files. To complete an installation the four binary files for a particular distribution are required.

Simply burning these files to CD as files will result in a single file being burnt to CD with a .iso extension. If this occurs your disks will not be bootable. The files available from Red Hat Network (RHN) are disk images and need to be burned to CD as an image.

Your burning software will extract the files from the .iso and burn them to CD. See your specific burning software documentation for more information on how to burn images to CD.

To check if you have burned each image correctly simply examine the contents of the CD. Instead of a single .iso file the disk should contain multiple files and directories.

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.

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=

» Read more

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. » Read more

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. » Read more

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.

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.

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

» Read more

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 "*"
# }

» Read more

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. » Read more