This is what perror says about error 134 Error code 134: Unknown error 134 134 = Record was already deleted (or record file crashed)
Hpe that makes any sense to you. Best regards Nils Valentin Tokyo/Japan 2003年 6月 26日 木曜日 09:04、Ian Collins さんは書きました: > My MySQL database just stopped. I had 47 users running on it who just > stopped being able to access the database. > The .err file in the MySQL data directory has, > > Version: '4.0.11-gamma-standard-log' socket: '/tmp/mysql.sock' port: 3306 > 030611 10:45:45 mysql_ha_read: Got error 124 when reading table > 030616 11:21:37 mysql_ha_read: Got error 134 when reading table > 030616 12:13:15 mysql_ha_read: Got error 134 when reading table > Warning: thr_alarm queue is full > Warning: thr_alarm queue is full > > The last line repeats about 500 times. > To get my users up and running, I restarted mysql. > > What is the alarm queue. The documentation says it creates a queue for > alarms, but little else. What was the alarm queue full of? and how do I > stop it? > > -- > > Many Regards, > Ian Collins > System Manager > KIWIPLAN NZ Ltd. > ================ > > There are always alternatives. > -- Spock, "The Galileo Seven", stardate 2822.3 -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
