On Tuesday 13 April 2004 21:04, Anders Johansson typed:

On Wednesday 14 April 2004 05.55, Mark Seven Smith wrote:

...

So far, it will NOT run. Yet, I was able to do this, just the other day, and it DID RUN. Yet I haven't changed anything that I can remember...

You ran mysqld directly as root, but with incorrect parameters. This failed to start mysql but it did succeed in changing the ownership of some important files.

Try

chown -R mysql.daemon /var/lib/mysql

followed by "rcmysql start" and see if that helps

AAAAGH! *MAN*, I was hoping that would work...it sounded so *logical*! Here's the result: markvii@linux:~> su Password: linux:/home/markvii # chown -R mysql.daemon /var/lib/mysql linux:/home/markvii # rcmysql start Starting service MySQL failed linux:/home/markvii # Here's what my directory looks like now: (I showed what it looked like with this command before, in the previous Email): linux:/home/markvii # ls -lia /var/lib/mysql total 20558 234907 drwxr-xr-x 4 mysql daemon 488 2004-04-13 21:41 . 23 drwxr-xr-x 41 root root 1072 2004-04-13 04:31 .. 246711 -rw-rw---- 1 mysql daemon 25088 2004-03-28 18:13 ib_arch_log_0000000000 246708 -rw-rw---- 1 mysql daemon 10485760 2004-04-10 09:26 ibdata1 246709 -rw-rw---- 1 mysql daemon 5242880 2004-04-10 09:26 ib_logfile0 246710 -rw-rw---- 1 mysql daemon 5242880 2004-03-28 18:13 ib_logfile1 98547 -rw-rw---- 1 mysql daemon 3200 2004-04-13 21:41 linux-slow.log 238969 drwx------ 2 mysql daemon 528 2004-03-28 18:13 mysql 262556 -rw-rw---- 1 mysql daemon 1347 2004-04-13 21:41 mysqld.log 262521 -rw-rw---- 1 mysql daemon 194 2004-04-08 03:27 mysqld.log-20040408.gz 262568 -rw-rw---- 1 mysql daemon 188 2004-04-08 12:14 mysqld.log-20040409.gz 251154 -rw-rw---- 1 mysql daemon 477 2004-04-11 01:37 mysqld.log-20040411.gz 247414 -rw-rw---- 1 mysql daemon 358 2004-04-12 11:33 mysqld.log-20040412.gz 247391 -rw-rw---- 1 mysql daemon 491 2004-04-13 01:19 mysqld.log-20040413.gz 238970 drwx------ 2 mysql daemon 48 2004-03-28 18:13 test linux:/home/markvii # Everything's now the same owner and group. But it doesn't help. There must be something simple being overlooked; but I go through everything I can find; the SUSE manuals for MySQL, everything, but I cannot figure it out. There is a page about troubleshooting; but it doesn't have anything very much to do with things at this point--everything it suggests has been tried. This is so *FRUSTRATING*!!! Any ideas on what to do next? Pay SuSE for help? Wait for the SuSE 9.2 (or whatever) to come out? Just abandon all the work I've done, and re-install the entire system (I don't have a way to really back things up...) Or perhaps just toss the notebook computer into the swamp (if San Diego has a swamp) and become a TV vegetable? ;-) Where should I go next? I'd like to take some courses in Computer Science so that I can understand what's "going on underneath the hood" so to speak (as if the computer is a car), but I can't get out and about; my health is too poor. If I understood the kernel better, it seems to me that I would be able to fathom why such problems come up. Who would know enough about Linux to be able to say what's going on with my weird problems? I am probably going to un-install all the MySQL and php and Apache stuff and wipe the /var/lib/mysql directory out one more time; but then, if this happens again, I don't know what I will do. I just hate the idea of having to be stuck using vi to catalog all my books...I won't be able to do the things that I am trying to accomplish by using a relational, SQL-type database. Maybe PostgreSQL? But that'll be even worse, trying to start learning all over again... Thanks, --Mark VII --Mark VII

On Tuesday 13 April 2004 22:09, Jon Clausen typed:

On Tue, Apr 13, 2004 at 09:55:53PM -0700, Mark Seven Smith wrote:

<snip>

...

Here's what my directory looks like now: (I showed what it looked like with this command before, in the previous Email):

