View Issue Details

IDProjectCategoryView StatusLast Update
0000869CentOS-4myqslpublic2013-03-23 14:01
Reporteruser307 
PrioritylowSeverityblockReproducibilityalways
Status closedResolutionsuspended 
Platformx86OSCentOSOS Version
Product Version4.0 (Final) - i386 
Target VersionFixed in Version 
Summary0000869: MySQL fails to start on fresh install - can't init databases
DescriptionMySQL fails to start on a fresh install.

[root@scrapy mysql]# /sbin/service mysqld start
Initializing MySQL database: [ OK ]
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL: [FAILED]

RPMs installed:
mysql-4.1.7-4.RHEL4.1
mysql-devel-4.1.7-4.RHEL4.1
mysql-server-4.1.7-4.RHEL4.1

/var/log/mysqld.log :
050318 19:24:24 mysqld started
050318 19:24:24 [ERROR] bdb: unable to initialize mutex: Function not implemented
050318 19:24:24 [ERROR] bdb: process-private: unable to initialize environment
lock: Function not implemented
050318 19:24:25 InnoDB: Started; log sequence number 0 43634
050318 19:24:25 [ERROR] Can't init databases
050318 19:24:25 [ERROR] Aborting

The problem is something is wrong with the BDB storage engine in MySQL.

A workaround is to start MySQL using 'mysqld_safe --skip-bdb'.
TagsNo tags attached.

Activities

user239

2005-03-22 10:49

  ~0002515

Last edited: 1970-01-01 00:00

Which CPU are you using?

user307

2005-03-22 13:35

  ~0002516

Last edited: 1970-01-01 00:00

[steve@scrapy ~]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 5
model : 4
model name : Pentium MMX
stepping : 3
cpu MHz : 233.940

user309

2005-03-23 16:09

  ~0002517

Last edited: 1970-01-01 00:00

I am having this issue as well, it is related to BDB Disable posix-mutex/NPTL
support, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91933

[root@linux ~]# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 8
model name : AMD-K6(tm) 3D processor
stepping : 12
cpu MHz : 414.042
cache size : 64 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
bogomips : 819.20
kbsingh@karan.org

kbsingh@karan.org

2005-04-05 22:13

administrator   ~0002518

Last edited: 1970-01-01 00:00

is it possible for one of you, with an i586 machine, to rebuild the bdb rpm (
http://mirror.centos.org/centos/4/os/SRPMS/libdbi-0.6.5-10.RHEL4.1.src.rpm ) on
the local machine, install and test again ?

user307

2005-04-06 13:33

  ~0002519

Last edited: 1970-01-01 00:00

Rebuilt libdbi and installed the new libdbi-0.6.5-10.RHEL4.1.i386.rpm
libdbi-dbd-mysql-0.6.5-10.RHEL4.1.i386.rpm

MySQL still fails to start:

050406 09:27:16 mysqld started
050406 9:27:17 [ERROR] bdb: unable to initialize mutex: Function not implemented
050406 9:27:17 [ERROR] bdb: process-private: unable to initialize environment
lock: Function not implemented
lotsofgadgets

lotsofgadgets

2005-06-01 14:56

reporter   ~0002624

I have the same problem with a fresh install of CentOS4 in a ViaC3 mini-itx Motherboard:
[root@canit ~]# cat /proc/cpuinfo
processor : 0
vendor_id : CentaurHauls
cpu family : 6
model : 7
model name : VIA Samuel 2
stepping : 3
cpu MHz : 400.131
cache size : 64 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu de tsc msr cx8 mtrr pge mmx 3dnow
bogomips : 788.48


Tail of /var/log/mysqld.log

050531 21:32:46 mysqld started
050531 21:32:46 [ERROR] bdb: unable to initialize mutex: Function not implemented
050531 21:32:46 [ERROR] bdb: process-private: unable to initialize environment lock: Function not implemented
050531 21:32:46 InnoDB: Started; log sequence number 0 43634
050531 21:32:46 [ERROR] Can't init databases
050531 21:32:46 [ERROR] Aborting

050531 21:32:46 InnoDB: Starting shutdown...
050531 21:32:49 InnoDB: Shutdown completed; log sequence number 0 43634
050531 21:32:49 [Note] /usr/libexec/mysqld: Shutdown complete

050531 21:32:49 mysqld ended
timj

timj

2005-08-09 21:45

reporter   ~0002744

The (correct) workaround in the original report can be implemented in a slightly easier way by adding "skip-bdb" to the "mysqld" section of /etc/my.cnf, which then allows MySQL to be started/stopped as normal using "service mysqld start/stop".
rstory

rstory

2005-10-03 17:21

reporter   ~0002815

I just got hit with this too, CentOS 4.1. There seems to be a simple spec change that fixes this, mentioned in the redhat bug report. Seems like such a minor change should be able to be pushed out in updates...

$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : AMD Athlon(TM) XP 2400+
stepping : 1
cpu MHz : 2003.330
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
tigalch

tigalch

2013-03-23 14:01

manager   ~0016877

CentOS4 is EOL

Issue History

Date Modified Username Field Change
2005-03-22 10:49 user239 CC => falcon@rasterburn.com
2005-03-22 10:51 kbsingh@karan.org Component Missing Component => MySQL
2005-03-23 16:09 user309 CC => jeremy@techgooroo.net
2005-04-05 22:13 kbsingh@karan.org Status NEW => ASSIGNED
2005-06-01 14:56 lotsofgadgets Note Added: 0002624
2005-08-09 21:45 timj Note Added: 0002744
2005-10-03 17:21 rstory Note Added: 0002815
2013-03-23 14:01 tigalch Note Added: 0016877
2013-03-23 14:01 tigalch Status assigned => closed
2013-03-23 14:01 tigalch Resolution open => suspended
2013-03-23 14:01 tigalch Fixed in Version --- =>