• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Mysql 4.x upgrade failed

D

durodata

Guest
I tried to upgrade my mysql server from the instructions on ART, but unfortunately it didn't complete successfully


instructions


Any way how to fix it?


[root@www admin]# rpm -e MySQL-Max MySQL-server MySQL-client MySQL-shared-compat --nodeps
error: package MySQL-Max is not installed
error: package MySQL-server is not installed
error: package MySQL-client is not installed
error: package MySQL-shared-compat is not installed
[root@www admin]# yum install mysql-server mysql mysql-compat
Gathering header information file(s) from server(s)
Server: Atomic Rocket Turtle - 3ES - Atomic PSA-Compatible RPMS
Server: Atomic Rocket Turtle - 3ES - Atomic Desktop
Server: Atomic Rocket Turtle - 3ES - Base OS RPMS mirror
Server: Atomic Rocket Turtle - 3ES - Project Gamera
Server: Atomic Rocket Turtle - 3ES - SW-Soft PSA 7.0 RPMS
Server: Atomic Rocket Turtle - 3ES - SW-Soft PSA 7.1 RPMS
Server: Atomic Rocket Turtle - 3ES - SW-Soft PSA 7.5 RPMS
Server: Atomic Rocket Turtle - 3ES - OS Update RPMS mirror
Finding updated packages
Downloading needed headers
mysql-devel-0-4.0.24-1.rh 100% |=========================| 6.6 kB 00:00
mysql-0-4.0.24-1.rhel3.ar 100% |=========================| 12 kB 00:00
mysql-server-0-4.0.24-1.r 100% |=========================| 6.6 kB 00:00
mysql-compat-0-4.0.24-1.r 100% |=========================| 5.6 kB 00:00
Resolving dependencies
.Dependencies resolved
I will do the following:
[install: mysql-compat 4.0.24-1.rhel3.art.i386]
[update: mysql-server 4.0.24-1.rhel3.art.i386]
[update: mysql 4.0.24-1.rhel3.art.i386]
I will install/upgrade these to satisfy the dependencies:
[deps: mysql-devel 4.0.24-1.rhel3.art.i386]
Is this ok [y/N]: y
Downloading Packages
Getting mysql-devel-4.0.24-1.rhel3.art.i386.rpm
mysql-devel-4.0.24-1.rhel 100% |=========================| 652 kB 00:06
Getting mysql-server-4.0.24-1.rhel3.art.i386.rpm
mysql-server-4.0.24-1.rhe 100% |=========================| 1.4 MB 00:13
Getting mysql-4.0.24-1.rhel3.art.i386.rpm
mysql-4.0.24-1.rhel3.art. 100% |=========================| 7.5 MB 02:16
Getting mysql-compat-4.0.24-1.rhel3.art.i386.rpm
mysql-compat-4.0.24-1.rhe 100% |=========================| 243 kB 00:04
Running test transaction:
Test transaction complete, Success!
mysql 100 % done 1/7
mysql-compat 100 % done 2/7
mysql-devel 100 % done 3/7
mysql-server 100 % done 4/7
Completing update for mysql-devel - 5/7
Completing update for mysql-server - 6/7
packagemng: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
packagemng: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
packagemng: Unable to connect to the mysql database

System error 2: No such file or directory
packagemng: Unable to connect to the mysql database

System error 2: No such file or directory
error: %trigger(psa-7.5.2-rhel3.build75050130.17) scriptlet failed, exit status 1
Installed: mysql-compat 4.0.24-1.rhel3.art.i386
Updated: mysql-server 4.0.24-1.rhel3.art.i386 mysql 4.0.24-1.rhel3.art.i386
Dep Installed: mysql-devel 4.0.24-1.rhel3.art.i386
Transaction(s) Complete
[root@www admin]#
[root@www admin]# mysql --version
mysql Ver 12.22 Distrib 4.0.24, for redhat-linux-gnu (i686)
 
psa 7.5 added in some triggers that I havent had a chance to fully investigate yet. I suspect they're trying to populate the PSA database indicating what is installed/updated, and mysql is in the midst of restarting at the moment it does that. The installation as you noted however was successful
 
Do the above instuctions work with CentOS 3.4?
I have MySQL 4.0.23 installed with Plesk 7.5.2 and want to upgrade to 4.0.24...

What should my /etc/yum.conf file look like?

Currently this is my yum.conf:
Code:
[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
installonlypkgs=kernel kernel-smp kernel-hugemem kernel-enterprise kernel-debug kernel-unsupported kernel-smp-unsupported kernel-hugemem-unsupported
tolerant=1
exactarch=1

[base]
name=CentOS-3.4 - Base
baseurl=http://mirror.trouble-free.net/cAos/centos-3/3.4/os/$basearch/
gpgcheck=1
[update]
name=CentOS-3.4 - Updates
baseurl=http://mirror.trouble-free.net/cAos/centos-3/3.4/updates/$basearch/
gpgcheck=1
[addons]
name=CentOS-3.4 - Addons
baseurl=http://mirror.trouble-free.net/cAos/centos-3/3.4/addons/$basearch/
gpgcheck=1
[extras]
name=CentOS-3.4 - Extras
baseurl=http://mirror.trouble-free.net/cAos/centos-3/3.4/extras/$basearch/
gpgcheck=1
[psa-7.5]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.5 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.5/3ES/
baseurl=http://archive.atomicrocketturtle.com/atomic/psa-7.5/3ES/
baseurl=http://www.atomicrocketturtle.com/atomic/psa-7.5/3ES/

[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/art/3ES/
baseurl=http://archive.atomicrocketturtle.com/atomic/art/3ES/
baseurl=http://www.atomicrocketturtle.com/atomic/art/3ES/
[app-vault]
name=Atomic Rocket Turtle - $releaserver - App - Vault
baseurl=http://3es.atomicrocketturtle.com/atomic/app-vault/
baseurl=http://archive.atomicrocketturtle.com/atomic/app-vault/
baseurl=http://www.atomicrocketturtle.com/atomic/app-vault/

Thanks
 
We had a very serious problem with upgrading MySQL on Redhat 9.0

The auto-updater stopped on updating the MySQL and corrupted the enitre email system. SQL scripts worked fine but all emails responded with errors in outgoing and incoming emails. MySQL did not respond using putty, and playing around with qmail had no use either.

I am sure there is a problem with plesk and the latest version of MySQL.

The final solution resulted in us formatting the linux box, and re-installing the plesk system. It was a major problem, loss of data, and HUGE amounts of complaints from customers.

I will never use auto-update again..... and wish you all the best.
 
Back
Top