Page 1 of 1

Fresh install of mysql 4.1 on windows 2k3 server...issues

Posted: Wed Sep 28, 2005 2:25 pm
by Burrito
I just configured a new windows 2k3 server and installed mysql 4.1. I wasn't having any problems until I migrated all of the data over from my old server to the new and then tried a select off of the "new" database.

here's the kicker:

if I go to the command line and "use %database%" to my new database then do "show tables", they pop right up. but if I try to "select * from %table%" from the new database, it dies a horrible death.

and here's where it gets even weirder, if I "use mysql" and then do "show tables" it dies a horrible death. I've repeated this pattern like 5 times to make sure that it wasn't a fluke...and indeed it's not.

another strange thing, I installed mysql as a service and when I try to restart the service, it just hangs on stopping, so I end up having to reboot the new server...total PITA.

any ideas what might be happening here?

thx,

Burr

Posted: Wed Sep 28, 2005 2:42 pm
by Burrito
Update:

ok, I have now figured out that php is the culprit in here somehow. When I do a fresh reboot and go to the command line mysql utility, I can select or do whatever I want, but as soon as I try doing anything from php, then go back to the cli, I have the issues I had before. I am now killing the mysql-nt process from the task manager to "stop" the service, then net starting it back up.

what's weird though is that I created all of the tables on my new database with phpMyAdmin so clearly php and mysql were jiving before.

I'm going to try dropping the new database now and see if that makes any difference...but if you have any ideas as to what might be causing this problem, I'd love to hear them.

thx,

Burrito

EDIT:

rather than create a new post, I'll update here:

everything seems to be in order now. Here's what I ended up doing:

first I uinstalled and reinstalled mysql, no luck

then I remembered that I read somewhere an issue similar to this where the solution was to drop the mysql database and run with it
I did that and everythign seemed to be working just right...however, that didn't sit well with me as I'm pretty sure the mysql db is sorta required for username p/word stuff, for for some VERY odd reason, it worked just like it should.

I then uninstalled mysql, and reinstalled it again, thereby readding the mysql db, I then granted all privileges to my new db user, fired it up, and whola! works like a peach.

this seems like a complete voodoo fix to me, and those of you who know me know how much I loathe voodoo fixes, but I'm going to just chalk this one up to black magic and let it be.

I'd still be interested in hearing if any of you have ever encountered such a problem and the way you fixed it...and I'd really like to remember where I read that dropping the mysql db is a solution so I can give props where props are due.

/EDIT