219935 - Getting--- ERROR 1030: Got error 134 from table handler

Status: RESOLVED INVALID

(Bugzilla :: Bugzilla-General, defect)

Description

[UmarKathap]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; Installed by Symantec Package)
Build Identifier: 

The System Bugzila was working fine. Suddenly it's giving error as following:

Posting Bug  
   One moment please...  
Content-type: text/html 
Software error:
INSERT INTO bugs ( product, version, rep_platform, bug_severity, priority, 
op_sys, assigned_to, bug_status, bug_file_loc, short_desc, component, 
target_milestone, everconfirmed, reporter, creation_ts, groupset) VALUES 
( 'Bugzilla', '1.0', 'PC', 'normal', 'P2', 'Windows 
2000', '3', 'NEW', '', 'test', 'Functionality', '---', '1', 3, now(), (0) & 
255) : Duplicate entry '1497' for key 1 at globals.pl line 224. 
For help, please send mail to the webmaster (ftpuser@chatsvr), giving this 
error message and the time and date of the error. 


While I am trying to insert manually in mysql db i am getting

ERROR 1030: Got error 134 from table handler

The same error I am getting even in select or update for bug_id 1497.

select bug_id from bugs where bug_id > 1495; giving result as
1496
1497

but select bug_id,groupset from bugs where bug_id > 1495 giving the above 
mentioned error.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.




It's happened suddenly so I am unable to give steps for reproducing the same.
But You can guess and resolve the problem by the details given by me.
Thanks in Advance
Umar

Comment 1

[chaduv]

What version of bugzilla? Did you change any relevant software soon before it 
started erroring (perl, mysql, etc). Can you still reproduce the problem?

Comment 2

[Dave Miller [:justdave]]

perror (provided with MySQL) says:

dave@ibook [20:17 ~ 5] tcsh> perror 134
Error code 134:  Unknown error: 134
134 = Record was already deleted (or record file crashed)

Sounds like your database is corrupted.  Try "REPAIR TABLE bugs" from the mysql>
prompt.  This isn't a problem with Bugzilla, so resolving invalid.  Please
continue the discussion on [e-mail] if you still need help.
 Feel free to report back here whether or not REPAIR TABLE was successful though.