On Tuesday 13 April 2004 05:50, Radu Voicu typed:

Hi!

First of all, I have to remind you that expressions like "who is considering switching back to Debian..." won't help much (won't hurt, either, because we're all grown ups, not kids who's having a fight over who's toy is better)

Actually I was just sort of thinking out loud; but it is inappropriate for a non-Debian mailing list. I am sorry.

About your little issue - why I can *BET* that you altered (by hand or otherways) /etc/my.cnf and/or the directory /var/lib/mysql ??? I am waiting for confirmation of this and then we'll talk about it...

Yes, I altered it--to use InnoDB tables, because that's what the tutorial wants me to do.  IF you go in and check for yourself, you will see that SuSE has provided the necessary instructions for InnoDB tables already--in the #COMMENTS it says you are to "uncomment the following lines" for InnoDB table, and that is what I have done.  That's *ALL* I have done in that file...

Check out my config:

/etc/my.cnf [client] port            = 3306 socket          = /var/lib/mysql/mysql.sock

[mysqld] log big-tables log-error local-infile    = 1 port            = 3306 socket          = /var/lib/mysql/mysql.sock skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K myisam_sort_buffer_size = 8M

[SNIP] Mine is the same: here is the corresponding part of mine (corresponding to the part above:) # The following options will be passed to all MySQL clients [client] #password       = your_password port            = 3306 socket          = /var/lib/mysql/mysql.sock # Here follows entries for some specific programs # The MySQL server [mysqld] port            = 3306 socket          = /var/lib/mysql/mysql.sock skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K myisam_sort_buffer_size = 8M ...And so on and so forth. NOW, however, here is the part that I modfied: as you can see, all I did was to modify these lines by removing the "#" symbols, and I changed a couple of the values for the memory sizes, according to what the Tutorial said. It said you could use "this" value if you had as much as 128 megs of RAM (and I have 256 MB). So, I felt safe in doing so, and it did work fine: # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /var/lib/mysql/ innodb_log_arch_dir = /var/lib/mysql/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 70M innodb_additional_mem_pool_size = 10M # Set .._log_file_size to 25 % of buffer pool size innodb_log_file_size = 20M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 The Tutorial left it up to us to modify the following if we wanted; I felt that it was sort of silly because it wouldn't allow you to actually make anything that worked! And I felt it would be better to get my database started as soon as possible, and learn as I go, while inputing the books I need to catalog: # Remove the next comment character if you are not familiar with SQL #safe-updates All this does is prevent you from deleting a critical database accidentally. Since I didn't even have a database that was even mildly important, I was not worried about it.

In order to work, you *HAVE* to be SURE that ALL the files within /var/lib/mysql are owned by mysql:daemon or mysql:root - it's a MUST!!!

Here they are: linux:/var/lib/mysql # ls -lia total 20558  234907 drwxr-xr-x    4 mysql    daemon        488 2004-04-13 20:43 .      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       3040 2004-04-13 20:43 linux-slow.log  238969 drwx------    2 mysql    root          528 2004-03-28 18:13 mysql  262556 -rw-rw----    1 mysql    root          898 2004-04-13 20:43 mysqld.log  262521 -rw-rw----    1 mysql    root          194 2004-04-08 03:27 mysqld.log-20040408.gz  262568 -rw-rw----    1 mysql    root          188 2004-04-08 12:14 mysqld.log-20040409.gz  251154 -rw-rw----    1 mysql    root          477 2004-04-11 01:37 mysqld.log-20040411.gz  247414 -rw-rw----    1 mysql    root          358 2004-04-12 11:33 mysqld.log-20040412.gz  247391 -rw-rw----    1 mysql    root          491 2004-04-13 01:19 mysqld.log-20040413.gz  238970 drwx------    2 mysql    root           48 2004-03-28 18:13 test linux:/var/lib/mysql #

you can check it with ls -lia /var/lib/mysql and repair it entering the following command: chown -R mysql:daemon /var/lib/mysql

Looking for your *PERTINENT* comments...

Well, I cannot think of anything else at the moment; thanks for emphasizing these things, because although they're correct (they have no problems), I wouldn't have necessarily thought of checking them.  Especially the part about how those /var/lib/mysql files must be owned by mysql:daemon or mysql:root.  But, they are...and my /etc/my.cnf file is OK, which I already knew, because I had already worked up to chapter 6 in the tutorial book the other day, creating example InnoDB tables and such; and this would not have worked, apparently, if that my.cnf file was NOT set up properly.  And I knew that I had not changed anything important...that's why I felt that what I said WAS "pertinent".  I had said that it had been WORKING, just fine, and now the daemon won't start--there IS NO socket without a running daemon!  This is something that I did not know yesterday, and it is WHY I get the error message that I get: markvii@linux:~> mysql -u pampaluz -p Enter password: ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/ mysql/mysql.sock' (2) markvii@linux:~>su Password: linux:/home/markvii # rcmysql start Starting service MySQL                                  failed linux:/home/markvii # rcmysql status Checking for service MySQL:                                                             unused linux:/home/markvii # You see?  And if I go and try to "Enable" MySQL in the Runlevel Editor in YAST, it hangs for a few seconds, and then tells me that it "FAIL"s.  And at the suggestion of someone one time, I un-installed EVERYTHING, and re-installed (all the MySQL, and Apache, and php, and all of that), and re-installed it, and that's when it began working enough for me to get up to chapter six in the Tutorial book I am following, but now I am back where I started--what is wrong?  Do you see why this is really bothering me?  The only solution that has really worked so far, is to uninstall everything, delete my /var/lib/mysql (which kills any database I may have been working on), and then start over.  Is this how people are using MySQL?  If I seem upset then I'm sorry; but if someone is going to try and help me, it would useful if they would actually listen to the question, and see how I have already tried typing "rcmysql start" at the root prompt, instead of telling me that this is the solution, because it is not. Thanks, if you have read this far, and I especially thank you if you can see a way to help me out with this...someday I may be there to help you out; I am generous to a fault (but it would have to be something I could do; like typing a lot of stuff that you don't want to have to type up yourself; I am bedridden, and have a lot of time on my hands...) Thanks again, --Mark Seven Smith pampaluz@cox.net