I got Upgrading firefox-1.0-12.EL4.x86_64. error: %post(firefox-1.0-12.EL4.x86_64) scriptlet failed, exit status 255 Upgrading iiimf-x-12.1-10.EL.x86_64. error: %post(iiimf-x-12.1-10.EL.x86_64) scriptlet failed, exit status 255 Upgrading iiimf-gtk-12.1-10.EL.x86_64. error: %post(iiimf-gtk-12.1-10.EL.x86_64) scriptlet failed, exit status 255 Upgrading system-switch-im-0.1.2-3.noarch. Upgrading iiimf-le-chinput-0.3-16.x86_64. error: %post(iiimf-le-chinput-0.3-16.x86_64) scriptlet failed, exit status 255 Upgrading iiimf-le-xcin-0.1.7-11.x86_64. error: %post(iiimf-le-xcin-0.1.7-11.x86_64) scriptlet failed, exit status 255 Upgrading iiimf-gnome-im-switcher-12.1-10.EL.x86_64. error: %post(iiimf-gnome-im-switcher-12.1-10.EL.x86_64) scriptlet failed, exit status 255 when I was upgrading from RHEL 4 RC to RHEL4 on EM64T. Passing "selinux=0" to kernel seems to fix the problem.
Upgrades between beta releases are not supported.
Those messages also happened to upgrading from RHEL 3 U4: Upgrading libgcc-3.4.3-9.EL4.i386. error: %post(libgcc-3.4.3-9.EL4.i386) scriptlet failed, exit status 255 Upgrading glibc-2.3.4-2.i686. warning: /etc/ld.so.conf created as /etc/ld.so.conf.rpmnew error: %postun(glibc-2.3.2-95.30.i686) scriptlet failed, exit status 255 error: %trigger(redhat-lsb-1.3-3.1.EL3.i386) scriptlet failed, exit status 255 error: %trigger(redhat-lsb-1.3-3.1.EL3.x86_64) scriptlet failed, exit status 255Upgrading glibc-2.3.4-2.x86_64. warning: /etc/ld.so.conf created as /etc/ld.so.conf.rpmnew error: %trigger(redhat-lsb-1.3-3.1.EL3.i386) scriptlet failed, exit status 255 error: %trigger(redhat-lsb-1.3-3.1.EL3.x86_64) scriptlet failed, exit status 255
Can you provide the complete /root/install.log from your rhel3 install plus /root/upgrade.log from after the upgrade as well as /var/log/anaconda*
I will upload /root/install.log and /root/anaconda-ks.cfg. /root/upgrade.log and /var/log/anaconda* are generated when booting kernel with "selinux=0" after I saw those messages in upgrade.log. They are quite normal now. I can upload them if you still want them.
Created attachment 111263 [details] anaconda-ks.cfg
Created attachment 111264 [details] install.log
I got the same problem when uprading from RHEL 4 to RHEL 4 U1 on ia32 and EM64T. As the result, some rpms weren't upgraded. I had to run the upgrade process the second time, passing "selinux=0" to kernel.
Anaconda should not be used for upgrades except between releases -- going between updates, you should use up2date.