Fatal error: Can't open privilege tables: Can't find file:
'./mysql/host.frm' (errno 13) ...
 
Well, since I failed to use RPM to install MySQL 4.0 over 3.23 -- I am
not sure if I have to unstall the latter before I install the former,
the manual does not mention that, I went ahead to do a fresh binary
installation of it on my Linux 7, under usr/local/ directory.  Followed
the manual step by step until I started the server:
/bin/mysqld_safe & (also tried it with parameter user=mysql),
but I got "mysql ended ... [1]+ Done    ./bin/mysqld_safe" msg,
 
and I could not run any further commands, failing with msgs like "Can't
connect to local MySQL server though socket '/tmp/mysql.sock', Check
that mysqld is running and that the socket: '/tmp/mysql.sock' exists!"
 
then I found in the sql log file: "Fatal error: Can't open privilege
tables: Can't find file: './mysql/host.frm' (errno 13) ..." when
starting the InnoDB tables.
 
Both files mysql.sock and host.frm are not mentioned in the manual, and
not found in my file system.
 
Any one can point out the problem?
 
Thanks.

        -----Original Message-----
        From: Zhao, Charles 
        Sent: Tuesday, January 06, 2004 4:53 PM
        To: '[EMAIL PROTECTED]'
        Subject: MySQL 4.0 Installation Problem
        
        
        I have 3.23 that comes with my Linux distribution, now when I
tried to do a rpm installation of 4.0, I got messages like:
        "warning: MySQL-server-4.0.17 ... .rpm: V3 DSA signature: NOKEY,
key ID ...,
        file /usr/bin/mysql from install of MySQL-client-4.0.17.0
conflicts with file from package mysql-3.23.52-3
        ...
        file /usr/shar/man/man1/ ... from install of ... conflicts with
file from package mysql-3.23...
        ..."
        and the conflict list goes on.
         
        The installation manual does not seem to discuss about such
issues.  Do I need to remove my 3.23 before I run the installation? --
but that's not what the manual says, though.  The first warning msg, is
that a problem, too?
         
        Thanks.

Reply via email to