Topic: MySQL upgrade to MySQL 5.5.13 not compatible with SME 8.0beta6 server.

[LANMonkey]

I have managed to successfully install an upgrade of MySQL 5.5.13 in my SME 8.0beta6 server.  I used the remi repository together with the epel repository with the following command:

Code: [Select]

yum --enablerepo=epel2,remi update mysql\* 

epel2 was a repository I installed from another source instead of the one provided by Contribs.  See the discussion on this upgrade here:

http://forums.famillecollet.com/viewtopic.php?pid=1812

I have several bits of evidence that this upgrade is not compatible.  My preference in the webmail, like filters, is not present.  Several WordPress sites I had installed are not working.  And I can't log in from the client.

So I need to know how to get my system back or if it is even possible.  Perhaps a reinstallation is required.

I have tried some yum commands.  "yum erase mysql\*" warned me against ripping it out like that.  "yum reinstall mysql\*" just tried to reinstall the upgrade.  My first attempt was the most natural to me, "yum downgrade mysql\*" and this almost appeared to work.  This is what I got back:

Code: [Select]

[xxx@xxx ~]#yum downgrade  mysql\*
Loaded plugins: fastestmirror, protect-packages, smeserver
Setting up Downgrade Process
Loading mirror speeds from cached hostfile
 * base: mirrors.netdna.com
 * updates: mirrors.usc.edu
Excluding Packages from CentOS - os
Finished
Excluding Packages from CentOS - updates
Finished
No Match for available package: mysql-bench-5.0.77-4.el5_5.4.i386
No Match for available package: mysql-connector-odbc-3.51.26r1127-1.el5.i386
No Match for available package: mysql-devel-5.0.77-4.el5_5.4.i386
No Match for available package: mysql-test-5.0.77-4.el5_5.4.i386
Resolving Dependencies
--> Running transaction check
---> Package mysql.i386 0:5.0.77-4.el5_6.6 set to be updated
---> Package mysql.i386 0:5.5.13-1.el5.remi set to be erased
---> Package mysql-server.i386 0:5.0.77-4.el5_6.6 set to be updated
---> Package mysql-server.i386 0:5.5.13-1.el5.remi set to be erased
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package          Arch     Version                 Repository              Size
================================================================================
Downgrading:
 mysql            i386     5.0.77-4.el5_6.6        smeupdates-testing     4.8 M
 mysql-server     i386     5.0.77-4.el5_6.6        smeupdates-testing     9.8 M

Transaction Summary
================================================================================
Remove        0 Package(s)
Reinstall     0 Package(s)
Downgrade     2 Package(s)

Total size: 15 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
  file /usr/lib/mysql/libmysqlclient.so.15.0.0 from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysqlclient15-5.0.67-1.el5.remi.i386
  file /usr/lib/mysql/libmysqlclient_r.so.15.0.0 from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysqlclient15-5.0.67-1.el5.remi.i386
  file /etc/my.cnf from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/charsets/Index.xml from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/charsets/cp1250.xml from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/charsets/cp1251.xml from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/czech/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/danish/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/dutch/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/english/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/estonian/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/french/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/german/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/greek/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/hungarian/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/italian/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/japanese/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/korean/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/norwegian-ny/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/norwegian/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/polish/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/portuguese/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/romanian/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/russian/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/serbian/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/slovak/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/spanish/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/swedish/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386
  file /usr/share/mysql/ukrainian/errmsg.sys from install of mysql-5.0.77-4.el5_6.6.i386 conflicts with file from package mysql-libs-5.5.13-1.el5.remi.i386

Error Summary
-------------
[xxx@xxx ~]#
I can't interpret these errors towards a solution.

So, any tips, clues or solutions on how to restore my mysql to its original 5.0 version would be appreciated.

[LANMonkey]

I have now tried,

Code: [Select]

yum --enablerepo epel2,remi downgrade  mysql\*
But I tried to follow it with

Code: [Select]

signal-event post-downgrade
but got an error about not being able to open a file, or something, so I used,

Code: [Select]

signal-event post-upgrade
signal-event reboot
But the upgrade is still in place.  Was my error in applying the post-upgrade event?  How do you follow up a downgrade in SME?

[janet]

LANMonkey

Number 1 GOLDEN RULE
DO NOT  test or experiment on production systems

