mysqld-nt cannot start as service

Anon

Woke up this morning and mysqld-nt wouldn't start (I'm running Win2k). Uninstalled MySQL and then found that the service was still in the system. Tried mysqld-nt --remove and that returned an error. Reinstalled MySQL wihtout problems but still couldn't register it as a service with Win2k. Manual starts with either mysqld-nt and NET START mysqld-nt doesn't work either.

I'm resolving to mysqld-nt --standalone now. But I REALLY would like to know how to fix the problem. (It really frustrates me when you know that something on your system doesn't work, if you know what I mean).

Thanks!

p/s: I'm sorry to post a MySQL question on a PHP forum, but www.mysql.com doesn't seem to have one.

mithril

Ed,

Where have you installed MySQL? If it's anywhere other than c:\mysql, you need to copy the my-example.cnf to c:\ as my.cnf and specify the install directory to start as a server. For example, if you installed to e:\mysql, you'd add the following line:

  basedir = e:/mysql

it's also a good idea to specify the data directory like so:

  datadir = e:/mysql/data

A full listing of the MySQL command line arguments can be obtained by issuing mysql-nt --help. All those arguments can also be set in your my.cnf. HTH.

geoff

mithril

Damn typos!!!🙂

"start as a server" should read "start as a service"...... of course it's a server🙂
"issuing mysql-nt --help" should read "issuing mysqld-nt --help"

geoff

Anon

Well, like I mentioned before Geoff, MySQL was running fine in the past few days and its only this morning when I started my computer and it refused to run. I have it installed in the default directory.

Don't know what's wrong. I can't even remove the service now (oh, wait... I can! MySQL has just disappeared from the list of services on my machine, that is after I executed about 20 times worth of mysqld-nt --remove!).

Will reboot now and will post again if I can get it to be installed as a service once again.

Anon

mysqld-nt can't seem to start without using any additional parameters e.g. --standalone, --console, --safemode.

Any idea why? Really frustrating to see something that worked yesterday and break down today (without any changes to the system).