Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'okay, i'm having some issues' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
okay, i'm having some issues
Authored by: jodin on May 12, '01 01:35:57AM

i followed the directions exactly, and although there were some errors (the grant all command woudn't work) i managed to get it up and running and even run through the tutorial on webmonkey. then i went about trying to create a new database and something went wrong - now i can't even start the MySQL server!

the error i kept getting concerns a error message file buried deep in the english directory of mysql. here's the exact error:

010512 00:10:28 mysqld started

/usr/local/libexec/mysqld: Fatal error: Error message file '/usr/local/share/mysql/english/errmsg.sys' had only 194 error messages, but it should have at least 196 error messages.
Check that the above file is the right version for this program!

010512 00:10:28 mysqld endedn

okay, so here's what i did (don't get mad at me). after about 20 of those i reinstalled the package and then ran install from the CLI. i still got the error so i went in and deleted the offending file and reinstalled again. then when running safe_mysqld & i was getting an error :

010512 0:25:58 Can't start server: Bind on TCP/IP port: Address already in use

just for the hell of it i deleted that messagefile again and tried to start server again. this time i got the obvious:

/usr/local/libexec/mysqld: Fatal error: Can't find messagefile '/usr/local/share/mysql/english/errmsg.sys'

at this point i reinstalled again and am getting

010512 0:45:39 Can't start server: Bind on TCP/IP port: Address already in use

but i can't find the server running.

PLEASE HELP! i'm obviously a newbie with this and not getting a good grasp on what i'm doing wrong.


[ Reply to This | # ]
fixed it!
Authored by: jodin on May 13, '01 10:54:33PM

okay, got it. i had to go in and do a rude kill (kill -9 pid) to get the other SQL process stopped. once that was done i could fire it right back up! i guess the error about the incorrect errorlog size is gone, so who cares!

[ Reply to This | # ]