CentOS 4.3 + ASL = mysql dies...?

[TheEniGMa]

Have done some test installs of CentOS 4.2 + PLESK + ASL a few months ago, and they worked perfect. Now, trying to make a fresh install of CentOS 4.3 the exact same way makes mysql die and unwilling to start again.

CentOS 4.3 Minimal install
yum update
PLESK 7.5.4 (build 75060322 for RHEL4)
(adding ASL channel into yum.conf)
yum update (installing ASL kernel)

Everything works fine up till the latest step. Before installing ASL kernel, mysql can be restarted, PLESK works and so on. After ASL a "service mysqld restart" result in:

Code: Select all

[root@tux00 admin]# /etc/rc.d/init.d/mysqld start
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL:                                            [FAILED]

Code: Select all

/var/log/messages:
May 29 12:20:39 tux00 mysqld: Stopping MySQL:  failed
May 29 12:20:56 tux00 mysqld: Starting MySQL:  failed

Code: Select all

/var/log/mysqld.log:
060529 12:23:01  mysqld started
060529 12:23:01 [ERROR] bdb:  unable to initialize mutex: Function not implemented
060529 12:23:01 [ERROR] bdb:  process-private: unable to initialize environment lock: Function not implemented
060529 12:23:01  InnoDB: Started; log sequence number 0 450034
060529 12:23:01 [ERROR] Can't init databases
060529 12:23:01 [ERROR] Aborting

060529 12:23:01  InnoDB: Starting shutdown...
060529 12:23:04  InnoDB: Shutdown completed; log sequence number 0 450034
060529 12:23:04 [Note] /usr/libexec/mysqld: Shutdown complete

060529 12:23:04  mysqld ended

Haven't seen any other services that might have been affected by ASL, but I haven't really looked for it either...

However, it sems like mysql works up untill you do a restart connect (or stop/start). After ASL install and rebbot mysql starts and PLESK is accessable up untill I execute "service mysqld restart" from prompt...

Fresh install, no other things done when testing this.

Any idea what this can be?

[scott]

why does that error message seem so disturbingly familiar.

[TheEniGMa]

Did a little google-search on the error and found out that I caould simply put:

skip-bdb

under the [mysql]-directive and mysql starts up just fina again. It also seams like skip-bdb wouldn't do any harm for customers / mysql performance as well so....?!