LinHES Forums • View topic - Can't start backend-SQL problems

Board index KnoppMyth General

All times are UTC - 6 hours

Can't start backend-SQL problems

Page 2 of 2

[ 25 posts ]

Go to page Previous 1, 2

Print view

Previous topic Next topic

Author

Message

shplad

Post subject:

Posted: Wed May 31, 2006 9:37 pm

Joined: Sun Nov 14, 2004 10:04 am

Posts: 263

Location: Toronto, Canada

dmcman:

I tried the myisamchk command, and I even tried it with the -c switch. Either way,
it didn't seem to give me any results-it just spit out all the command parameters. I think....
I'm not sure. Documentation for myisamchk suggests you need to run it from the same
directory as the database, but I don't know in what directory the database is.

Output I did get (other than all the switches) was:

Code:

Variables (--variable-name=value)
and boolean options {FALSE|TRUE}  Value (after reading options)
--------------------------------- -----------------------------
character-sets-dir                (No default value)
data-file-length                  0
keys-used                         18446744073709551615
set-auto-increment                0
set-character-set                 (No default value)
sort-records                      0
tmpdir                            (No default value)
key_buffer_size                   520192
myisam_block_size                 1024
read_buffer_size                  262136
write_buffer_size                 262136
sort_buffer_size                  2097144
sort_key_blocks                   16
decode_bits                       9
ft_min_word_len                   4
ft_max_word_len                   254
ft_max_word_len_for_sort          20
ft_stopword_file                  (No default value)

Thanks again.

Shplad

dmcman73 wrote:

Try running this command as root:

#myisamchk

This command will check the mysql tables for any errors and it requires that mysql to not be running. Usually you would run the command with:

#myisamchk <tablename>

to specify each table individually, running it without specifying a table will force it to check every single one in your database so it may take some time.

If your database comes back clean then the only other thing I can think of is that you may have a corruption in your mysql install such as a config file.

Without actually being ont he box to check everything it is pretty difficult to trouble shot any further.

What do your logs say? They are located in /var/log/mysql.

_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick

Last edited by shplad on Wed May 31, 2006 9:47 pm, edited 1 time in total.

Top

tjc

Post subject:

Posted: Wed May 31, 2006 9:40 pm

Joined: Thu Mar 25, 2004 11:00 am

Posts: 9551

Location: Arlington, MA

Are you in the right directory? See Cecil's instructions on DB repair here (if you haven't already): http://mysettopbox.tv/phpBB2/viewtopic.php?t=1043

Top

dmcman73

Post subject:

Posted: Wed May 31, 2006 9:45 pm

Joined: Sun Mar 21, 2004 10:01 am

Posts: 77

tjc beat me to it.

Let me know how you make out with the DB check.

Top

shplad

Post subject:

Posted: Thu Jun 01, 2006 8:48 am

Joined: Sun Nov 14, 2004 10:04 am

Posts: 263

Location: Toronto, Canada

Okay, done. Can't see any of the warnings listed in Cesman's post. Am I missing anything?

Code:

- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2

---------

Checking MyISAM file: recordingprofiles.MYI
Data records:      29   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links

---------

Checking MyISAM file: recordmatch.MYI
Data records:       0   Deleted blocks:      19
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1

---------

Checking MyISAM file: recordoverride.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check record links

---------

Checking MyISAM file: schemalock.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference

---------

Checking MyISAM file: settings.MYI
Data records:     424   Deleted blocks:       3
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links

---------

Checking MyISAM file: smartplaylist.MYI
Data records:       8   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check data record references index: 3
- check record links

---------

Checking MyISAM file: smartplaylistcategory.MYI
Data records:       3   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check record links

---------

Checking MyISAM file: smartplaylistitem.MYI
Data records:       8   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check record links

---------

Checking MyISAM file: snessettings.MYI
Data records:       1   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check record links

---------

Checking MyISAM file: videobookmarks.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links

---------

Checking MyISAM file: videocategory.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links

---------

Checking MyISAM file: videocountry.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links

---------

Checking MyISAM file: videogenre.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links

---------

Checking MyISAM file: videometadata.MYI
Data records:      15   Deleted blocks:       3
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check data record references index: 3
- check data record references index: 4
- check record links

---------

Checking MyISAM file: videometadatacountry.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference

---------

Checking MyISAM file: videometadatagenre.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference

---------

Checking MyISAM file: videosource.MYI
Data records:       1   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check record links

---------

Checking MyISAM file: videotypes.MYI
Data records:       7   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links

---------

Checking MyISAM file: websites.MYI
Data records:       0   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links

---------

Checking MyISAM file: xvmc_buffer_settings.MYI
Data records:       2   Deleted blocks:       0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links
root@box:/var/lib/mysql/mythconverg#

