| Bug #22392 | Internal program error (failed ndbrequire) | ||
|---|---|---|---|
| Submitted: | 15 Sep 2006 13:56 | Modified: | 15 Sep 2006 14:08 |
| Reporter: | Jeffrey Tagen | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | Max-5.0.24 | OS: | Linux (RHEL4) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[15 Sep 2006 14:08]
Jonas Oreland
Hi This is a duplicate of http://bugs.mysql.com/bug.php?id=20892 Which has been fixed in 5.0.25 The problem is related to out of datamemory... So increasing datamemory will maybe fix your problem Very sorry... /Jonas
Description: Running small cluster (2 servers running both mysqld and ndbd and a separate ndb_mgm controller), system shut down while under almost no load. Received the following error from web app when connecting via PHP "Got temporary error 4031 'Node failure caused abort of transaction' from ndbcluster] in EXECUTE("insert into ........" Both servers had identical errors in ndb_error_log file: Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug) Error: 2341 Error data: DbtupPagMan.cpp Error object: DBTUP (Line: 331) 0x0000000a Program: ndbd Pid: 4244 Trace: /var/lib/mysql-cluster/ndb_3_trace.log.2 Version: Version 5.0.24 Restarted ndbd and cycled mysqld, everything seems to be working properly. This is running RHEL4: Linux db2 2.6.9-34.0.1.ELsmp #1 SMP Wed May 17 17:05:24 EDT 2006 i686 i686 i386 GNU/Linux using the MySQL packaged 5.2.24-0.rhel4 RPMS Trace log is too big to attach (~1MB), available at http://sdkck.com/ndb_3_trace.log.2 How to repeat: Unknown Suggested fix: Unknown