Bug #41118 NDBD first start issue on server reboot
Submitted: 29 Nov 2008 2:39 Modified: 11 Aug 2015 7:57
Reporter: Phil Bayfield Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:mysql-5.1-telco-6.3 OS:Linux (Ubuntu 8.10 Server)
Assigned to: CPU Architecture:Any
Tags: 6.3.18-6.3.20, ndbd, reboot, start

[29 Nov 2008 2:39] Phil Bayfield 
Description:
I previously posted this bug but cannot find it in the bug system!

Upon rebooting the server the first start attempt of ndbd fails, the second attempt completes successfully.

Logs attached.

How to repeat:
Rebooting server
Stating ndbd normally
[11 Dec 2008 21:26] Gustaf Thorslund 
Phil,

Can you please provide your config.ini.

Do you get problem after every reboot or just once?

/Gustaf
[12 Dec 2008 9:12] Phil Bayfield 
I have upgraded to 6.3.19 and still had the issue.

Here is my config.ini:

[TCP DEFAULT]
SendBufferMemory=2M
ReceiveBufferMemory=2M

[NDB_MGMD DEFAULT]
PortNumber=1186
Datadir=/var/lib/mysql-cluster

[NDB_MGMD]
Id=1
Hostname=192.168.10.2

[NDB_MGMD]
Id=2
Hostname=192.168.10.3

[NDBD DEFAULT]
NoOfReplicas=2
Datadir=/var/lib/mysql-cluster
DataMemory=3584M
IndexMemory=256M
LockPagesInMainMemory=1

MaxNoOfConcurrentOperations=200000

StringMemory=25
MaxNoOfTables=4096
MaxNoOfOrderedIndexes=2048
MaxNoOfUniqueHashIndexes=512
MaxNoOfAttributes=24576
DiskCheckpointSpeedInRestart=100M
FragmentLogFileSize=256M
NoOfFragmentLogFiles=24
RedoBuffer=32M

TimeBetweenLocalCheckpoints=20
TimeBetweenGlobalCheckpoints=1000
TimeBetweenEpochs=100

MemReportFrequency=3600
BackupReportFrequency=2

### Realtime Extensions
RealTimeScheduler=1
SchedulerExecutionTimer=80
SchedulerSpinTimer=40

### Timeouts
TransactionDeadlockDetectionTimeout=5000
HeartbeatIntervalDbDb=3000
HeartbeatIntervalDbApi=3000

### Disk data related
DiskPageBufferMemory=64M
SharedGlobalMemory=256M

[NDBD]
Id=3
Hostname=192.168.10.6
LockExecuteThreadToCPU=2
LockMaintThreadsToCPU=3

[NDBD]
Id=4
Hostname=192.168.10.7
LockExecuteThreadToCPU=2
LockMaintThreadsToCPU=3

[MYSQLD]
Hostname=192.168.10.4

[MYSQLD]
Hostname=192.168.10.5

[MYSQLD]
Hostname=192.168.10.6

[MYSQLD]
Hostname=192.168.10.7
[12 Dec 2008 9:15] Phil Bayfield 
I have ndbd starting automatically on boot via /etc/init.d/ndbd which simply contains the ndbd command without options.
[9 Jan 2009 23:37] Phil Bayfield 
I have encountered this problem once again after an upgrade to 6.3.20.
[9 Jan 2009 23:38] Phil Bayfield 
Time: Friday 9 January 2009 - 23:22:45
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: dbtup/DbtupRoutines.cpp
Error object: DBTUP (Line: 695) 0x0000000a
Program: ndbd
Pid: 4866
Trace: /var/lib/mysql-cluster/ndb_3_trace.log.3
Version: mysql-5.1.30 ndb-6.3.20-GA
***EOM***
[26 May 2009 12:20] Jonathan Miller 
Are you sure that the networking is up and running before the data nodes are started?

Workaround is to wait for system to full start before starting the Cluster.
[27 May 2009 11:21] Phil Bayfield 
I've not had the problem in more recent versions of cluster.

Currently have 6.3.24 and had no issues with this version whatsoever.