efa-project.org


https://forum.efa-project.org/

[solved] v3.0.0.9 upgrade fails because of various issues

https://forum.efa-project.org/viewtopic.php?t=1552

Page 1 of 1

[solved] v3.0.0.9 upgrade fails because of various issues

Posted: 11 Apr 2016 06:48
by pdwalker
(note: I'm just writing my thoughts down here as I diagnose my own update problems. I'm not asking for help; summary is at the bottom)

yum update previously run and system previously rebooted

Code: Select all

[root@efa spamassassin]# yum update
Loaded plugins: fastestmirror, security
Setting up Update Process
Loading mirror speeds from cached hostfile
epel/metalink                                            | 5.2 kB     00:00
 * base: centos.01link.hk
 * epel: ftp.cuhk.edu.hk
 * extras: centos.01link.hk
 * rpmforge: mirror.oscc.org.my
 * updates: centos.01link.hk
base                                                     | 3.7 kB     00:00
extras                                                   | 3.4 kB     00:00
rpmforge                                                 | 1.9 kB     00:00
updates                                                  | 3.4 kB     00:00
No Packages marked for Update
checking and updating EFA

Code: Select all

[root@efa ~]# EFA-Update -check
[EFA] Getting latest version number from http://dl.efa-project.org
[EFA] You are running EFA version EFA-3.0.0.8
[EFA] Latest version update is EFA-3.0.0.9
[root@efa ~]# EFA-Update -update
[EFA] Good you are root
[EFA] Starting update to EFA-3.0.0.9
[EFA] Good you are root
Loaded plugins: fastestmirror, security
Setting up Update Process
Loading mirror speeds from cached hostfile
 * base: centos.01link.hk
 * epel: ftp.cuhk.edu.hk
 * extras: centos.01link.hk
 * rpmforge: mirror.oscc.org.my
 * updates: centos.01link.hk
No Packages marked for Update
Your system has an updated kernel, but you are not running
on the latest kernel.  Please restart your system and run
EFA-Update after restart.
/var/EFA/update/EFA-update-script died with exit status 1
[root@efa ~]# uname -a
Linux efa.domain.local 2.6.32-573.22.1.el6.x86_64 #1 SMP Wed Mar 23 03:35:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
rebooted again, just because

Code: Select all

[root@efa spamassassin]# /var/EFA/update/EFA-update-script
[EFA] Good you are root
Loaded plugins: fastestmirror, security
Setting up Update Process
Loading mirror speeds from cached hostfile
epel/metalink                                            | 5.2 kB     00:00
 * base: centos.01link.hk
 * epel: ftp.cuhk.edu.hk
 * extras: centos.01link.hk
 * rpmforge: mirror.oscc.org.my
 * updates: centos.01link.hk
base                                                     | 3.7 kB     00:00
extras                                                   | 3.4 kB     00:00
rpmforge                                                 | 1.9 kB     00:00
updates                                                  | 3.4 kB     00:00
No Packages marked for Update
Your system has an updated kernel, but you are not running
on the latest kernel.  Please restart your system and run
EFA-Update after restart.
check the kernel update check in the update script, lines 354 and 355 and run those commands

Code: Select all

[root@efa ~]# uname -r
2.6.32-573.22.1.el6.x86_64
[root@efa ~]# grep -m 1 CentOS /boot/grub/menu.lst
title CentOS (2.6.32-573.22.1.el6.x86_64.debug)
that's funny. running a debug kernel?
reboot again and make sure the correct kernel is selected.
that's funny. I didn't get a chance to select which kernel to boot.

further checking: my booted kernel was the second entry in the grub kernel list, not the first. The update check was looking for the first entry. As a result, the update check was failing.

Quick fix, reconfigure the boot list to make the first entry the kernel I need to boot from and continue with the update.

Not sure why my kernel entry in the grub list was different from the default - something I previously did, or some artifact from previous upgrades/updates. Solution(?) pay attention to the "default=X" line in the grub file and then grep for that particular line? Or just ignore it because my installation is weird. I think I'll go with weird.

fixed the grub problem, now rerun the update

Code: Select all

[root@efa ~]# /var/EFA/update/EFA-update-script
Error: Package: 2:postfix-perl-scripts-2.6.6-6.el6_7.1.x86_64 (@updates)
           Requires: postfix = 2:2.6.6-6.el6_7.1
           Removing: 2:postfix-2.6.6-6.el6_7.1.x86_64 (@updates)
               postfix = 2:2.6.6-6.el6_7.1
           Updated By: 2:postfix-3.0.4-1.efa.el6.x86_64 (EFA)
               postfix = 2:3.0.4-1.efa.el6
           Available: 2:postfix-2.6.6-6.el6_5.x86_64 (base)
               postfix = 2:2.6.6-6.el6_5
           Available: 2:postfix-3.0.3-2.efa.el6.x86_64 (EFA)
               postfix = 2:3.0.3-2.efa.el6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Update to Version 3.0.0.9 FAILED.  Updates cancelled.
result: failure again.
according to this post, remove the problem package

Code: Select all

[root@efa ~]# yum erase postfix-perl-scripts
rerun the update
result: failure again.

Code: Select all

Transaction Check Error:
  file /usr/share/man/man3/XML::SAX::Base.3pm.gz from install of perl-XML-SAX-0.96-7.el6.noarch conflicts with file from package perl-XML-SAX-Base-1.04-1.el6.rf.noarch
  file /usr/share/man/man3/XML::SAX::Exception.3pm.gz from install of perl-XML-SAX-0.96-7.el6.noarch conflicts with file from package perl-XML-SAX-Base-1.04-1.el6.rf.noarch
According to this post, remove the package and reinstall and then try again...

Code: Select all

rpm -e --nodeps perl-XML-SAX-Base
yum install perl-XML-SAX
/var/EFA/update/EFA-update-script
side note: I'm getting emails with the subject "EFA Update Complete..."

I think the subject should either be "EFA Update Failure..." or "EFA Update Results..." in this case.

update result this time: third time lucky. update complete.

Code: Select all

3.0.0.9 update is complete

All done
Please restart your system as soon as possible.
If your system does not return to a command prompt
you can now safely press ctrl-c to abort logsave
Thank you for using E.F.A.
[root@efa ~]# reboot
reboot one more time and check system - update appears successful, mail is going in and out properly.

Summary:
three problems preventing updates.
- two of them previously documented in the forums
- one of them appears "new" and is probably a problem specific to my installation for whatever reason
- each failure sends an "EFA Update Complete" message which is not technically correct :)
- last updated succeeded (of course) and everything appears to be working.

Oh, and thanks to you previous upgraders for having the problems and solving them. That certainly saved me a lot of time.

Re: [solved] v3.0.0.9 upgrade fails because of various issues

Posted: 11 Apr 2016 19:03
by darky83
A few useful comments there thanks :)

We still don't fully understand why some installations have yum conflicts and some don't.
Did some testing with previous installs, and also I have an system running from 3.0.0.0 up until the latest version that always upgraded just fine.

Maybe it is because of some customisation some users have done (monitoring tools maybe?)

The comment about the upgrade mails is an good one, we should change it if the upgrade fails, good point.

Re: [solved] v3.0.0.9 upgrade fails because of various issues

Posted: 13 Apr 2016 09:42
by pdwalker
Glad to help.

I think the thing to do would be to for us to compare the yum.conf and the yum.repos.d to see if there are any significant differences between the two that might be causing the issue.

I don't recall if I made any changes to mine but that doesn't mean I didn't. It's not something I would want to do as I don't want to get away from the base.

One thing I do do, is run "yum update" from the command line periodically. Perhaps one of the updates causes the issue during upgrade time?
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited