Thanks Bhavin,
I tried your suggestion ("safe_mysqld start") and get a lot of "Permission
denied" errors. So, I "su" to root and try it, and it appears that it does
start ("Starting mysqld daemon with databases from /usr/local/mysql/data").
However, when I try to connect, either as root (which I understand is not a
good idea) or under my normal login, I get the same error, i.e., that the
socket can't be found.
Very puzzling and I'm quickly approaching the point of concluding that the
amount of time trying to troubleshoot this mess not warranting the potential
benefits.
Colin
> Have you tried .../bin/safe_mysqld start to start the DB first? This is what
> will create /tmp/mysql.sock socket file & start the DB server. Then you can
> use the 'mysql' client for connecting to the DB. Also, if you don't want to
> use transactional database, meaning, if you don't want support for rollback
> and stuff, which I am guessing you might not, then you can download the
> 3.23.49 binary or rpm (not max) from the mysql.com site (instead of Marc
> Liyanage's site). Since it's giving errors regarding innodb, my guess is
> that the server is configured to create inno db tables and not myisam
> tables, which is what the default binaries/rpm are configured to do (i.e.
> create myisam tables, but they are non-transactional).
>
> Regards,
> Bhavin.
>
> ----- Original Message -----
> From: "Colin Cooler" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, June 09, 2002 3:55 PM
> Subject: Newbie MySQL installation problems (specific)
>
>
>> Buying Paul DuBois' most excellent book "MySQL" has made me more
> comfortable
>> with Mysql and Unix, so I thought I would try to use Mysql/PHP combo as
> the
>> web database for a redesigneed site at Right Moves For Youth (trying to
> keep
>> "at risk" kids in school).
>>
>> After running his "cleanup instructions" and then downloading and
> installing
>> the mysql package from Marc Liyanage's site, I tried to run the following
>> command (as per instructions):
>> "sudo ./scripts/mysql_install_db;" I then get the following results:
>>
>>> Preparing db table
>>> Preparing host table
>>> Preparing user table
>>> Preparing func table
>>> Preparing tables_priv table
>>> Preparing columns_priv table
>>> Installing all prepared tables
>>> ERROR: 1062 Duplicate entry 'localhost-root' for key 1
>>> ERROR: 1062 Duplicate entry 'localhost-root' for key 1
>>> 020609 0:35:05 ./bin/mysqld: Shutdown Complete
>>
>>
>> When I try to start mysql from the command line, I then get the ubiquitous
>> error message: "ERROR 2002: Can't connect to local MySQL server through
>> socket '/tmp/mysql.sock' (2) "
>>
>> I also discovered a "localhost.err" file in my data directory which yields
>> the following information:
>>
>>> 020609 01:09:50 mysqld started
>>> Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
>>> If you do not want to use transactional InnoDB tables, add a line
> skip-innodb
>>> to the [mysqld] section of init parameters in your my.cnf
>>> or my.ini. If you want to use InnoDB tables, add for example,
>>> innodb_data_file_path = ibdata1:30M
>>> But to get good performance you should adjust for your hardware
>>> the InnoDB startup options listed in section 2 at
>>> http://www.innodb.com/ibman.html
>>
>>> 020609 1:09:51 /usr/local/mysql-3.23.49/bin/mysqld: Can't create/write
> to
>> file '/usr/local/mysql-3.23.49/data/localhost.pid' (Errcode: 13)
>>> 020609 1:09:51 /usr/local/mysql-3.23.49/bin/mysqld: Can't find file:
>> './mysql/host.frm' (errno: 13)
>>> 020609 1:09:51 /usr/local/mysql-3.23.49/bin/mysqld: Error on delete of
>> '/usr/local/mysql-3.23.49/data/localhost.pid' (Errcode: 13)
>>> 020609 01:09:52 mysqld ended
>>
>> Finally, when I try the following: "mysqladmin -u root status" I also get
>> the "can't connect through /tmp/myssql.sock" error message.
>>
>>
>> No matter what I try, I can't seem to connect to mysql so that I can even
>> BEGIN to figure out how to correct the 1062 problem! Can anyone tell me
> how
>> to what the "ERROR: 1062" message means and how to resolve this mess?
> I've
>> searched the archives, and this error appears to have occurred
> occasionally,
>> but being a newbie to MySQL, I can't understand the solutions to the
>> problem. Usually this problem has occurred AFTER someone has been able to
>> successfully connect to mysql.
>>
>> Oh Woe is me,
>> Colin
>>
>>
>> ---------------------------------------------------------------------
>> Before posting, please check:
>> http://www.mysql.com/manual.php (the manual)
>> http://lists.mysql.com/ (the list archive)
>>
>> To request this thread, e-mail <[EMAIL PROTECTED]>
>> To unsubscribe, e-mail
> <[EMAIL PROTECTED]>
>> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>>
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
> <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
