Topic: Upgrading to SME server 7.2

[MasthaX]

Good day, I am running SME server 7.1.3 at the moment and i was wandering can i upgrade it without losing my current settings? I want to upgrade it for PHP5 and MYSQL 5. Also I am running a used mailserver. I dont have users(not like a file server). Just 3 accounts so I can recreate them if nesscesery. I am sorry if there was a topic about this but I couldn't find it.

Regards, Jurgen

[NickCritten]

Hi MasthaX,

there's nothing to stop you upgrading to 7.2, just read the release announcement http://forums.contribs.org/index.php?topic=37872.0 you will find upgrade instructions there.

7.2 does not upgrade PHP or MySQL to v5 however, and doing so manually isn't for the faint-hearted.

There are several forum threads on the subject of upgrading PHP & MySQL if you really want to go ahead with it though.

Nick

[Brenno]

I just performed the upgrade from 7.1.3 to 7.2 per the instructions at:
http://wiki.contribs.org/SME_Server:Documentation:FAQ&section=3#Updating_from_SME_7.1.3_to_SME_7.2

The server-manager and server-console are still reporting 7.1.3.

How can I track down the source of the failure?  What might be available in the logs, etc?

[chris burnat]

The server-manager and server-console are still reporting 7.1.3.
How can I track down the source of the failure?  What might be available in the logs, etc?

Have you performed the reconfiguration required after the upgrade?   This reconfiguration would have rebooted your server, and you can check this by looking into the "messages" log.

After clicking Reconfigure check the Status message and that the server does actually reboot. Rarely circumstances arise that prevent the reconfigure from triggering. If so run the following:

Code: [Select]

signal-event post-upgrade; signal-event reboot
If this does not fix your issue, please enter a bug report at Bugzilla providing as much information as you can.

[Brenno]

I followed the instructions to the letter; the server did reboot and I verified this in the logs.

I re-ran the post-upgrade and reboot commands just now to see if that would make any difference.  Again, I verified that the server rebooted by checking the logs, but there is no change.

I am hesitant to simply repeat the whole upgrade process in case this makes things worse.... is this possibly a good option?

[StuartTaylor]

This happened to me as welll with both of the servers I am running. 

Doing a yum clean all sorted me out for server number 1

server number 2 simply refuses to update I have done the yum clean all for that one as well but it doesn't do anything.

I am considering trying to update from using the 7.2 cd.

[chris burnat]

I am hesitant to simply repeat the whole upgrade process in case this makes things worse.... is this possibly a good option?

It is not a good option, apart from potentially adding to your problems, this issue should be brought to the attention of the Dev Team, you may have a bug which needs to be identified.  Please fill a report at Bugzilla, and attach the following:
- yum/yum logs
- The output of the commands (as attachments):

Code: [Select]

/sbin/e-smith/audittools/templates

and

/sbin/e-smith/audittools/newrpms  

This would be a good start.
Thanks
chris

[chris burnat]

This happened to me as welll with both of the servers I am running.   server number 2 simply refuses to update I have done the yum clean all for that one as well but it doesn't do anything. I am considering trying to update from using the 7.2 cd.

 This issue should be brought to the attention of the Dev Team, you may have a bug which needs to be identified.  Please fill a separate report at Bugzilla, and attach the following:
- yum yum logs
- The output of the commands (as attachments):

Code: [Select]

/sbin/e-smith/audittools/templates

and

/sbin/e-smith/audittools/newrpms  
Thanks.
chris

[Brenno]

Chris,

I am opening a bug on this... how do I get that output into a txt file or otherwise for attaching?

Also, I don't have an /sbin/e-smith/audittools/newrpms file... is that a problem, too?

[chris burnat]

Brenno, OK.  Do not worry about the command line stuff.  Just copy and paste the yum/yum log (server-manager --> view log files) onto a text file and attach it to the bug report. Thanks.

[Brenno]

I have opened bug number 3299 and included snippets from both yum/yum.log and yum/current.

[Brenno]

I tried following the latest version of the instructions for upgrading on a different bone-stock server, and here is the verbatim text output from putty:

Code: [Select]

