My log filled up with errors so I had to run that script to clear. I then ran the database fix commands.

Now I get this error
Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)


I think it is because I have my mysql.cnf file pointing to the wrong place but I am not sure. I can no longer start mysql.

Below is my "my.cnf"

root@alexvdmythtv:/etc/mysql# cat /etc/mysql/my.cnf
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "/var/lib/mysql/my.cnf" to set server-specific options or
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
[client]
#password = my_password
port = 3306
socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = -5

[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
# Both location gets rotated by the cronjob.
#log = /var/log/mysql.log
log = /var/log/mysql/mysql.log
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-external-locking
#
# The skip-networking option will no longer be set via debconf menu.
# You have to manually change it if you want networking i.e. the server
# listening on port 3306. The default is "disable" - for security reasons.
#skip-networking
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 128K
#
# Query Cache Configuration
#
query_cache_limit = 1048576
query_cache_size = 26214400
query_cache_type = 1
#
# Here you can see queries with especially long duration
#log-slow-queries = /var/log/mysql/mysql-slow.log
#
# The following can be used as easy to replay backup logs or for replication
#server-id = 1
#log-bin = /var/log/mysql/mysql-bin.log
#binlog-do-db = include_database_name
#binlog-ignore-db = include_database_name
#
# Read the manual if you want to enable InnoDB!
skip-innodb
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# If you want to enable SSL support (recommended) read the manual or my
# HOWTO in /usr/share/doc/mysql-server/SSL-MINI-HOWTO.txt
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer = 16M

So I know that Cesman, xsecrets and others have helped with this issue before.

I really dont want to reinstall or I guess I could try and upgrade.

Please help.

Ok, if you know we've helped with this issue before, have you searched the forum? What did we recommened before? Did have we recommened not work? What else have you tried?

_________________
cesman

When the source is open, the possibilities are endless!

Ok after more searching it appears that it is not necessarily what you have fixed before.

My syslog is reporting error 144 which means that the table has been damaged and wasnt able to repaired.

I got that error after I tried to run a repair on user.MYI

It is also saying that it cant open privelaged tables which I think is a permissions problem.

Is this correct. Not sure what to do if I running the repair command is not working.

root@alexvdmythtv:/var/log# cat syslog
Sep 27 06:25:22 alexvdmythtv syslogd 1.4.1#16: restart.
Sep 27 06:37:40 alexvdmythtv -- MARK --
Sep 27 06:57:40 alexvdmythtv -- MARK --
Sep 27 07:17:01 alexvdmythtv /USR/SBIN/CRON[4211]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 07:37:41 alexvdmythtv -- MARK --
Sep 27 07:57:41 alexvdmythtv -- MARK --
Sep 27 08:17:01 alexvdmythtv /USR/SBIN/CRON[4225]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 08:37:41 alexvdmythtv -- MARK --
Sep 27 08:57:42 alexvdmythtv -- MARK --
Sep 27 09:17:01 alexvdmythtv /USR/SBIN/CRON[4239]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 09:37:42 alexvdmythtv -- MARK --
Sep 27 09:57:42 alexvdmythtv -- MARK --
Sep 27 10:17:01 alexvdmythtv /USR/SBIN/CRON[4253]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 10:37:43 alexvdmythtv -- MARK --
Sep 27 10:57:43 alexvdmythtv -- MARK --
Sep 27 11:17:01 alexvdmythtv /USR/SBIN/CRON[4267]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 11:37:44 alexvdmythtv -- MARK --
Sep 27 11:57:44 alexvdmythtv -- MARK --
Sep 27 12:17:01 alexvdmythtv /USR/SBIN/CRON[4281]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 12:37:45 alexvdmythtv -- MARK --
Sep 27 12:42:55 alexvdmythtv ntpd[2525]: time reset -0.155492 s
Sep 27 12:47:12 alexvdmythtv ntpd[2525]: synchronized to LOCAL(0), stra tum 13
Sep 27 12:48:16 alexvdmythtv ntpd[2525]: synchronized to 65.119.47.241, stratum 2
Sep 27 13:02:22 alexvdmythtv ntpd[2525]: time reset +0.357321 s
Sep 27 13:06:39 alexvdmythtv ntpd[2525]: synchronized to LOCAL(0), stra tum 13
Sep 27 13:07:45 alexvdmythtv ntpd[2525]: synchronized to 65.119.47.241, stratum 2
Sep 27 13:17:01 alexvdmythtv /USR/SBIN/CRON[4295]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 13:24:01 alexvdmythtv ntpd[2525]: time reset -0.308159 s
Sep 27 13:28:18 alexvdmythtv ntpd[2525]: synchronized to LOCAL(0), stra tum 13
Sep 27 13:29:24 alexvdmythtv ntpd[2525]: synchronized to 65.119.47.241, stratum 2
Sep 27 13:57:46 alexvdmythtv -- MARK --
Sep 27 14:17:01 alexvdmythtv /USR/SBIN/CRON[4309]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 14:37:46 alexvdmythtv -- MARK --
Sep 27 14:57:46 alexvdmythtv -- MARK --
Sep 27 15:17:01 alexvdmythtv /USR/SBIN/CRON[4323]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 15:37:47 alexvdmythtv -- MARK --
Sep 27 15:57:47 alexvdmythtv -- MARK --
Sep 27 16:17:01 alexvdmythtv /USR/SBIN/CRON[4337]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 16:37:48 alexvdmythtv -- MARK --
Sep 27 16:57:48 alexvdmythtv -- MARK --
Sep 27 17:17:01 alexvdmythtv /USR/SBIN/CRON[4351]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 17:37:48 alexvdmythtv -- MARK --
Sep 27 17:57:49 alexvdmythtv -- MARK --
Sep 27 18:17:01 alexvdmythtv /USR/SBIN/CRON[4365]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 18:37:49 alexvdmythtv -- MARK --
Sep 27 18:57:49 alexvdmythtv -- MARK --
Sep 27 19:17:02 alexvdmythtv /USR/SBIN/CRON[4379]: (root) CMD ( run-p arts --report /etc/cron.hourly)
Sep 27 19:37:50 alexvdmythtv -- MARK --
Sep 27 19:52:07 alexvdmythtv mysqld_safe[4469]: started
Sep 27 19:52:08 alexvdmythtv mysqld[4472]: 050927 19:52:08 /usr/sbin/my sqld: Can't open file: 'user.MYI'. (errno: 144)
Sep 27 19:52:08 alexvdmythtv mysqld[4472]: 050927 19:52:08 Fatal error: Can't open privilege tables: Can't open file: 'user.MYI'. (errno: 144)
Sep 27 19:52:08 alexvdmythtv mysqld[4472]: 050927 19:52:08 Aborting
Sep 27 19:52:08 alexvdmythtv mysqld[4472]:
Sep 27 19:52:08 alexvdmythtv mysqld[4472]: 050927 19:52:08 /usr/sbin/my sqld: Shutdown Complete
Sep 27 19:52:08 alexvdmythtv mysqld[4472]:
Sep 27 19:52:08 alexvdmythtv mysqld_safe[4475]: ended
Sep 27 19:52:14 alexvdmythtv /etc/init.d/mysql[4517]: 0 processes alive and '/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf p ing' resulted in
Sep 27 19:52:14 alexvdmythtv /etc/init.d/mysql[4517]: ^G/usr/bin/mysqla dmin: connect to server at 'localhost' failed
Sep 27 19:52:14 alexvdmythtv /etc/init.d/mysql[4517]: error: 'Can't con nect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Sep 27 19:52:14 alexvdmythtv /etc/init.d/mysql[4517]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Sep 27 19:52:14 alexvdmythtv /etc/init.d/mysql[4517]:
Sep 27 20:17:01 alexvdmythtv /USR/SBIN/CRON[4525]: (root) CMD ( run-p arts --report /etc/cron.hourly)

I guess I will have to do a reinstall clean.

Is it possible that I could use mythrestore, or how about auto upgrade. Would those fix the mysql database?

When mythbackup runs, it attempts to check and fix db before backing it up. If you db is truly jacked, best to just start all over. But that is your call.

_________________
cesman

When the source is open, the possibilities are endless!

Thanks is it possible to run from x term. If so is the command mythrestore or myth-restore?

I cannot get into the frontend. It goes through the initial setup screens and then dumps back to knoppmyth screen.

You can run anything from an xterm. Who said anything about mythrestore?

_________________
cesman

When the source is open, the possibilities are endless!

so the answer is start over.

No, that is up to you to decide. Have you even taken a look at the MySQL logs? If you cannot repair the db, then that gives you little choice but to start over. If for whatever reason you /etc/init.d/mysql got jacked, you can copy the one off the CD.

_________________
cesman

When the source is open, the possibilities are endless!