Thanks for the reply Gerald.
I took your advise and tried myisamchk with the following results:
[EMAIL PROTECTED] mysql]# myisamchk -r user.*
myisamchk: error: 'user.frm' doesn't have a correct index definition. You
need to recreate it before you can do a repair
---------
myisamchk: error: 'user.MYD' doesn't have a correct index definition. You
need to recreate it before you can do a repair
---------
- recovering (with sort) MyISAM-table 'user.MYI'
Data records: 6
- Fixing index 1
Being relatively new to mysql, I am just getting my actual
databases/tables set up so wiping out the entire mysql database and starting
over is an option. Any thoughts on where I go from here??
I tried the -o option same results. Here are the results from myisamchk -r
for the entire mysql directory. The results don't make sense to me. How
could everything need to be rebuilt??
[EMAIL PROTECTED] mysql]# myisamchk -r *.*
myisamchk: error: 'columns_priv.frm' doesn't have a correct index
definition. You need to recreate it before you can do a repair
---------
myisamchk: error: -1 when opening MyISAM-table 'columns_priv.MYD'
---------
- recovering (with keycache) MyISAM-table 'columns_priv.MYI'
Data records: 0
---------
myisamchk: error: 'db.frm' doesn't have a correct index definition. You need
to recreate it before you can do a repair
---------
myisamchk: error: 'db.MYD' doesn't have a correct index definition. You need
to recreate it before you can do a repair
---------
- recovering (with sort) MyISAM-table 'db.MYI'
Data records: 3
- Fixing index 1
- Fixing index 2
---------
myisamchk: error: 'func.frm' doesn't have a correct index definition. You
need to recreate it before you can do a repair
---------
myisamchk: error: -1 when opening MyISAM-table 'func.MYD'
---------
- recovering (with keycache) MyISAM-table 'func.MYI'
Data records: 0
---------
myisamchk: error: 'host.frm' doesn't have a correct index definition. You
need to recreate it before you can do a repair
---------
myisamchk: error: -1 when opening MyISAM-table 'host.MYD'
---------
- recovering (with keycache) MyISAM-table 'host.MYI'
Data records: 0
---------
myisamchk: error: 'tables_priv.frm' doesn't have a correct index definition.
You need to recreate it before you can do a repair
---------
myisamchk: error: -1 when opening MyISAM-table 'tables_priv.MYD'
---------
- recovering (with keycache) MyISAM-table 'tables_priv.MYI'
Data records: 0
---------
myisamchk: error: 'user.frm' doesn't have a correct index definition. You
need to recreate it before you can do a repair
---------
myisamchk: error: 'user.MYD' doesn't have a correct index definition. You
need to recreate it before you can do a repair
---------
- recovering (with sort) MyISAM-table 'user.MYI'
Data records: 6
- Fixing index 1
[EMAIL PROTECTED] mysql]#
Any help would be appreciated!!
--
David C. Rankin, J.D., P.E.
RANKIN * BERTIN, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
--
----- Original Message -----
From: "gerald_clark" <[EMAIL PROTECTED]>
To: "David Rankin" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, December 12, 2003 8:37 AM
Subject: Re: MySql died a hard death after using grant and won't restart
> perror 145
> 145 = Table was marked as crashed and should be repaired.
>
> Run myisamchk on it.
>
> David Rankin wrote:
>
> >I can't figure this out. I'm setting privileges for access on a local net
to
> >a user [EMAIL PROTECTED] using grant and all of a sudden mysql is dead. I'm
> >running 3.23.31 on Mandrake 7.2. I haven't had any problems in years.
> >Anybody got any thoughts on this? Please reply to
[EMAIL PROTECTED]
> >What in the heck could cause a "Bogus stack limit or frame pointer,
aborting
> >backtrace" ??
> >
> >The applicable part of the .err log is:
> >
> >mysqld got signal 11;
> >The manual section 'Debugging a MySQL server' tells you how to use a
> >stack trace and/or the core file to produce a readable backtrace that may
> >help in finding out why mysqld died
> >Attemping backtrace. You can use the following information to find out
> >where mysqld died. If you see no messages after this, something went
> >terribly wrong
> >Bogus stack limit or frame pointer, aborting backtrace
> >
> >Number of processes running now: 0
> >031211 20:38:21 mysqld restarted
> >031211 20:38:21 Found invalid password for user: '[EMAIL PROTECTED]';
> >Ignoring user
> >/usr/sbin/mysqld: ready for connections
> >031211 21:40:40 /usr/sbin/mysqld: Normal shutdown
> >
> >031211 21:40:40 /usr/sbin/mysqld: Shutdown Complete
> >
> >031211 21:40:40 mysqld ended
> >
> >031211 21:40:47 mysqld started
> >031211 21:40:47 /usr/sbin/mysqld: Can't open file: 'user.MYD'. (errno:
145)
> >031211 21:40:47 mysqld ended
> >
> >**** next ****
> >
> >I mv /datadir/mysql /datadir/mysql-old
> >
> >then do a mysql_install_db and try again. Same error results
> >
> >mysqld got signal 11;
> >The manual section 'Debugging a MySQL server' tells you how to use a
> >stack trace and/or the core file to produce a readable backtrace that may
> >help in finding out why mysqld died
> >Attemping backtrace. You can use the following information to find out
> >where mysqld died. If you see no messages after this, something went
> >terribly wrong
> >Cannot determine thread, ebp=0xb, backtrace may not be correct
> >Bogus stack limit or frame pointer, aborting backtrace
> >
> >
> >
> >--
> >David C. Rankin, J.D., P.E.
> >Rankin * Bertin, PLLC
> >510 Ochiltree Street
> >Nacogdoches, Texas 75961
> >(936) 715-9333
> >(936) 715-9339 fax
> >--
> >
> >
> >
> >
>
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