It is very easy to setup a test server & try these experimental upgrades first. If your production box uses RAID1, then remove a fully sync'd drive & put that in the test server so you have a test server "identical" to your production server.

To fix try
rpm -e --nodeps packagename
for all the mysql packages that you inappropriately upgraded. Look at the yum log files to see what was upgraded
(note: when using the --nodeps switch, be very careful to ensure only packages you really wish to remove are removed)

Then do a normal
yum update
making sure ONLY the standard recommended repos are enabled ie as per contribs wiki yum articles

signal-event post-upgrade
signal-event reboot

[cactus]

Code: [Select]

[xxx@xxx ~]#yum downgrade  mysql\*
Loaded plugins: fastestmirror, protect-packages, smeserver
Setting up Downgrade Process


snip

Code: [Select]

================================================================================
 Package          Arch     Version                 Repository              Size
================================================================================
Downgrading:
 mysql            i386     5.0.77-4.el5_6.6        smeupdates-testing     4.8 M
 mysql-server     i386     5.0.77-4.el5_6.6        smeupdates-testing     9.8 M

Transaction Summary
================================================================================


This also shows you have smeupdates-testing enabled by default which is another thing you should better not do as the packages in this repository are not tested and are development releases. Please take my advice and only enable the repositories as advised in the FAQ:

http://wiki.contribs.org/SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled

[LANMonkey]

Thanks for helping me out on this people.  It's not as though I hadn't been warned.  A bad combination of no information, overconfidence and laziness.

Here are the logs for that day:

Code: [Select]

Jun 08 11:23:23 Installed: php-common-5.3.6-4.el5.remi.i386
Jun 08 11:23:30 Installed: mysqlclient15-5.0.67-1.el5.remi.i386
Jun 08 11:23:32 Installed: mysql-libs-5.5.13-1.el5.remi.i386
Jun 08 11:23:33 Updated: php-pdo-5.3.6-4.el5.remi.i386
Jun 08 11:23:35 Updated: mysql-5.5.13-1.el5.remi.i386
Jun 08 11:23:36 Installed: libedit-2.11-2.20080712cvs.el5.i386
Jun 08 11:23:37 Updated: php-cli-5.3.6-4.el5.remi.i386
Jun 08 11:23:40 Updated: php-5.3.6-4.el5.remi.i386
Jun 08 11:23:40 Installed: libaio-0.3.106-5.i386
Jun 08 11:23:40 Installed: libXmu-1.0.2-5.i386
Jun 08 11:23:41 Installed: libXaw-1.0.2-8.1.i386
Jun 08 11:23:46 Installed: t1lib-5.1.1-7.el5.i386
Jun 08 11:23:46 Updated: php-xml-5.3.6-4.el5.remi.i386
Jun 08 11:23:53 Updated: mysql-server-5.5.13-1.el5.remi.i386
Jun 08 11:23:55 Updated: php-mbstring-5.3.6-4.el5.remi.i386
Jun 08 11:23:55 Updated: php-ldap-5.3.6-4.el5.remi.i386
Jun 08 11:23:55 Updated: php-imap-5.3.6-4.el5.remi.i386
Jun 08 11:23:56 Updated: php-gd-5.3.6-4.el5.remi.i386
Jun 08 11:23:56 Updated: php-mysql-5.3.6-4.el5.remi.i386
Jun 08 11:24:00 Updated: php-devel-5.3.6-4.el5.remi.i386
Jun 08 11:24:09 Erased: php-pecl-Fileinfo
Jun 08 12:37:22 Installed: mysql-libs-5.5.12-1.el5.remi.i386
Jun 08 12:37:27 Installed: mysql-5.5.12-1.el5.remi.i386
Jun 08 12:37:35 Installed: mysql-server-5.5.12-1.el5.remi.i386
Gleaned from that here is a summary of the remi packages installed:

Code: [Select]

mysqlclient15-5.0.67-1.el5.remi.i386
mysql-libs-5.5.13-1.el5.remi.i386
mysql-libs-5.5.12-1.el5.remi.i386
mysql-5.5.12-1.el5.remi.i386
mysql-server-5.5.12-1.el5.remi.i386
mysql-server-5.5.13-1.el5.remi.i386
mysql-5.5.13-1.el5.remi.i386
php-xml-5.3.6-4.el5.remi.i386
php-mbstring-5.3.6-4.el5.remi.i386
php-ldap-5.3.6-4.el5.remi.i386
php-imap-5.3.6-4.el5.remi.i386
php-gd-5.3.6-4.el5.remi.i386
php-mysql-5.3.6-4.el5.remi.i386
php-devel-5.3.6-4.el5.remi.i386
php-common-5.3.6-4.el5.remi.i386
php-pdo-5.3.6-4.el5.remi.i386
php-cli-5.3.6-4.el5.remi.i386
php-5.3.6-4.el5.remi.i386 

