I get an error when I'm trying to initialize the database using mysql_install_db:
Didn't find /usr/libexec/mysqld

Indeed, there is no mysqld or mysqld_safe on my whole filesystem. Wondering if anyone who got mysql running can tell me what they did.

Thanks

If you installed mysql using the standard Fedora rpm install and if you are running Gnome , you should have access to it through the Systems Settings->Server Settings->Services dialog. Start the service from there and then run the client as normal to set up db's etc.

Worked like a charm for me.

bl

That did it. That Services gui makes it very easy.

I've been puttering around in MySQL for an hour or two. The client connects to the server fine. However, when I rebooted, during the startup messages I see "timeout error occurred trying to start MySQL Daemon" and then MySQL <failed > over on the right side (normally get <OK> for other daemons).

Yet, after booting is finished, I open up a terminal and enter "mysql" and I connect to the server fine. So what's up with that error message during boot? Since I enabled mysqld via the Services gui, I don't really know where to look to troubleshoot this.

I get the same failed message on startup, but mysql is up and running fine for the test site I put up. I officially have a LAMP installation now. I'm a happy boy.

I don't know why the daemon returns a [FAILED] at startup, but there are some elements of the mysqld daemon such as InnoDB that are not setup out of the box.

As root, try looking at the mysqld log files in /var/log. Either with an editor or whatever suits, examine mysqld.log or mysqld.log.* . That might provide some insight.

If you post the log contents here, or on any mysql forum, someone should be able to help interpret them.

Hope this helps!
bl

you were right on the money blaroe. Here's a snip from mysqld.log.1

031213 21:52:57 mysqld started
Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
If you do not want to use transactional InnoDB tables, add a line
skip-innodb
to the [mysqld] section of init parameters in your my.cnf
or my.ini. If you want to use InnoDB tables, add to the [mysqld]
section, for example,
innodb_data_file_path = ibdata1:10M:autoextend
But to get good performance you should adjust for your hardware
the InnoDB startup options listed in section 2 at
http://www.innodb.com/ibman.html
/usr/libexec/mysqld: ready for connections

I'm going to check out the info at innodb.com, but if you have any further comments, I'd appreciate them too. Thanks!

That may not be causing the initialisation to fail, but you're on the scent. Normally any critical errors would show up in mysqld.log (I think!) Keep us posted on progress.

If this doesn't solve the init problems, maybe you could check with forums focused on mysql - one I know of is http://www.blogomania.com/forums/.

Good luck!
bl

My mysqld.log file is totally empty, but has the same timestamp as mysqld.log.1 (this morning, 4:02 am).

I don't know exactly how the mechanics of logging work, but I'm guessing that the contents of mysqld.log was copied over to mysqld.log.1 at that time.

I show the exact same Innodb error in my logs. As MySQL is running ok, I'm not too concerned about it, but I'd be curious to see if it speeds my test sites up any. Probably not as the box is running on 128 meg right now (old box and can't come by any cheap ram for it) but worth a try just to see.

I noticed the same startup problems only after I assigned a password to the mysql root user. The problem is in the mysqladmin ping command in the mysql startup script, it apparently doesn't work after assigning the root user a password. So I modified the script and in the mysqladmin ping commands added the "-u root -p 'password' " and the script works fine now. Thats not the best solution but does seem to work.

Craig

I have the same prolbem, only happens after i put in a root password.

so that will fix it hey ? where is the file to edit on the system please.


TT

I know it'll be a little late for this but instead of using the 'root' user in the mysqld init script you can use any other user wich is not in the database just think of one

You can replace the line

if [ -n "`/usr/bin/mysqladmin ping 2> /dev/null`" ]; then
and
if !([ -n "`/usr/bin/mysqladmin ping 2> /dev/null`" ]); then

to:

if [ -n "`/usr/bin/mysqladmin ping -u mysqld 2> /dev/null`" ]; then

and

if !([ -n "`/usr/bin/mysqladmin ping -u mysqld 2> /dev/null`" ]); then

in the /etc/rc.d/init.d/mysqld file

This works for me!!