#1030 - Got error 127 from storage engine

[chris_sharman]

issue tracker just died on me.
phpmyadmin reports the error below on the issue table.
Think it's a mysql problem.
Anyone confirm ? Know cause / fix ?

Thanks,
Chris

SQL-query: Documentation

SELECT *
FROM `issues`
LIMIT 0 , 30

MySQL said: Documentation
#1030 - Got error 127 from storage engine

[issinoho]

Possible database corruption, have you tried repairing the table,

REPAIR TABLE <table-name>

Ref, http://www.databasejournal.com/features ... _3300511_2

[Ton van der Zwet]

Possible database corruption, have you tried repairing the table,

REPAIR TABLE <table-name>

Ref, http://www.databasejournal.com/features ... _3300511_2

OK, I guess the table will be corrupt and will get corrupted every time a certain sequence of instructions is executed. With an old version of MySQL and VMS, PHP etc. I managed to corrupt the database 'reliable' within a minute . After a discussion with JFP, the work-around was simple and is now the default setting: Use innodb tables instead of MyISAM tables.

You can check the db engine used for a table with this command:

Code: Select all

mysql> show table status like 'my_table';

Except for the own MySQL tables you can use the innodb tables almost everywhere.

In the manual you'll find the commands to change the db-engine for tables.

We backed up and reloaded our databases after we recreated the tables in innodb format.

Allthough this works for PHPBB (we run a phpbb for almost two years now!), the problem with MyISAM tables isn't solved yet.

Ton van der Zwet, member of the openoffice on OpenVMS porting team

http://www.oooovms.dyndns.org/ (Web site porting effort)
http://www.4ovms.dyndns.org/phpbb/ (supporting phpbb site)

[Marty]

Does the MyISAM engine still have corruption problems? It looks like Joomla is set up to use MyISAM, and I've been having problems with table data disappearing.

[Ton van der Zwet]

Does the MyISAM engine still have corruption problems? It looks like Joomla is set up to use MyISAM, and I've been having problems with table data disappearing.

I didn't check it recently.

I try to spend as much time as possible on the fieldtest of OpenVMS and GNV.
I was wondering, do you mean with data disappearing that the table is not corrupt?
My symptoms were real table corruptions...
On the other hand, almost every software component has been updated since then.
Maybe a total new best practices, or better yet, optimize the default settings for "all" tooling so that it will behave better running on the latest OpenVMS versions available for us hobbyists.

[Marty]

MySQL 4.1.4, VMS 7.3-2 and Joomla users keep disappearing. Since I'm the only one using this on my test machine, it says to me that something is wrong with MySQL.

Code: Select all

mysql> use joomla;
Database changed
mysql> select username,password,gid from jos_users;

ERROR 1030 (HY000): Got error 127 from storage engine
mysql> repair table jos_users;
+------------------+--------+----------+------------------------------------+
| Table            | Op     | Msg_type | Msg_text                           |
+------------------+--------+----------+------------------------------------+
| joomla.jos_users | repair | warning  | Number of rows changed from 1 to 0 |
| joomla.jos_users | repair | status   | OK                                 |
+------------------+--------+----------+------------------------------------+
2 rows in set (0.40 sec)

mysql> select username,password,gid from jos_users;
Empty set (0.07 sec)

Where'd admin go?

[Ton van der Zwet]

Marty,

did you follow the recommendations from the OpenVMS porter? I modified the startup file to make the default database engine for tables innodb. I haven't had an error since (with phpbb).
Can you look at the engine used for joomla table?

A friend did a joomla installation and according to him he didn't have make many modifications to get it going. Unfortunally he is having a holiday, so I can't ask him for the details.

[Marty]

I'd be interested in seeing how your friend got this to work. By default Joomla uses MyISAM which may be why it keeps crapping out. Did your friend do any changes to the install, or did he change the db engine for it?

Curious,
Marty