Shplad

tjc wrote:

Are you in the right directory? See Cecil's instructions on DB repair here (if you haven't already): http://mysettopbox.tv/phpBB2/viewtopic.php?t=1043

Top

dmcman73

Post subject:

Posted: Thu Jun 01, 2006 2:58 pm

Joined: Sun Mar 21, 2004 10:01 am

Posts: 77

Well from the looks of the output, your DB is clean.

Ideally Mysql, on a local system, will connect to itself using the sock file that it is complaining it can not find. This sock file is created by mysqld when it starts. I had an issue on a past box where I installed linux OS, named the host name something like mythbox and upon boot up mysql refused to start spitting out the sock file error. I changed the host name back to localhost and all was well.

From the Mysql site: "A Unix socket file is used if you don't specify a hostname or if you specify the special hostname localhost"

My guess here is that the Mysql install was setup with the skip-networking variable turned on or you have some other network issue that is not allowing your mysql connection through TCP/IP.

If this your issue? I don't know but it dosn't hurt to try it.

Change your host name to localhost and see if that helps. I see that your host name is "box".

See here on changing host names: http://www.geocities.com/rlcomp_1999/hostname.html
and also commands to verify that your host name has changed.

Top

shplad

Post subject:

Posted: Fri Jun 02, 2006 6:57 pm

Joined: Sun Nov 14, 2004 10:04 am

Posts: 263

Location: Toronto, Canada

dmcman:

Thanks once more. I'm guessing that's not the problem, as "box" was the default name given
in the KnoppMyth install-I didn't change it. I suppose it might have become corrupted.
I'll check for that. Networking appears to be working okay. I can SSH into
the box. I can transfer viles via Samba. I can access the Mythweb. Assuming that's not it, though,
do you have any other suggestions? I'd really hate to have to reinstall from scratch-
it's a real b*tch for Linux newbies like me, and this was already at least my 6th install.

Shplad

dmcman73 wrote:

Top

shplad

Post subject: permissions?

Posted: Sun Jun 04, 2006 12:59 pm

Joined: Sun Nov 14, 2004 10:04 am

Posts: 263

Location: Toronto, Canada

Just to rule out permissions problems, It would be greatly appreciated if someone could
please print out the perms for:

/var
/var/run/
var/run/mysql

Thanks in advance.

shplad

Top

avocade

Post subject:

Posted: Tue Jul 18, 2006 3:03 am

Joined: Sat Jun 18, 2005 7:47 am

Posts: 73

Location: Sweden

Shplad, did you have any luck resolving the issue? I'm having the _exact_ same errors as you have, with mysqld not starting, instead spitting out this error "ERROR 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)".

Going crazy here, since _everything else_ works fine on the box. I can't even do an auto-upgrade since you need to do "mythbackup" first, which of course doesn't work properly if you can't do a mysqldump on the database.......

Top

avocade

Post subject:

Posted: Tue Jul 18, 2006 3:24 am

Joined: Sat Jun 18, 2005 7:47 am

Posts: 73

Location: Sweden

Solved!?

-----------

found this info on the mysql site:

Using /usr/sbin/mysqld --verbose allowed me to see that there was an unrecognized variable 'old_passwords=1', which I later found out was being set by Debian in /etc/mysql/my.cnf for some backward compatibility with *Debian* software. Removing this entry from the configuration file was all that was needed to get my server working again. This bug has been addressed by the Debian package maintainers: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321578

----------------

then I tried changing that and starting mysqld again, which gave me this in syslog:

"/usr/sbin/mysqld: unknown variable 'expire-logs-days=20'"

so I changed that too with "nano /etc/mysql/my.cnf"

changed old_passwords=1
to
#old_passwords=1

changed expire-logs-days=20
to
#expire-logs-days=20

and lo and behold, when trying /etc/init.d/mysql start it now starts!! must have made an involuntary upgrade (with apt-get perhaps?) of the mysql my.conf file!

now I've made a backup, let's restart and see if everything is back to normal.

Top

shplad

Post subject:

Posted: Fri Jul 21, 2006 2:08 pm

Joined: Sun Nov 14, 2004 10:04 am

Posts: 263

Location: Toronto, Canada

Avocade/all:

Thanks for your input. I I find playing with mysql totally intimidating.
So I ended up just installing R5C7 from scratch.

However, for those who are inclined to to try to fix
MySQL (or should I say TheirSQL? :-)

) these pages over at the University of Washington's website looked very helpful.
http://www.washington.edu/computing/web/publishing/mysql.html

Shplad

avocade wrote:

Top

Page 2 of 2

[ 25 posts ]

Go to page Previous 1, 2

Board index KnoppMyth General

All times are UTC - 6 hours

Who is online

Users browsing this forum: No registered users and 22 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum