[root@server02 base]# rpm -Uvh psa-7.0.0-rh9.build040205.22.i586.rpm
Preparing... ########################################### [100%]

Trying to define super-server internet daemon type... xinetd
Trying to check if xinetd daemon is running... done
===> Reading /etc/psa/psa.conf ...

Making some checks before upgrading

Now BIND server shutting down...

Trying to stop BIND server... done
Trying to start BIND server... done

BIND server starts Ok.

Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Usage: /etc/init.d/mysqld start|stop|restart
Cannot start Mysql server

ERROR while trying to check Plesk Database version
Check the error reason, fix and try again

Aborting...

error: %pre(psa-7.0.0-rh9.build040205.22) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping psa-7.0.0-rh9.build040205.22
[root@server02 base]#[root@server02 init.d]# ls -al my*
-rwxr-xr-x 1 root root 5575 Feb 12 18:02 mysql
-rwxr-xr-x 1 root root 5575 Feb 18 10:25 mysqld
[root@server02 init.d]#How can I solve this?

service mysql status
service mysqld status

same output :)

<sprintserve> why don't youjust reinstall Mysql?
<mr-d> I already reinstalled mySQL
<mr-d> mysql-3.23.x didn't want to start though
<mr-d> I am now on MySQL 4.x
<mr-d> but mysql4 doesn't pass the 'Does MySQL work' Plesk-test :(

luckily, you can edit the post install shell script and tell it NOT to die when that error occurs... IT seems to do wonders.

Status doesn't excist, just shows the error. Plesk-7-install dies when it doesn't see what it wants to see.

[root@server02 log]# ps -aux | grep mysql
root 25259 0.0 0.0 3752 560 pts/1 S 15:08 0:00 grep mysql
[root@server02 log]# service mysqld restart
Stopping MySQL: [FAILED]
Starting MySQL: [ OK ]
[root@server02 log]# service mysqld restart
Stopping MySQL: [FAILED]
Starting MySQL: [ OK ]
[root@server02 log]# cat mysqld.log
040218 15:08:15 mysqld started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.18-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306
A mysqld process already exists at Wed Feb 18 15:08:18 CET 2004
[root@server02 log]#

this looks like something else is going on... you can contact me on icq, yaho, or aim... you can find them all by looking at my profile... I will try and help you as best as i can.

MySQL-3 downgrade succeeded... next ->
===> Upgrading MySQL Database from version 6.0 to 7.0
Trying to upgrade SQL database... done
Setting up locales... done
Trying to fix qmail aliases for mailman mail lists... done
Setting mailman to autostart... done
Trying to reconfigure proftpd... done


===> Upgrading FP Extension


===> Upgrading FP Extension
Trying to shedule license displaying for admin login... done

ERROR while trying to set proper permissions on virtual hosts dirs
Check the error reason, fix and try again

Aborting...


WARNING: post-install script of RPM package psa-7.0.0-rh9.build040205.22 execution
failed. As the the package psa-7.0.0-rh9.build040205.22 was registered in the RPM
database, you need to execute the following command before attempting
to reinstall the package:
rpm -e psa-7.0.0-rh9.build040205.22

error: %post(psa-7.0.0-rh9.build040205.22) scriptlet failed, exit status 1
[root@server02 base]#

I contacted bizness on MSN. He knows soo much about Plesk.

Well, every works now. He limited downtime for me :)