Update mysql 4.1 to 5.1 fails

S

snaaps

Verified User
Joined
Jan 29, 2005
Messages
230
Location
Netherlands
Why can whe not update from 4.1 tot 5.1?
Its everytime the same problem but with different errors.

(note i reinstalled mysql now with ./mysql,sh in de script directory so its now back to 4.1)

The errors when tried to update:
PHP: 
[root@server26 custombuild]# ./build mysql
Found /usr/local/directadmin/custombuild/mysql/MySQL-client-5.1.50-1.glibc23.i386.rpm
Found /usr/local/directadmin/custombuild/mysql/MySQL-devel-5.1.50-1.glibc23.i386.rpm
Found /usr/local/directadmin/custombuild/mysql/MySQL-server-5.1.50-1.glibc23.i386.rpm
Found /usr/local/directadmin/custombuild/mysql/MySQL-shared-5.1.50-1.glibc23.i386.rpm
Stopping mysqld ...
Shutting down MySQL.                                       [  OK  ]
Upgrading MySQL 4.1 to 5.1
warning: MySQL-client-5.1.50-1.glibc23.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5
error: MySQL-devel-5.1.50-1.glibc23.i386.rpm: V3 DSA signature: BAD, key ID 5072e1f5
error: MySQL-devel-5.1.50-1.glibc23.i386.rpm cannot be installed
/etc/init.d/mysqld: line 173: my_print_defaults: command not found
Can't execute /usr/bin/mysqld_safe                         [FAILED]
Giving mysqld a few seconds to start up...
Restarting MySQL.
/etc/init.d/mysqld: line 173: my_print_defaults: command not found
/etc/init.d/mysqld: line 173: my_print_defaults: command not found
MySQL PID file could not be found!                         [FAILED]
/etc/init.d/mysqld: line 173: my_print_defaults: command not found
Can't execute /usr/bin/mysqld_safe                         [FAILED]
It is recommended to do "./build php n" after MySQL update.
[root@server26 custombuild]#

EDIT:
fix it with:
PHP: 
cd /usr/local/directadmin/custombuild
rm -f /usr/local/directadmin/custombuild/mysql/*
./build update
./build mysql


But, why are all joomla tabels like jos_core_acl_aro, jos_session are always corrupt after a upgrade from 4 to 5?
This happend every time when we update mysql, WHY?????:?
(and how to fix or better a soulition that this not happend)
 
Last edited:
Normally it should after upgrading an check to see if its corrupted, if so it repairs the table.
We have updated MySQL 4.x to MySQL 5.x without any problems.
 
Hi, the problems with the corrupt database is a problem issue from joomla below version 1.6 and its not a mysql update problem.

so whe have update mysql and after that whe restore the corrupt database with the user backups off directadmin.
 
You must log in or register to reply here.
Back
Top