[root@ponch ~]# yum update smeserver-support smeserver-yum yum yum-plugin-fastest-mirror python-sqlite
==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Loading "smeserver" plugin
Loading "fastestmirror" plugin
Setting up Update Process
Setting up repositories
smeaddons                 100% |=========================|  951 B    00:00
updates                   100% |=========================|  951 B    00:00
base                      100% |=========================| 1.1 kB    00:00
ftp://ftp.planetmirror.com/pub/smeserver/releases/7/smeos/i386/repodata/repomd.xml: [Errno 4] IOError: [Errno ftp error] 550 7: No such file or directory
Trying other mirror.
smeos                     100% |=========================|  951 B    00:00
smeupdates                100% |=========================|  951 B    00:00
Determining fastest mirrors
Reading repository metadata in from local files
Excluding Packages from CentOS - updates
Finished
Excluding Packages from CentOS - os
Finished
Could not find update match for python-sqlite
Could not find update match for yum
Could not find update match for yum-plugin-fastest-mirror
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for smeserver-yum to pack into transaction set.
smeserver-yum-1.2.0-37.el 100% |=========================|  46 kB    00:01
---> Package smeserver-yum.noarch 0:1.2.0-37.el4.sme set to be updated
---> Downloading header for smeserver-support to pack into transaction set.
smeserver-support-1.6.0-3 100% |=========================|  32 kB    00:00
---> Package smeserver-support.noarch 0:1.6.0-39.el4.sme set to be updated
--> Running transaction check
--> Processing Dependency: smeserver-locale-sv for package: smeserver-support
--> Processing Dependency: smolt for package: smeserver-support
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for smeserver-locale-sv to pack into transaction set.
smeserver-locale-sv-1.2.0 100% |=========================|  13 kB    00:00
---> Package smeserver-locale-sv.noarch 0:1.2.0-27.el4.sme set to be updated
---> Downloading header for smolt to pack into transaction set.
smolt-0.9.8.1-5.el4.sme.n 100% |=========================|  12 kB    00:00
---> Package smolt.noarch 0:0.9.8.1-5.el4.sme set to be updated
--> Running transaction check
--> Processing Dependency: aspell-sv for package: smeserver-locale-sv
--> Processing Dependency: dbus-python for package: smolt
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for aspell-sv to pack into transaction set.
aspell-sv-0.51-1.2.1.el4. 100% |=========================| 3.2 kB    00:00
---> Package aspell-sv.i386 50:0.51-1.2.1.el4.sme set to be updated
---> Downloading header for dbus-python to pack into transaction set.
dbus-python-0.22-12.EL.9. 100% |=========================| 9.2 kB    00:00
---> Package dbus-python.i386 0:0.22-12.EL.9 set to be updated
--> Running transaction check

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Updating:
 smeserver-support       noarch     1.6.0-39.el4.sme  smeos              83 k
 smeserver-yum           noarch     1.2.0-37.el4.sme  smeos              77 k
Installing for dependencies:
 aspell-sv               i386       50:0.51-1.2.1.el4.sme  smeos             1.3 M
 dbus-python             i386       0.22-12.EL.9     smeos             115 k
 smeserver-locale-sv     noarch     1.2.0-27.el4.sme  smeos              64 k
 smolt                   noarch     0.9.8.1-5.el4.sme  smeos             139 k

Transaction Summary
=============================================================================
Install      4 Package(s)
Update       2 Package(s)
Remove       0 Package(s)
Total download size: 1.8 M
Is this ok [y/N]: y
Downloading Packages:
(1/6): smeserver-support- 100% |=========================|  83 kB    00:01
(2/6): smeserver-locale-s 100% |=========================|  64 kB    00:00
(3/6): aspell-sv-0.51-1.2 100% |=========================| 1.3 MB    00:05
(4/6): smolt-0.9.8.1-5.el 100% |=========================| 139 kB    00:00
(5/6): dbus-python-0.22-1 100% |=========================| 115 kB    00:00
(6/6): smeserver-yum-1.2. 100% |=========================|  77 kB    00:00
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
smeserver trap pre-install: smeserver-support
smeserver trap pre-install: smeserver-locale-sv
smeserver trap pre-install: aspell-sv
smeserver trap pre-install: smolt
smeserver trap pre-install: dbus-python
smeserver trap pre-install: smeserver-yum
  Updating  : smeserver-yum                ######################### [1/8]
  Installing: dbus-python                  ######################### [2/8]
  Installing: smolt                        ######################### [3/8]
  Installing: aspell-sv                    ######################### [4/8]
  Installing: smeserver-locale-sv          ######################### [5/8]
  Updating  : smeserver-support            ######################### [6/8]
  Cleanup   : smeserver-support            ######################### [7/8]
  Cleanup   : smeserver-yum                ######################### [8/8]
