## WeBWorK Main Forum

### Statistics and Student Progress broken for one problem set

by Rob Owen -
Number of replies: 1
Sorry to intrude once again, but we're getting a very odd error here, though one of minor importance. For exactly one of our problem sets -- I think it might've been the first one created in this course, though I wasn't actually here for that -- both the statistics and student progress seem to be broken. It's the only problem set of the course which is afflicted by this error, which reads as follows:

### Warning messages

• DBD::mysql::st execute failed: Got error 127 from storage engine at /usr/local/webwork2/lib/WeBWorK/DB/Schema/SQL.pm line 276.

### Error messages

DBD::mysql::st execute failed: Got error 127 from storage engine at /usr/local/webwork2/lib/WeBWorK/DB/Schema/SQL.pm line 276.

### Call stack

The information below can help locate the source of the problem.

• in WeBWorK::DB::Schema::SQL::getAll called at line 1913 of /usr/local/webwork2/lib/WeBWorK/DB.pm
• in WeBWorK::DB::getAllUserProblems called at line 334 of /usr/local/webwork2/lib/WeBWorK/ContentGenerator/Instructor/Stats.pm
• in WeBWorK::ContentGenerator::Instructor::Stats::displaySets called at line 142 of /usr/local/webwork2/lib/WeBWorK/ContentGenerator/Instructor/Stats.pm
• in WeBWorK::ContentGenerator::Instructor::Stats::body called at line 152 of /usr/local/webwork2/lib/WeBWorK/Template.pm
• in WeBWorK::Template::template called at line 437 of /usr/local/webwork2/lib/WeBWorK/ContentGenerator.pm
• in WeBWorK::ContentGenerator::content called at line 174 of /usr/local/webwork2/lib/WeBWorK/ContentGenerator.pm
• in WeBWorK::ContentGenerator::go called at line 318 of /usr/local/webwork2/lib/WeBWorK.pm

As I mentioned, this isn't a terribly important error in the larger picture, but it's quite annoying as this is the background problem set we're using to ensure that the students have enough competency to get through the course. As always, any help would be greatly appreciated.

### Re: Statistics and Student Progress broken for one problem set

by Eddie Fuller -
Rob,

What version of mysql are you using? Error 127 usually means a record file is corrupted but can also mean table size problems. How big is your active webwork database?

You can try a few things but I would suggest first backing up webwork first, especially the database. mysqldump -u root -p webwork > webwork.sql if you haven't already.

It's probably worth doing '/etc/init.d/mysqld restart' and '/etc/init.d/httpd restart' to reload everything (or whatever your version of these would be) and see if that clears it up.

If not, you may need to repair a table. Probably <course>_set or <course>_set_user. This is fairly drastic and you may want to get some other opinions before going down this path. If you decide to, see

http://dev.mysql.com/doc/refman/5.0/en/repair.html

for more detail and tread softly :). You may lose data REPAIR'ing tables.

-Eddie