[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mysqld.sock missing



On Fri, 12 Aug 2005 15:06:44 +0200
Daniel Leidert <daniel.leidert.spam@gmx.net> wrote:

Thanks for the reply.

> > Last night I believe I upgraded mysql. Now whenever I try and use mysql, I
> > get this error:
> > 
> > > ~$ mysql
> > > ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> > > '/var/run/mysqld/mysqld.sock' (2) 
> 
> I had a similar problem. What does '/etc/init.d/mysql start' say? If it
> does not start, then open your /etc/mysql/my.cnf and comment out
> 'old_passwords' (mysql now fails with this option).

Here is what '/etc/init.d/mysql start' says:

> /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!

I've posted what syslog says at the bottom of this email.
 
> > I've tried reinstalling mysql-server-4.1, mysql-client-4.1, and
> > libmysqlclient14, but nothing seems to work. I've looked through
> > documentation, with nothing being said about a missing 'mysqld.sock' file.
> 
> This normally means, that your mysql-server is not running.

Which you are correct. It isn't running. :(

> > My system is a PB G3 Firewire (Pismo) running Debian/Etch. Any help would be
> > appreciated.
> 
> If mysqld does not start, you should have a look at the syslog.

I have now looked at the syslog. It's looking like /var/lib/mysql/mysql/user.frm
is corrupt in some way. Again, I'm at a loss as to how to approach this problem.
If someone could shed a little light on this for me, I'd really appreciate it...
I've seen a few cases on Google where they said to run
mysql_fix_privelege_tables, but I can't even get mysqld running, so everything
I've tried results in the original error I posted...

************* 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 *************

-M.



Reply to: