DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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?
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)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.