Cannot start MySql

Next topic

Author	Message
Brian Smith	Monday 08 September 2003 9:15:22 pm I have an existing version of MySql on My Windows machine and I have installed the Windows 95/98/ME Installer version of eZ Publish. While the installation was running I realized it was installing another version on MySql in C:\Program Files\eZ systems. I let the installation finish and uninstalled it. Now I am unable to start MySql. I get the error messages "C:\MYSQL\BIN\MYSQLD~1.EXE: Can't change dir to 'C:\Program Files\eZ systems\mysql\data' (errcode: 2)". Does any one have any ideas how to fix this?
Jeroen van Gorkum	Wednesday 10 September 2003 7:22:23 am the mysql daemon (MYSQLD~1.EXE) tries to switch to its data directory, but can't because you uninstalled that. it's possible (i think) to have two mysql servers installed on one machine, as long as only one is running. so, the easiest solution to your problem may be to uninstall the Windows 95/98/ME Installer version of eZ Publish completely, and re-install it again (including MySQL). just be sure to stop your `own' (first) mysql server when you're using ez publish. jeroen.
Brian Smith	Wednesday 10 September 2003 12:28:15 pm Thanks Jeroen for your reply. I tried that and every combination of install/unistall of the two MySql servers. In all cases, the Mysql server on my C: drive tries to point to C:\Program Files\eZ systems. It sounds to me that a registry entry from the install is not cleaned up during the uninstall. At this point I can't use my development MySql server which is a real problem.
Jeroen van Gorkum	Thursday 11 September 2003 10:28:32 am (it's more complicated in real life, as usual.) AFAIK, mysql doesn't store runtime configuration settings in the windows registry; when the server starts, it looks for a unix style configuration text file (in this order): C:\%windowsdir%\my.ini C:\my.cnf so, what's probably happening at the moment is that your development server finds the ez publish configuration file. configuration settings that affect your situation are: `-h' or `--datadir=path'; tells the server where the databases are. `-b' or `--basedir=path'; tells the server where to start looking for other files it needs. these settings can be supplied on the command line when you (or a windows shortcut or service) start the mysql server, or stored in one of the above configuration files. you can also specify a configuration file to use when you start the server. example configuration files are in the mysql directory. type `mysqld -?' on the command line in a mysql\bin directory for available options, and to see what the current configuration for the server is. and last but not least: windows explorer (w2k file manager) seems to think my C:\my.cnf is a file of type 'SpeedDial', and that it isn't necessary to show the `.cnf' extension. it won't connect to a pornsite, though, but actually is the mysql configuration file (`dir' on the command line shows the .cnf extension). hth, jeroen.
Carl Albrecht	Thursday 01 April 2004 12:51:37 am I have a very similar problem except that, I had uninstalled eZpublish a couple of days ago and thought I'd have a go at running Apache2/php/mysql. I'm having problems with the install of mysql though, I've put a new my.ini file into the WINNT folder from the mysql zip file, and ran the command "C:\>mysqld-nt --install" but get the response "The service already exists! The current server installed: c:\eZpublish\mysql\bin\mysqld-nt.exe". But.... hang on...eZpublish directory doesnt exist, it hasn't for a couple of days and several reboots. So my question is, how do I clean up after eZpublish uninstall, and how does the mysqld-nt.exe recognise that path when it doesnt exist and wasnt unzipped untill well after the uninstall of eZpublish?
Carl Albrecht	Thursday 01 April 2004 11:57:22 am err...never mind..found the problem of my previous post and fixed it. I done a search through the Regedit for eZpublish, and modified the paths I found (several) by taking out the non-existant eZpublish directory in the path. Everything worked smoothly after that. This may help with some of the other posts in this topic, but dont quote me on that, you edit the registry at <b>your own risk.</b> Someone may want to make a note of this in the FAQ for future reference, that is if anyone actually reads this. BTW, I didnt uninstall eZpublish because I didnt like it, as a matter of fact I thought it was great, a few bugs and very thin documentation on how to use it, but other than that. My intention from the start was only to take it for a test drive because it was fairly new. Carl