| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Ask Bjørn Hansen | Date: | August 11 2003 1:46pm |
| Subject: | Re: Corrupt index = mysqld freeze? | ||
| View as plain text | |||
On Thursday, Aug 7, 2003, at 13:41 America/Los_Angeles, Jennifer Goodie wrote: > I have a stand alone database server. It is a RAID5 running mySQL > 3.23.55 > on FreeBSD 4.1 In addition to Jeremy's suggestion of setting skip-name-resolve (and changing host names in the "mysql" database to IP addresses) you might want to consider upgrading FreeBSD to something more recent than 4.1 (unless that was a typo). 4.1 is over 3 years old. If skip-name-resolve doesn't help then it might be worthwhile to consider converting the tables to InnoDB to see if that changes anything. - ask -- http://www.askbjoernhansen.com/
| Thread | ||
|---|---|---|
| • Corrupt index = mysqld freeze? | Jennifer Goodie | 7 Aug |
| • Re: Corrupt index = mysqld freeze? | Jeremy Zawodny | 7 Aug |
| • RE: Corrupt index = mysqld freeze? | Jennifer Goodie | 8 Aug |
| • Re: Corrupt index = mysqld freeze? | Jeremy Zawodny | 8 Aug |
| • RE: Corrupt index = mysqld freeze? | Jennifer Goodie | 8 Aug |
| • Re: Corrupt index = mysqld freeze? | Dan Nelson | 8 Aug |
| • Re: Corrupt index = mysqld freeze? | Jeremy Zawodny | 9 Aug |
| • Re: Corrupt index = mysqld freeze? | Jeremy Zawodny | 9 Aug |
| • RE: Corrupt index = mysqld freeze? | Jennifer Goodie | 14 Aug |
| • Re: Corrupt index = mysqld freeze? | Jeremy Zawodny | 18 Aug |
| • Re: Corrupt index = mysqld freeze? | Daniel Kasak | 8 Aug |
| • Re: Corrupt index = mysqld freeze? | Ask Bjørn Hansen | 11 Aug |
