Today I had to solve a RPM problem on a Red Hat Enterprise Linux WS release 4 (Nahant Update 6) system (RHEL4) where there were duplicate packages when querying the rpm database. This had happened after an upgrade to update 6 using up2date from the command line.
It seemed like i386 and x64 packages had gotten installed on some packages and this caused some problems, like logon authentication and execution of some programs.
Trying to remove a duplicate rpm package
# rpm -e libtool-libs-1.5.6-4.El4.2
gave the error message
error: "libtool-libs-1.5.6-4.El4.2" specifies multiple packages
After searching the Red Hat knowledge base I located article Why do I see duplicate packages when querying the rpm database? where it says it is necessary to specify the architecture of the package to remove.
# rpm -qa --queryformat %{NAME}-%{VERSION}-%{ARCH}\\n
If you add %{RELEASE} you can also determine if the package is from other package vendors like RPMForge.
Since this was a x64 system, I wanted to remove the i386 version
# rpm -e libtool-libs-1.5.6-4.El4.2.i386
This had to be done with every duplicate package on the system.
Locate the i386 packages that interfered with the x64 packages can be done using the command
rpm -qa | sort | uniq -d
These packages have dependencies so you have to add these manually, really fun job to do.
Edit:
In RHEL5 you can use yum to remove packages in a easy way
yum remove <package>.i386 yum remove <package>.x86_64
Tags: RedHat, RHEL4, rhel5, rpm, up2date
Posted by Hans-Henry Jakobsen
You may access either graphical or text interfaces for the Redhat installation system from any other system. Access to a text mode display requires telnet, which is installed by default on Fedora systems. To remotely access the graphical display of an installation system, use client software that supports the VNC (Virtual Network Computing) display protocol. A number of providers offer VNC clients for Microsoft Windows and Mac OS, as well as UNIX-based systems.
The installation system supports two methods of establishing a VNC connection. You may start the installation, and manually login to the graphical display with a VNC client on another system. Alternatively, you may configure the installation system to automatically connect to a VNC client on the network that is running in listening mode.
Enabling Remote Access with VNC
To enable remote graphical access to the installation system, enter two options at the prompt:
linux vnc vncpassword=astrongpassword
The vnc option enables the VNC service. The vncpassword option sets a password for remote access. The example shown above sets the password as astrongpassword. The VNC password must be at least six characters long.
Specify the language, keyboard layout and network settings for the installation system with the screens that follow. You may then access the graphical interface through a VNC client. The installation system displays the correct connection setting for the VNC client:
Starting VNC... The VNC server is now running. Please connect to computer.mydomain.com:1 to begin the install... Starting graphical installation... Press <enter> for a shell
You may then login to the installation system with a VNC client. Start the VNC client Enter the server and display number in the VNC Server dialog. For the example above, the VNC Server is computer.mydomain.com:1.
This is possible on RedHat, Fedora and probably other distributions derived on these distributions like CentOS.
Tags: CentOS, Fedora, installation, RedHat, remote access, vnc
Posted by Hans-Henry Jakobsen
I’ve just migrated a couple of servers from Courier-IMAP to Dovecot, and am very happy with the latter so far. I thought I’d share the courier2dovecot shell script I whipped together (based on the instructions I found in the migration how-to), for converting Courier-IMAP maildirs to Dovecot format.
While the script is rather simple, it can save a fair bit of typing when migrating some hundreds of mail accounts, especially since Courier stores some of its own state files recursively in each folder of the maildir hierarchy, making it a real pain to otherwise manually rename or remove all of them.
Here’s a plain-English summary of what the script currently does, when given a Courier maildir path as an argument:
The script will also verbosely print out each action it performs, handy for redirecting the output to a log file for a large migration.
Hopefully people about to jump ship from Courier to Dovecot find this useful. If anyone comes up with improvements to the script, please send them my way.
#!/bin/sh # # courier2dovecot -- Converts a Courier maildir to Dovecot format. # Copyright (c) 2005 Arto Bendiken. Released under the GNU GPL. # Newest version available from http://bendiken.net/scripts/ # # 2005-10-21 initial version for Dovecot 1.0. # dir="$1" if [ -z "$dir" ] || [ "$dir" = "-?" ] || [ "$dir" = "-h" ] || [ "$dir" = "--help" ]; then echo "Usage: $0 maildirpath" exit 1 fi if [ ! -d "$dir" ] || [ ! -e "$dir/courierimapsubscribed" ]; then echo "$dir is not a path to a Courier maildir" exit 1 fi find $dir -name courierimapsubscribed -print0 | xargs -0r rename -v 's/courierimapsubscribed/subscriptions/' find $dir -name subscriptions -print0 | xargs -0r sed -i 's/INBOX\.//' find $dir -name courierimapuiddb -print0 | xargs -0r rename -v 's/courierimapuiddb/dovecot-uidlist/' find $dir -name courierimaphieracl -print0 | xargs -0r rm -vrf find $dir -name courierimapacl -print0 | xargs -0r rm -vf find $dir -name courierimapkeywords -print0 | xargs -0r rm -vrf
Comment to the script:
Hey Arto & everyone using this script:
Be careful when trying to run this on Red Hat Enterprise Linux or CentOS 4 systems. These operating systems ship with a different rename command than the Debian systems. You can also tell them apart based on the output when running ‘rename’ with no arguments.
This is the perl version which works:
Usage: rename [-v] [-n] [-f] perlexpr [filenames]
This is the RHEL/CentOS version that doesn’t:
call: rename.orig from to files…
Hope this helps someone out there, and thanks for the script Arto!
Source: http://bendiken.net/2005/11/03/courier-imap-to-dovecot-migration-script
Tags: CentOS, Courier-imap, Debian, Dovecot, Fedora, find, maildir, perl, RedHat, SMTP, xargs
Posted by Hans-Henry Jakobsen
yum and rpm stop doing their magic because of corrupt files etc and no updates can be performed on the system. A simple, but maybe not recommended solution is to delete the files located in /var/lib/rpm
-rw-r--r-- 1 root root 0 Jan 22 10:10 __db.000 -rw-r--r-- 1 root root 24576 Jan 19 17:12 __db.001 -rw-r--r-- 1 root root 1318912 Jan 19 17:12 __db.002 -rw-r--r-- 1 root root 450560 Jan 19 17:12 __db.003
This solution does most likely work in other rpm based distributions.
Tags: core 5, Fedora, RedHat, rpm, yum
Posted by Hans-Henry Jakobsen
You can specify the SELinux mode using the configuration file /etc/sysconfig/selinux.
# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=enforcing # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
Setting the value to enforcing is the same as adding enforcing=1 to your command line when booting the kernel to turn enforcing on, while setting the value to permissive is the same as adding enforcing=0 to turn enforcing off. Note that the command line kernel parameter overrides the configuration file.
However, setting the value to disabled is not the same as the selinux=0 kernel boot parameter. Rather than fully disabling SELinux in the kernel, the disabled setting instead turns enforcing off and skips loading a policy.
Source: http://fedora.redhat.com/docs/selinux-faq-fc3/index.html#id2825945
Tags: CentOS, Fedora, RedHat, selinux
Posted by Hans-Henry Jakobsen