up2date questions

[merimax]

Hello:

I am running RH3 linux and I am trying to do an up2date but I keep getting the message attached below.

If I force the upgrade will I mess up DA? Can I just force the update of these packages and then just do a 'build all' in customapache?

Any help you can provide would be appreciated.

Thanks,
Darlene
Merimax, Inc.



*************UP2DATE OUTPUT****************
To solve all dependencies for the RPMs you have selected, The following
packages you have marked to exclude would have to be added to the set:

Package Name Reason For Skipping
======================================================================
MySQL-python-0.9.1-6 Pkg name/pattern
httpd-2.0.46-46.ent Pkg name/pattern
httpd-devel-2.0.46-46.ent Pkg name/pattern
kernel-2.4.21-32.0.1.EL Pkg name/pattern
kernel-2.4.21-32.0.1.EL Pkg name/pattern
kernel-BOOT-2.4.21-32.0.1.EL Pkg name/pattern
kernel-debuginfo-2.4.21-4.0.1. Pkg name/pattern
kernel-debuginfo-2.4.21-4.0.1. Pkg name/pattern
kernel-debuginfo-2.4.21-4.0.1. Pkg name/pattern
kernel-doc-2.4.21-32.0.1.EL Pkg name/pattern
kernel-hugemem-2.4.21-32.0.1.E Pkg name/pattern
kernel-hugemem-unsupported-2.4 Pkg name/pattern
kernel-smp-2.4.21-32.0.1.EL Pkg name/pattern
kernel-smp-2.4.21-32.0.1.EL Pkg name/pattern
kernel-smp-unsupported-2.4.21- Pkg name/pattern
kernel-smp-unsupported-2.4.21- Pkg name/pattern
kernel-source-2.4.21-32.0.1.EL Pkg name/pattern
kernel-unsupported-2.4.21-32.0 Pkg name/pattern
kernel-unsupported-2.4.21-32.0 Pkg name/pattern
kernel-utils-2.4-8.37.12 Pkg name/pattern
mod_auth_mysql-20030510-2.ent Pkg name/pattern
mod_auth_pgsql-2.0.1-4.ent Pkg name/pattern
mod_perl-1.99_09-10.ent Pkg name/pattern
mod_perl-devel-1.99_09-10.ent Pkg name/pattern
mod_python-3.0.3-5.ent Pkg name/pattern
mod_ssl-2.0.46-46.ent Pkg name/pattern
mysql-3.23.58-15.RHEL3.1 Pkg name/pattern
mysql-bench-3.23.58-15.RHEL3.1 Pkg name/pattern
mysql-devel-3.23.58-15.RHEL3.1 Pkg name/pattern
php-4.3.2-23.ent Pkg name/pattern
php-devel-4.3.2-23.ent Pkg name/pattern
php-imap-4.3.2-23.ent Pkg name/pattern
php-ldap-4.3.2-23.ent Pkg name/pattern
php-mysql-4.3.2-23.ent Pkg name/pattern
php-odbc-4.3.2-23.ent Pkg name/pattern
php-pgsql-4.3.2-23.ent Pkg name/pattern
sendmail-8.12.11-4.RHEL3.1 Pkg name/pattern
sendmail-cf-8.12.11-4.RHEL3.1 Pkg name/pattern
sendmail-devel-8.12.11-4.RHEL3 Pkg name/pattern
sendmail-doc-8.12.11-4.RHEL3.1 Pkg name/pattern
tftp-server-0.39-0.EL3.1 Pkg name/pattern
vsftpd-1.2.1-3E.1 Pkg name/pattern

Unresolvable chain of dependencies:
redhat-config-httpd 1.1.0-4.30.2 requires httpd

 

[nobaloney]

Welcome to up2date hell.

Do NOT remove httpd from the exclude list or you will break your install to the point where you may have to rebuild your server.

Instead add redhat-config-httpd to the exclude list.

Which will probably give you another error.

Continue to exclude packages that result in the same error, until it either works or you find one you cannot remove because you need it.

At that point, write back with the message you then receive.

Jeff

 

[merimax]

I added redhat-config-httpd to the exclude list and all went well.

Can I upgrade the kernel?

Thanks again for your help.

Darlene

 

[nobaloney]

DA won't care about the kernel upgrade.

Can you upgrade the kernel? Sure.

May you upgrade the kernel? (with apologies to my sixth grade teacher)

You'll have to make that decision on your own. It won't cause any problems with DA.

We used to shake in our boots when updating kernels. We feel a lot better about it now, but we still make sure there's a good reason before we blindly do it, as it does require the server be rebooted to run off the new kernel.

Jeff

 

[roel]

If you're gonna update the kernel, leave your GRUB or LILO on the old one by default, to start with - both boot managers have options to only use the new kernel on the next reboot. That way, you won't have to phone up some poor guy who'll have to drive over to the datacenter to change it back to the old kernel with all the associated downtime, if the new one borks the system. (assuming your server is connected to an APC or something, of course)
And yes, I had this happen to me once.

 

[nobaloney]

Only once? You're lucky .

Speaking for RHL and RHEL:

If your server ran from the Install CDs and installed the kernels unchanged on your server, and if you don't use proprietary hardware RAID, it's likely an automated Kernel upgrade will work without problem.

What roel explains makes sense, but I don't believe that's automatically installed by the automatic upgrade routines.

If you're going to modify LILO or GRUB to only boot the new kernel once, then don't forget to modify it back to continue using it in the future.

Jeff