linux:/home/markvii # ls -lia /var/lib/mysql total 20558 234907 drwxr-xr-x 4 mysql daemon 488 2004-04-13 21:41 . 23 drwxr-xr-x 41 root root 1072 2004-04-13 04:31 ..

jon@a13:~> ll -d /var/lib/mysql/ drwxr-xr-x 6 mysql daemon 5280 2004-04-14 06:01 /var/lib/mysql/

Maybe?

OK, here's what mine says (it's the same, except for the 6, mine's a 4): linux:/home/markvii # ll -d /var/lib/mysql/ drwxr-xr-x 4 mysql daemon 488 2004-04-13 21:41 /var/lib/mysql/ [Continuing on...]

...

262556 -rw-rw---- 1 mysql daemon 1347 2004-04-13 21:41 mysqld.log

What's in this?

Here is my entire mysqld.log file. There are others, but they are compressed, and I think they are old... linux:/var/lib/mysql # less mysqld.log 040413 07:10:29 mysqld started InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 20971520 bytes! 040413 7:10:32 Can't init databases 040413 7:10:32 Aborting 040413 7:10:33 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 040413 7:10:33 /usr/sbin/mysqld-max: Shutdown Complete 040413 07:10:33 mysqld ended 040413 20:43:10 mysqld started InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 20971520 bytes! 040413 20:43:12 Can't init databases 040413 20:43:12 Aborting 040413 20:43:12 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 040413 20:43:12 /usr/sbin/mysqld-max: Shutdown Complete 040413 20:43:12 mysqld ended 040413 21:41:49 mysqld started InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 20971520 bytes! 040413 21:41:51 Can't init databases 040413 21:41:51 Aborting 040413 21:41:51 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 040413 21:41:51 /usr/sbin/mysqld-max: Shutdown Complete 040413 21:41:51 mysqld ended I do not understand those error messages; when I was doing the InnoDB exercises, they seemed to work just fine; I had no problems, and the databases all displayed their tables and such just fine. Even still, I should still be able to get stuff done, at least the Monitor should run! linux:/var/lib/mysql # /etc/init.d/mysql start Starting service MySQL failed linux:/var/lib/mysql # linux:/var/lib/mysql # rcmysql start Starting service MySQL failed linux:/var/lib/mysql # Note the time of this post: I've been sitting here all day, trying to figure this out. I am going in circles! It can't be so difficult; everything else works, so I don't think I have a hardware problem, but it *seems* like that, because nothing I try works (for MySQL)! Here is what happened when I first made MySQL work: ==================== /etc/init.d/mysql start returned 0 (success): Creating MySQL privilege database and starting MySQL... Preparing db table Preparing host table Preparing user table Preparing func table Preparing tables_priv table Preparing columns_priv table Installing all prepared tables 040328 18:13:15 /usr/sbin/mysqld-max: Shutdown Complete PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! This is done with: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h linux password 'new-password' See the manual for more instructions. You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory: cd sql-bench ; perl run-all-tests Please report any problems with the /usr/bin/mysqlbug script! The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at https://order.mysql.com ..done ==================== This was when I was able to begin making progress in the Tutorial, and get up to chapter 6. And yesterday I was still able to log in to the Monitor, and do things like "display databases;" and such as that. Of course, I cannot do any of the benchmark stuff, because I don't have the daemon running yet. There is a document, "/usr/share/doc/packages/mysql/README.SuSE" which tells where things *really* are in the SuSE 9.0 distribution. They're not where they're said to be in the MySQL manual. But I am aware of this, so this is not where the problem lies, either... Today, I am getting all these weird error messages, and MySQL will not let me load the daemon, just like before. And the only fix then was to wipe everything clean and start fresh. And I did. But now, I don't want to have to do that again. I think that is stupid, having to re-install every time I wish to use a database. But what else can I do? Thanks in advance... Best regards... --Mark VII

On Tuesday 13 April 2004 23:31, Radu Voicu typed:

Hi!

By typing your error message into Google, I was lead to the following result (two of them)

Dang! I thought I had exhausted all that I could do with Google! Guess not! Thanks...

"Solution This only works if you don't care about your innodb transaction backups! Although to get this error, InnoDB probably wasn't working in the first place.

Just move those log files to ib_logfile0.bak, ib_logfile1.bak, etc. and start mysql again.

why don't I just delete them?

Consequences

This solution is not elegant but it works. At least it worked for me because I didn't have any real data in the innodb tables anyways. INNODB stores all transactions in it's log files so by moving those, I probably erased all the backups of my transactions. If you have data you need to save, you'll have to get help from someone wiser than me. ;) "

Nope, don't need them, and don't care what they say...I had no useful data entered yet, because I was sure that I would lose it...

2nd result:

"Yes, do you have already the InnoDB data and log files and you are specifying a different size for them.

YIKES! The book said something about that, but I inferred that it meant if you had been using InnoDB databases before...I didn't realize that it applied to even if you had done *anything* before; and I did do the fixes to /etc/ my.cnf AFTER I ran "/etc/init.d/mysql start" for the first time (which initializes and performs some first-time tasks).

You should do:

1- if the older InnoDB files doesn't has important data for you, just delete them.

Good! I will.

2- if you need to preserve theses files them specify the correct size in your my.cnf/my.ini.

Nah--I'll leave it how the Tutorial told me to set it up.

3- If you don't use InnoDB, then specify skip-innodb in the configuration file."

Why would you want to do that? The ISAM database style has no foreign keys; How Can It Even Be Considered a "Relational Database Management System"? Answer: IT ISN'T! You *need* to have InnoDB if you want to do true relational databasing...

I just want to tell you this if you have to do forensics on your database, do this:

1. Back-up ALL your folder /var/lib/mysql, by copying it on your home directory, for instance (use mc to do this), also copy /etc/my.cnf 2. rpm -ev mysql 3. DELETE all the directory you backed up 4. reinstall mysql, execute the online update (by running the comand you) and start modifying /etc/my.cnf then rcmysql restart after EVERY line of modifications you do into it 5. be sure that you don't have /homedir/.my.cnf and/or /root/.my.cnf

This seemed pretty difficult at first, but I read through it, and it makes perfect sense now. I don't understand that last part of number 4; "by running the command you"? You mean the YAST Online Update (probably this).

P.S. Please send me a copy of your mysql manual (the one you are using for innodb and to learn mysql)

Now that would be difficult; I purchased it at Borders: http://tinyurl.com/2bdpm (This is an Amazon.com link). the book is really for rank beginners; I can send it to you once I am through with it (which ain't ever gonna happen unless I get past this dang daemon problem! ) Otherwise, you are welcome to it when I am done...which should be fairly quick. It really is a nice book for beginners, it has a "crash course" in relational databases (chapter three) and it goes rather quickly, with no real "troubleshooting" area in the back or anything like that; it just gets you going on having a working database system set up with InnoDB and I don't know what else--but I paid something like $35 dollars for it, and although I really need it, I wish it had more (for the money). But, if I use it, and then you get to use it, and then maybe it helps others...then what the heck? Like I say, it makes it all very easy (I looked into a lot of other MySQL books, and they went into far too much detail; too much for me to be able to deal with. I would never be able to make any progress through them, trying to cope with all the stuff they throw at you!) Anyway, thanks for your assistance; I think that it is going to work now. It is too late I think to try these things today; but I'll be getting back to it tomorrow. Best regards, and thanks again, --Mark VII -- "The world around us is very mysterious. It doesn't yield its secrets easily. As long as you feel that you are the most important thing in the world you cannot really appreciate the world around you. You are like a horse with blinders, all you see is yourself apart from everything else." -- "Journey To Ixtlan", Carlos Castaneda ------ Mark Seven Smith -- pampaluz@cox.net -- AIM & /. == Pampaluz Free Software Foundation (www.gnu.org) Member #1372 Pampaluz Linux Counter #122264 - http://counter.li.org/

On Tue, Apr 13, 2004 at 11:17:18PM -0700, Mark Seven Smith wrote:

...

...

23 drwxr-xr-x 41 root root 1072 2004-04-13 04:31 ..

jon@a13:~> ll -d /var/lib/mysql/ drwxr-xr-x 6 mysql daemon 5280 2004-04-14 06:01 /var/lib/mysql/

Maybe?

Not. Sorry for the static... I misread ".." for "." in your output... :P Nice that you got it going though... /Jon -- Whatever rocks your boat!