Article ID: 2303, created on Oct 29, 2007, last review on Apr 18, 2012

  • Applies to:
  • Pro Control Panel Linux


View Knowledge
Knowledge ID 1025
Product : WEBppliance for Linux
Version : 3.5.15
Topic : FAQ

Failing to restart MySQL can cause the WEBppliance Pro 3.5.15 upgrade to fail

When you install the WEBppliance Pro for Linux 3.5.15 upgrade you may end up getting the following error:

On WEBppliance LS your error would look like:

Upgrading... (this may take several minutes to hours)
Upgrade to Linux Webppliance 3.5.15-6 [FAILED]

Failed to install service RPMs.

Installation aborted.
Please review the error logs in /var/log/ensim for more information.
Failure: Upgrading your system

On WEBppliance LH the control center will say that there was an error in the webppliance-mysql post install scriptlet.

Please verify that this is the issue that caused the upgrade to fail. Check /var/log/ensim/installer.err you should see something like:

Starting MySQL: [FAILED]
Please do the following:
1. Consult /var/log/appliance/setup.err for the description and /var/log/appliance/setup.log for the detail.
2. Try to address the problem.
3. Run the setup script again.
error: execution of %post scriptlet from webppliance-mysql-3.5.15-6 failed, exit status 1

Also in /var/log/appliance/setup.err you would see:

[Sun Jul 27 13:28:19 GMT+4 2003] [success] mysql Creating symlink to Ensim Sys V Init script
[Sun Jul 27 13:33:21 GMT+4 2003] [failure] mysql starting mysqld
Failed to execute: "/etc/rc.d/init.d/mysqld start".

This happens because MySQL doesn't restart properly. The first thing you should do is:

killall mysqld
/etc/rc.d/init.d/mysql start
rpm -qa | grep webppliance-mysql
You should see 2 different versions installed, uninstall the older one with:
rpm -e --nodeps --justdb --noscripts webppliance-mysql-3.5.10
cd /usr/lib/opcenter/rpmscripts/mysql
./post 2
/etc/rc.d/init.d/webppliance start
If you have a lot of domains then starting webppliance will take a while. Let this run you can monitor /var/log/appliance/ensim_appliance.log to see the process.




Related Knowledge

Related Links
Last ModifiedUsageSatisfiedLast Used
8/20/2004 1:00:55 PM182 10/11/2007 5:55:27 AM

4cc899da08664637a8bc437308d3ddd7 3ccb419cf98083f3bb45808fba8dbc7c 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF