MySQL 5.1 install - daemon crashes

[zeltus]

This is a new thread based on my earlier one - I have tried deinstalling/reinstalling package MySQL but the mysqld daemon still crashes as fast as I can start it. mysqld_safe continually loops, which makes for fun and games trying to kill it off, but

#/usr/local/libexec/mysqld can be called direct... this throws out

zeltus# ./mysqld --user=mysql &
[2] 68492
[1] Exit 1 mysqld --user=mysql
jail0087# 080524 8:52:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
080524 8:52:38 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
080524 8:52:38 InnoDB: Started; log sequence number 0 46409
080524 8:52:38 [Note] Recovering after a crash using mysql-bin
080524 8:52:38 [Note] Starting crash recovery...
080524 8:52:38 [Note] Crash recovery finished.
080524 8:52:38 [Note] Event Scheduler: Loaded 0 events
080524 8:52:38 [Note] ./mysqld: ready for connections.
Version: '5.1.20-beta-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-5.1.20
[2] Done ./mysqld --user=mysql

Unfortunately, this is all I have achieved so far re diagnostics.. and other than telling me that mysqld died suddenly, I haven't got much else.

Can anyone else suggest what I might do now to get this up and running? I have no idea what I have to do to get mysqld to tell me why it is crashing... and it's all getting a bit frustrating. Sigh.

Cheers

Bill

[zeltus]

Well, I sorted it in the end... I had to de-install MySQL and reinstall it.. I re-make'd it from scratch, but with an extra option

zeltus# cd /usr/ports/databases/mysql51-server
zeltus# make deinstall
zeltus# make -DWITH_PROC_SCOPE_PTH=yes -DBUILD_OPTIMIZED=yes
zeltus# make install clean

And thereafter all was/is well. So far.

BUILD_OPTIMIZED is a bit of a red herring, it had no impact on this problem, but hey! it looked like a good idea to include it.

Dunno why PTHREADS needs to be included but again, on reflection, it seems to be a a good idea (the other thread option was for a LINUX set up and I run FREEBSD, so out of the three available options, the default of NONE fails with an immediate crash, the LINUX threads option looks to be inapplicable and thus I was left with this option.) Which as I said, seems to have worked. So far. I shall watch it like a hawl for a few days, methinks.

Cheers

Bill