Bug #9389 | NDB start/stop failure (also causing subsequent test failures) | ||
---|---|---|---|
Submitted: | 24 Mar 2005 18:28 | Modified: | 13 Oct 2005 14:34 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 5.0.3 and up | OS: | Some Unix (shifting) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[24 Mar 2005 18:28]
Joerg Bruehe
[14 Jun 2005 15:30]
Martin Skold
This problem is not seen in last 5.0.7 build, should I close it?
[14 Jul 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[10 Aug 2005 12:40]
Joerg Bruehe
Sorry, got out of sight for some time. The problem still exists, but is shifting platforms: In 5.0.11, it occurs just on "cane" (FreeBSD), both with native and with Linuxthreads: ndb_autodiscover [ fail ] Errors are (from PATH/mysqltest-time) : waitNodeState(NOT_STARTED, -1) timeout after 121 attemps At line 489: command "$NDB_TOOLS_DIR/ndb_waiter --no-defaults --not-started > /dev/null" failed (the last lines may be the most important ones) Ending Tests Occurred: cane-5.0-cluster.log normal cane-linuxthreads-5.0-cluster.log normal cane-linuxthreads-5.0-cluster.log ps-protocol
[16 Aug 2005 9:59]
Tomas Ulin
Is this only on freebsd with linux threads, if so it is a know issue, see below http://bugs.mysql.com/bug.php?id=8369
[16 Aug 2005 11:21]
Tomas Ulin
problem limited to freeBSD and lacking support there, thus setting low prio
[18 Aug 2005 3:18]
Stewart Smith
I was talking with someone who is more familiar with FreeBSD and they were saying it's quite possibly a bug in the FreeBSD implementation of LinuxThreads. The developers of this library could be interested to work with us - although it's probably not a priority.
[13 Oct 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[14 Dec 2005 19:36]
Joerg Bruehe
Sorry, got out of sight a bit. The problem of NDB not starting was reported again in bug#15619, and was traced back to a too aggressive compiler optimization there. I will not yet close this, but hope I can do it after a successful build + test round.