Possible 'user.frm' corruption...
Posted by: mannslists
Date: August 18, 2005 11:28AM

Hi all,

I posted about this in the 'Newbie' forum, but thought this might be a better place to post about this...

I'm using MySQL 4.1 on a Debian/Etch/PPC machine. Something odd happened one night, and I was told to drop by here from the guys at the Debian/PPC mailing list...

The first thing I noticed was that when I tried to use MySQL, it would always give me this error:

> ~$ mysql
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2)

I then reinstalled all of the Debian packages related to MySQL, but I was still stranded with the same error messages. When I posted what I had done on the Debian mailing list, they asked me what errors I had recieved when I did a '/etc/init.d/mysql start', and also what my '/var/log/syslog/' said on the matter:

This is what '/etc/init.d/mysql start' noted:

> /var/lib/mysql/mysql# /etc/init.d/mysql start
> Starting MySQL database server: mysqld...failed.
> Please take a look at the syslog.
> /usr/bin/mysqladmin: connect to server at 'localhost' failed
> error: 'Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the
> socket: '/var/run/mysqld/mysqld.sock' exists!

And here is what '/var/log/syslog' said:

************* PASTED *************
Aug 12 15:39:43 cora mysqld_safe[6844]: started
Aug 12 15:39:44 cora mysqld[6847]: 050812 15:39:44 InnoDB: Database was not
shut down normally!
Aug 12 15:39:44 cora mysqld[6847]: InnoDB: Starting crash recovery.
Aug 12 15:39:44 cora mysqld[6847]: InnoDB: Reading tablespace information from
the .ibd files...
Aug 12 15:39:44 cora mysqld[6847]: InnoDB: Restoring possible half-written data
pages from the doublewrite
Aug 12 15:39:44 cora mysqld[6847]: InnoDB: buffer...
Aug 12 15:39:44 cora mysqld[6847]: 050812 15:39:44 InnoDB: Starting log scan
based on checkpoint at
Aug 12 15:39:44 cora mysqld[6847]: InnoDB: log sequence number 0 44158.
Aug 12 15:39:44 cora mysqld[6847]: InnoDB: Doing recovery: scanned up to log
sequence number 0 44204
Aug 12 15:39:44 cora mysqld[6847]: InnoDB: Last MySQL binlog file position 0 79,
file name /var/log/mysql/mysql-bin.000233
Aug 12 15:39:44 cora mysqld[6847]: 050812 15:39:44 InnoDB: Flushing modified
pages from the buffer pool...
Aug 12 15:39:44 cora mysqld[6847]: 050812 15:39:44 InnoDB: Started; log sequence
number 0 44204
Aug 12 15:39:44 cora mysqld[6847]: 050812 15:39:44 [ERROR] /usr/sbin/mysqld:
Incorrect information in file: './mysql/user.frm'
Aug 12 15:39:44 cora mysqld[6847]: 050812 15:39:44 [ERROR] Fatal error: Can't
open privilege tables: Incorrect information in file: './mysql/user.frm'
Aug 12 15:39:44 cora mysqld_safe[6858]: ended
Aug 12 15:39:50 cora /etc/init.d/mysql[6925]: 0 processes alive and
'/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Aug 12 15:39:50 cora /etc/init.d/mysql[6925]: ^G/usr/bin/mysqladmin: connect to
server at 'localhost' failed
Aug 12 15:39:50 cora /etc/init.d/mysql[6925]: error: 'Can't connect to local
MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Aug 12 15:39:50 cora /etc/init.d/mysql[6925]: Check that mysqld is running and
that the socket: '/var/run/mysqld/mysqld.sock' exists!
Aug 12 15:39:50 cora /etc/init.d/mysql[6925]:
************* END PASTE *************

When the mailing list guys saw what was going on, they basically agreed with me that '/var/lib/mysql/mysql/user.frm' was somehow corrupted and that I talk to you guys. Because I cannot even get mysqld running, I have no way to fix (as far as I'm aware) this problem. If there's any light that you guys can shed on this, I'd really appreciate it!

Thanks!
-M.

Options: ReplyQuote


Subject
Written By
Posted
Possible 'user.frm' corruption...
August 18, 2005 11:28AM
September 23, 2005 07:02PM
October 05, 2005 05:31AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.