There were also some other packages installed as you can see in the logs:

Code: [Select]

libedit-2.11-2.20080712cvs.el5.i386
libaio-0.3.106-5.i386
libXmu-1.0.2-5.i386
libXaw-1.0.2-8.1.i386
t1lib-5.1.1-7.el5.i386
Now mary says that I should just remove the mysql packages with 'rpm -e'.  I would be tempted to remove everything from the remi repository and maybe even the other packages installed at the same time.

But, very precisely, should I only remove,

Code: [Select]

mysqlclient15-5.0.67-1.el5.remi.i386
mysql-libs-5.5.13-1.el5.remi.i386
mysql-libs-5.5.12-1.el5.remi.i386
mysql-5.5.12-1.el5.remi.i386
mysql-server-5.5.12-1.el5.remi.i386
mysql-server-5.5.13-1.el5.remi.i386
mysql-5.5.13-1.el5.remi.i386
Or should I remove everything from remi, or everything installed that session?

[cactus]

I would uninstall all packages that were installed in that session and re-install the packages that are updated and/or removed.

Fixed: syntax error

[LANMonkey]

I would install all packages that were installed in that session and re-install the packages that are updated and/or removed.

Do you mean you would uninstall all packages that were installed in that session ... ?  It's the uninstallation that I am asking about, 'rpm -e'.

[cactus]

Do you mean you would uninstall all packages that were installed in that session ... ?  It's the uninstallation that I am asking about, 'rpm -e'.

Oops, yes.

[LANMonkey]

OK, I tried uninstalling all of the remi packages, line by line.  Most of them would not be uninstalled, they failed due to dependency errors.

Here is the summary of results:

mysqlclient15-5.0.67-1.el5.remi.i386 failed from dependency errors " ... needed by ... "
mysql-libs-5.5.13-1.el5.remi.i386 not installed "... package not found ..."
mysql-libs-5.5.12-1.el5.remi.i386 uninstalled
mysql-5.5.12-1.el5.remi.i386 uninstalled
mysql-server-5.5.12-1.el5.remi.i386 failed from dependency errors " ... needed by ... "
mysql-server-5.5.13-1.el5.remi.i386 not installed "... package not found ..."
mysql-5.5.13-1.el5.remi.i386 not installed "... package not found ..."
php-xml-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "
php-mbstring-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "
php-ldap-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "
php-imap-5.3.6-4.el5.remi.i386 not installed "... package not found ..."
php-gd-5.3.6-4.el5.remi.i386, failed from dependency errors " ... needed by ... "
php-mysql-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "
php-devel-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "
php-common-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "
php-pdo-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "
php-cli-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "
php-5.3.6-4.el5.remi.i386 failed from dependency errors " ... needed by ... "

I'm not going to try any of the rest until I get this cleared up.

Any solutions here?

[cactus]

Any solutions here?

Yes:

Code: [Select]

rpm -e --nodeps package-name

[LANMonkey]

OK, I processed absolutely everything that I posted in my yum logs above using 'rpm -e --nodeps package-name'.  The I ran "yum update", and I am getting depsolving and conflict errors:

Code: [Select]

yum update
Loaded plugins: fastestmirror, protect-packages, smeserver
Loading mirror speeds from cached hostfile
 * base: mirror.hmc.edu
 * updates: centos.mirror.facebook.net
