Hello.
What is in error log? See:
http://dev.mysql.com/doc/mysql/en/starting-server.html
As I said, I couldn't find any error logs that seemed to relate (i.e, had information newer than the upgrade and start failures). I looked into the /etc/init.d/mysql script and tried running mysqlmanager directly. It would not run because of errors. From another message in this newsgroup, I saw that someone else was having similar problems and that removing the items from the [mysql] section of my.conf took care of them. That's what I did, and then the server started. From what I can tell, this appears to be a bug because the [mysql] section should have no affect on the server process and should not prevent mysqlmanager from running.
John Swartzentruber <[EMAIL PROTECTED]> wrote:
I was rash and decided to try to upgrade from 4.1 to 5.03 on my home
server. This isn't a critical system, but I am working on a class
project on it. Yup, I'm a newbie.
I'm running Fedora Core3. I did an "rpm -ivh" for each of the
appropriate RPMs (server, client, devel, bench, shared). For the
"shared" I did a --force because there is no shared-compat for 5.03.
Anyway, it looks like everything installed, but now, when I do
/etc/init.d/mysqld start, it tries for awhile, then fails.
I'm not sure where to look to figure out this problem. I don't see any
log files, and there are no error messages. Can anyone please get me
pointed in the right direction? If I can't figure this out soon, I'll
need to try to get 4.1 working again.
Thanks for your help.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