Migrating existing database mailpatterns
Migrating existing database networks
Migrating existing database spamassassin
Migrating existing database hosts
Migrating existing database accounts
Migrating existing database configuration
Migrating existing database yum_updates
Migrating existing database domains
Migrating existing database yum_installed
Migrating existing database yum_available
Migrating existing database yum_repositories
Migrating existing database backups
smeserver trap post-install: smeserver-support
smeserver trap post-install: smeserver-locale-sv
smeserver trap post-install: aspell-sv
smeserver trap post-install: smolt
smeserver trap post-install: dbus-python
smeserver trap post-install: smeserver-yum

Dependency Installed: aspell-sv.i386 50:0.51-1.2.1.el4.sme dbus-python.i386 0:0.22-12.EL.9 smeserver-locale-sv.noarch 0:1.2.0-27.el4.sme smolt.noarch 0:0.9.8.1-5.el4.sme
Updated: smeserver-support.noarch 0:1.6.0-39.el4.sme smeserver-yum.noarch 0:1.2.0-37.el4.sme
Complete!
==============================================================
WARNING: You now need to run BOTH of the following commands
to ensure consistent system state:

signal-event post-upgrade; signal-event reboot

You should run these commands unless you are certain that
yum made no changes to your system.
==============================================================
[root@ponch ~]# signal-event post-upgrade
[root@ponch ~]# signal-event reboot

Broadcast message from root (pts/1) (Thu Aug 16 21:10:32 2007):

The system is going down for reboot NOW!
[root@ponch ~]#
What I find curious is this, found right near the top:

Code: [Select]

Could not find update match for python-sqlite
Could not find update match for yum
Could not find update match for yum-plugin-fastest-mirror
I stopped the update process at this point and have not proceeded through the rest of the instructions lest this be a critical part of what went wrong the first time.  I also verified that the proper repositories were enabled via the server-manager before starting.

Any thoughts?

[chris burnat]

Brenno,
It all looks ok.  Keeping a copy of all proceedings during upgrade is good insurance, right?
The entries:

Code: [Select]

Could not find update match for python-sqlite
Could not find update match for yum
Could not find update match for yum-plugin-fastest-mirrorIndicate that these particular modules did not require upgrading when starting from 7.1.3.  I have checked this against some of my upgrade logs.  You are well on your way... Continue the upgrade by following the recipe found in the Wikis, yum clean all etc...  If there is a problem, you can always abort by saying N instead of Y - so no harm done.

Next is to try this on your other server, go one step at a time, as you did for this exercise.
but please report all of your findings in Bugzilla for this server, cross posting from Forum/Bugzilla make the Dev life a misery.
Thanks.

[Brenno]

Chris,

I completed the update on the second machine and it reports as 7.2 now.  I captured all details of the process via putty (all 1587 lines!)

There were some fatal errors reported during the process:

Code: [Select]

FATAL: Could not open '/boot/System.map-2.6.9-55.0.2.EL': No such file or directory
These occurred as the packages were being updated/installed, but things seem to be working fine at this point, though, so I will try this procedure again on the original machine and log everything.  I won't post the log to the bug I opened because this install actually went fine, but will post logs if the original machine upgrade fails for any reason.

Thanks for all your help.  This is a trial process for me; both of these machines were "fresh" installs of 7.0 (from CD) and not upgrades from previous versions.  I have one production email box still running 6.01 that I need to upgrade, but want to ensure I have the process down before upgrading to 7.0 via CD and then eventually 7.2 via this process.

[chris burnat]

Brenno, good news.

"but will post logs if the original machine upgrade fails for any reason."

Please post failure or success, outlining what you done about the machine associated with this bug report.
Thanks.