LinuxQuestions.org - using backports seems to have broken MySQL

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - using backports seems to have broken MySQL (https://www.linuxquestions.org/questions/debian-26/using-backports-seems-to-have-broken-mysql-419770/)

using backports seems to have broken MySQL

I rebooted my computer the other day after having upgraded with the backports apt source and i noticed a fun little error as the boot information scrolled by:

Quote:

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!

Upon checking, the folder was there, but it was very blank. I tried to remove the program, remove the backports source, update, and then reinstall it, but no help.

How would I go about fixing this problem?

Post the log.

Code:

tail -n 20 /var/log/mysql

tail -n 20 /var/log/mysql.err

aopen25:/home/daniel# tail -n 20 /var/log/mysql
tail: error reading `/var/log/mysql': Is a directory
aopen25:/home/daniel# tail -n 20 /var/log/mysql.err
aopen25:/home/daniel#

This is bad I assume?

Sorry, the logfiles should be in the /var/log/mysql directory.

aopen25:/var/log/mysql# ls -la
total 748
drwxr-s--- 2 mysql adm 4096 2006-02-26 11:04 .
drwxr-xr-x 15 root root 4096 2006-02-26 11:13 ..
-rw-rw---- 1 mysql adm 6333 2006-02-26 10:56 mysql-bin.000035
-rw-rw---- 1 mysql adm 117 2006-02-26 10:56 mysql-bin.000036
-rw-rw---- 1 mysql adm 272 2006-02-26 10:56 mysql-bin.000037
-rw-rw---- 1 mysql adm 538 2006-02-26 10:56 mysql-bin.000038
-rw-rw---- 1 mysql adm 695 2006-02-26 10:56 mysql-bin.000039
-rw-rw---- 1 mysql adm 196 2006-02-26 10:56 mysql-bin.000040
-rw-rw---- 1 mysql adm 98 2006-02-26 10:56 mysql-bin.000041
-rw-rw---- 1 mysql adm 98 2006-02-26 11:04 mysql-bin.000042
-rw-rw---- 1 mysql adm 98 2006-02-26 11:04 mysql-bin.000043
-rw-rw---- 1 mysql adm 117 2006-02-26 11:09 mysql-bin.000044
-rw-rw---- 1 mysql adm 4 2006-02-20 06:26 mysql-bin.028
-rw-rw---- 1 mysql adm 12686 2006-02-21 06:26 mysql-bin.029
-rw-rw---- 1 mysql adm 21846 2006-02-22 06:26 mysql-bin.030
-rw-rw---- 1 mysql adm 390784 2006-02-23 06:26 mysql-bin.031
-rw-rw---- 1 mysql adm 214549 2006-02-24 06:26 mysql-bin.032
-rw-rw---- 1 mysql adm 40528 2006-02-25 06:26 mysql-bin.033
-rw-rw---- 1 mysql adm 4 2006-02-25 06:26 mysql-bin.034
-rw-rw---- 1 mysql adm 523 2006-02-26 11:04 mysql-bin.index

doesn't appear to have any log files.

If I were to remove the backports apt-source could I purge my package listings, redownload them all and then install the older verion of MySQL that I had before?

If so, how do i go about purgeing my apt package listing?

Just use something like:

Code:

apt-get remove --purge mysql-common ...

Then remove bakcports from your sources file and install the packages again.

ok, i did all that, i've got 4.1 back (the problem was that it somehow had converted me to sql4.0, might have been the "-f upgrade" i did...)

Aaaany ways, now my problem is:
aopen25:/home/daniel# mysqld
060227 16:23:54 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060227 16:23:54 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 4505122.
InnoDB: Doing recovery: scanned up to log sequence number 0 4505168
InnoDB: Last MySQL binlog file position 0 79, file name /var/log/mysql/mysql-bin.000054
060227 16:23:54 InnoDB: Flushing modified pages from the buffer pool...
060227 16:23:54 InnoDB: Started; log sequence number 0 4505168
060227 16:23:54 [ERROR] mysqld: Incorrect information in file: './mysql/user.frm'
060227 16:23:54 [ERROR] Fatal error: Can't open privilege tables: Incorrect information in file: './mysql/user.frm'
aopen25:/home/daniel# mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

How might this trouble be solved?