Excluding Packages from CentOS - os
Finished
Excluding Packages from CentOS - updates
Finished
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package e-smith-samba.noarch 0:2.2.0-45.el5.sme set to be updated
--> Processing Dependency: samba3x-common >= 3.3.8 for package: e-smith-samba
--> Processing Dependency: samba3x-client >= 3.3.8 for package: e-smith-samba
--> Processing Dependency: samba3x >= 3.3.8 for package: e-smith-samba
--> Processing Dependency: /usr/bin/tdbbackup for package: e-smith-samba
--> Running transaction check
---> Package samba.i386 0:3.0.33-3.29.el5_6.2 set to be updated
--> Processing Dependency: samba-common = 3.0.33-3.29.el5_6.2 for package: samba
---> Package samba3x.i386 0:3.5.4-0.70.el5_6.1 set to be updated
--> Processing Dependency: libwbclient.so.0 for package: samba3x
--> Processing Dependency: libtalloc.so.2 for package: samba3x
--> Processing Dependency: libtdb.so.1 for package: samba3x
---> Package samba3x-client.i386 0:3.5.4-0.70.el5_6.1 set to be updated
---> Package samba3x-common.i386 0:3.5.4-0.70.el5_6.1 set to be updated
--> Processing Dependency: libsmbclient for package: samba3x-common
--> Running transaction check
---> Package libsmbclient.i386 0:3.0.33-3.29.el5_6.2 set to be updated
---> Package libtalloc.i386 0:2.0.1-11.el5 set to be updated
---> Package libtdb.i386 0:1.2.1-5.el5 set to be updated
---> Package samba-common.i386 0:3.0.33-3.29.el5_6.2 set to be updated
---> Package samba3x-winbind.i386 0:3.5.4-0.70.el5_6.1 set to be updated
--> Processing Conflict: samba3x-client conflicts samba < 3.5.4-0.70.el5_6.1
--> Processing Conflict: samba3x-winbind conflicts samba-common < 3.5.4-0.70.el5_6.1
--> Processing Conflict: samba3x conflicts samba-common < 3.5.4-0.70.el5_6.1
--> Processing Conflict: samba3x conflicts samba < 3.5.4-0.70.el5_6.1
--> Processing Conflict: samba3x-common conflicts samba-common < 3.5.4-0.70.el5_6.1
--> Processing Conflict: samba3x-common conflicts samba < 3.5.4-0.70.el5_6.1
--> Finished Dependency Resolution
samba3x-3.5.4-0.70.el5_6.1.i386 from smeupdates-testing has depsolving problems
  --> samba3x conflicts with samba-common
samba3x-winbind-3.5.4-0.70.el5_6.1.i386 from smeupdates-testing has depsolving problems
  --> samba3x-winbind conflicts with samba-common
samba3x-3.5.4-0.70.el5_6.1.i386 from smeupdates-testing has depsolving problems
  --> samba3x conflicts with samba
samba3x-client-3.5.4-0.70.el5_6.1.i386 from smeupdates-testing has depsolving problems
  --> samba3x-client conflicts with samba
samba3x-common-3.5.4-0.70.el5_6.1.i386 from smeupdates-testing has depsolving problems
  --> samba3x-common conflicts with samba-common
samba3x-common-3.5.4-0.70.el5_6.1.i386 from smeupdates-testing has depsolving problems
  --> samba3x-common conflicts with samba
Error: samba3x-common conflicts with samba-common
Error: samba3x-client conflicts with samba
Error: samba3x conflicts with samba-common
Error: samba3x-common conflicts with samba
Error: samba3x-winbind conflicts with samba-common
Error: samba3x conflicts with samba
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.

This was run with the smeupdates-testing repository enabled.  I also tried it with that repo disabled, but got similar errors.

Recall that my server is SME 8.0beta6.  There are some issues with Samba.  See this wikipedia entry:

http://wiki.contribs.org/SME_Server_8#Upgrading_samba

So what's next.  Anyone?

[cactus]

This was run with the smeupdates-testing repository enabled.  I also tried it with that repo disabled, but got similar errors.

Recall that my server is SME 8.0beta6.  There are some issues with Samba.  See this wikipedia entry:

http://wiki.contribs.org/SME_Server_8#Upgrading_samba

So what's next.  Anyone?

How about following the instructions you found yourself? Since you state that you are on SME Server 8 beta 6 these do apply to your situation, since you are now trying to update it.

[LANMonkey]

Here are the results of those commands,

Code: [Select]

rpm -q samba samba3x
samba-3.0.33-3.7.el5_3.1
package samba3x is not installed
Now the instructions provide for two contingencies, either samba-3.4 is installed, or samba3x is installed.  My results do not fit either contingency.

I'll assume that my result of samba-3.0 being installed is appropos of the first example (I had run this before and was stalled by this difference.) and I run the command listed in the instructions:

Code: [Select]

rpm -e --nodeps libtalloc libtdb samba samba-client samba-common samba-winbind
Here is what I get back:

Code: [Select]

rpm -e --nodeps libtalloc libtdb samba samba-client samba-common samba-winbind
error: package libtalloc is not installed
error: package libtdb is not installed
error: package samba-winbind is not installed
I alter the command to exclude the missing packages,

Code: [Select]

# rpm -e --nodeps  samba samba-client samba-common               
warning: /etc/samba/smb.conf saved as /etc/samba/smb.conf.rpmsave
warning: /etc/samba/smbusers saved as /etc/samba/smbusers.rpmsave
warning: /etc/pam.d/samba saved as /etc/pam.d/samba.rpmsave

I run, 'yum install tdb-tools' and this is successful.

And now I run 'yum update', followed by the usual 'signal-event post-upgrade; signal-event reboot'

On the reboot, I am getting an error on the monitor: 'httpd:  Syntax error on line 111 of /etc/httpd.conf/httpd.conf:  Cannot load /etc/httped/modules/libphp4.so into server: /etc/httpd/modules/libphp4.so: cannot open shared object file: No such file or directory'  And the web-manager page is not available.

The error is coming up in a repeated loop and fills up the screen.  I can log in to SSH successfully.  I am trying a second 'signal-event reboot'.  Same result.

The web server is down, none of the sites are available.

I am trying a second 'yum-update'.  There are no packages marked for update.

So my gateway on SME is still up, but the webserver is down as of this posting.  The system seems to be loaded up by this continuing loop that generates this repeating error display.

[cactus]

And now I run 'yum update', followed by the usual 'signal-event post-upgrade; signal-event reboot'

On the reboot, I am getting an error on the monitor: 'httpd:  Syntax error on line 111 of /etc/httpd.conf/httpd.conf:  Cannot load /etc/httped/modules/libphp4.so into server: /etc/httpd/modules/libphp4.so: cannot open shared object file: No such file or directory'  And the web-manager page is not available.

The error is coming up in a repeated loop and fills up the screen.  I can log in to SSH successfully.  I am trying a second 'signal-event reboot'.  Same result.

The web server is down, none of the sites are available.

That is because you also de-installed PHP and currently have no PHP installed most likely, since one of your previous posts mentioned the update of php:

Here are the logs for that day:

Code: [Select]

Jun 08 11:23:23 Installed: php-common-5.3.6-4.el5.remi.i386
Jun 08 11:23:30 Installed: mysqlclient15-5.0.67-1.el5.remi.i386
Jun 08 11:23:32 Installed: mysql-libs-5.5.13-1.el5.remi.i386
Jun 08 11:23:33 Updated: php-pdo-5.3.6-4.el5.remi.i386
Jun 08 11:23:35 Updated: mysql-5.5.13-1.el5.remi.i386
Jun 08 11:23:36 Installed: libedit-2.11-2.20080712cvs.el5.i386
Jun 08 11:23:37 Updated: php-cli-5.3.6-4.el5.remi.i386
Jun 08 11:23:40 Updated: php-5.3.6-4.el5.remi.i386


I am trying a second 'yum-update'.  There are no packages marked for update.

So my gateway on SME is still up, but the webserver is down as of this posting.  The system seems to be loaded up by this continuing loop that generates this repeating error display.

That won't help you as that will only try and find updates again, if the package is not installed it will not get updated.

I have already told you that you also need to reinstall packages that are marked updated:

I would uninstall all packages that were installed in that session and re-install the packages that are updated and/or removed.

Fixed: syntax error

Please read our instructions carefully. Thanks in advance

[LANMonkey]

I am running an install on all the packages that I uninstalled.

Some direction really is suggested.  Should a post-upgrade and reboot be run after every installation?  That's a lot of reboots.  There is also the issue of the correct order of installation.  But it appears that my system is being restored and after each reboot, I see more functionality return.

SYSTEM RESTORED.

Everything appears to be back in place.  I have my filters back in webmail and all my MySQL/PHP dependent blogs are functioning.  I consider the problem solved.

Would it have been easier to just do a reinstallation?  I wondered about files that might have become incompatible somehow, in which case I would have been twice fouled up.  Correcting an existing system is far more reassuring, even if more time consuming.

All this could have been avoided if I had installed a test server and why not?  It would have been easy enough to find one that would host SME.  Even an old laptop would have done the job.