On Thu, 2006-03-09 at 14:01 +0100, Jonas Oreland wrote:
> Hi,
>
> I think you hit bug#15303.
>
> The only current work around for this is as you suggested, ndbd --initial.'
>
> Hopefully, we will get around to fixing the bug any time soon
>
That indeed explains why they won't come up.. not why it crashed in the
first place .. :) But I even haven't looked at that yet ..
thnx for the feedback .
Kris
> /Jonas
>
> Kris Buytaert wrote:
> > I`m having troubles restarting ndbd on a node
> >
> >
> > After reporting Bug 17605 a couple of weeks ago, I left my development
> > cluster unattended ,
> >
> > When looking at it again I found out that my 2nd ndbd node was down. It
> > exited some 6 days ago with the error
> > Error object: QMGR (Line: 3826) 0x0000000a
> >
> >
> > Now several days later I try to restart ndbd on that node but it won't
> > come up again :(
> >
> > 2006-03-09 13:45:35 [MgmSrvr] INFO -- Node 2: Node 3: API version
> > 5.1.6
> > 2006-03-09 13:45:35 [MgmSrvr] INFO -- Node 3: Node 2 Connected
> > 2006-03-09 13:45:35 [MgmSrvr] INFO -- Node 3: CM_REGCONF president =
> > 2, own Node = 3, our dynamic id = 5
> > 2006-03-09 13:45:35 [MgmSrvr] INFO -- Node 3: Node 2: API version
> > 5.1.6
> > 2006-03-09 13:45:35 [MgmSrvr] INFO -- Node 3: Start phase 1
> > completed
> > 2006-03-09 13:45:35 [MgmSrvr] INFO -- Node 3: Receive arbitrator
> > node 1 [ticket=7d0c0007df3bb989]
> > 2006-03-09 13:45:37 [MgmSrvr] INFO -- Node 3: Start phase 2
> > completed (node restart)
> > 2006-03-09 13:45:38 [MgmSrvr] INFO -- Node 3: Start phase 3
> > completed (node restart)
> > 2006-03-09 13:45:38 [MgmSrvr] INFO -- Node 3: Start phase 4
> > completed (node restart)
> > 2006-03-09 13:45:45 [MgmSrvr] INFO -- Node 3: DICT: index 10
> > activated
> > 2006-03-09 13:45:45 [MgmSrvr] INFO -- Node 3: DICT: index 11
> > activated
> > 2006-03-09 13:45:45 [MgmSrvr] INFO -- Node 3: DICT: index 13
> > activated
> > 2006-03-09 13:45:45 [MgmSrvr] INFO -- Node 3: DICT: index 14
> > activated
> > 2006-03-09 13:45:45 [MgmSrvr] ALERT -- Node 3: Forced node shutdown
> > completed. Occured during startphase 5. Initiated by signal 0. Caused by
> > error 2341: 'Internal program error (failed ndbrequire)(Internal error,
> > programming error or missing error message, please report a bug).
> > Temporary error
> >
> > On the NDB node the error log shows ..
> >
> >
> > Time: Thursday 9 Mars 2006 - 13:45:34
> > Status: Temporary error, restart node
> > Message: Internal program error (failed ndbrequire) (Internal error,
> > programming error or missing error message, please report a bug)
> > Error: 2341
> > Error data: restore.cpp
> > Error object: RESTORE (Line: 994) 0x0000000a
> > Program: ndbd
> > Pid: 19135
> > Trace: /var/lib/mysql/mysql-cluster//ndb_3_trace.log.5
> > Version: Version 5.1.6 (alpha)
> > ***EOM***
> >
> >
> > A mail from earlier learns me that I should grep for FSOPENREF in my
> > traces however that give me no new info.
> >
> >
> > Any clue on how to fix this (apart from ndbd --initial )
> >
> > greetings
> >
> >
>
>
--
Kris Buytaert <mlkb@stripped>
