On Jan 23, 2008 6:45 AM, <[EMAIL PROTECTED]> wrote: <snip>
> > ls -al /var/lib/mysql > > drwx------ 2 mysql mysql 1752 Jan 22 15:55 mysql > drwx------ 2 mysql mysql 48 Jan 22 15:55 test > > It struck me odd that /var/lib/mysql has another directory inside with > the same name... but that was how the previous install looked as well. > Yeah - the sub-dirs under /var/lib/mysql are the individual named database schemas, and mysql uses the "mysql" schema to store the info about users, databases, privileges, etc., which brings us to the next point: > > Also, what do you get in the MySQL console if you do a: > > show databases; > > mysql> show databases; > +--------------------+ > | Database | > +--------------------+ > | information_schema | > +--------------------+ > 1 row in set (0.03 sec) This is *very* abnormal. You should have *at least* seen 3 items: information_schema, mysql, and test. The fact that nothing but the "meta" database shows up (AFAIK, information_schema isn't actually a DB in MySQL, it's just metadata about the server - kind of like the /proc filesystem in *nix). So, this leads me to think that maybe the MySQL service had not been restarted since the last time you emerged mysql? This would explain why cleaning the log dir and then restarting MySQL fixed it... > > > Also, try doing the create database procedure as previously outlined, > > then do a tail -n100 /var/log/mysql/mysql.err and > > /var/log/mysql/mysqld.err and /var/log/mysql/mysql.log - anything > > relative showing up in there? Maybe post the output of the above > > commands, as well as (tbz2'd, if they're large) attaching the > > /var/log/mysql/* files - might help us track this down... > > My first impulse was to look there as well but strangely nothing was > being written about those errors. So in response to your post I > thought I would clean out those logs with rm -f /var/log/mysql/my* > > Then restart mysql. > > Surprisingly after doing those steps. It now works. > > Apparently you've backhandedly fixed it simply with a request for > information... : ). Heh. Stranger things have happened, but not *too* much stranger... ;) > > Now smooth as silk: Awesome, glad it's working for you! > > Reminds me of a comment a neighbor made yrs ago. > > I was a sort of neighborhood fixit guy. Pretty handy with my hands > from a lifetime of bluecollar work and being raised as a kid in the > country. > > Neighbors would call me when their fixit chores got out of there > league. This one neighbor, on having me come over for an electrical > problem, swore things at his house started just working when he called > me to come over... said they'd see me coming and just know they'd have to > work shortly. > > That appears to be what happened here. Yeah, I've seen that happen quite a bit with computers - someone is having a problem (consistently, too), they call in the computer tech, and it starts working perfectly as soon as the tech is there... :) A hypothesis of mine is that (at least some of the time), as soon as the computer tech is there, and asking to see the problem duplicated, the user focuses more on what they are actually doing, and in doing so, performs the action in the correct manner... Possibly... :) -James -- [email protected] mailing list
