CTDB doesn't start again after it was stopped once

[Андрей Гребенников]

Hi!
Could anyone help me with my CTDB which is in the pacemaker? When I stop 
the cluster service on the one node and start it again the CTDB doesn't 
start on it. The log.ctdb is:

2011/07/08 12:03:55.353333 [ 6863]: Starting CTDB daemon
2011/07/08 12:03:55.375698 [ 6864]: Starting CTDBD as pid : 6864
2011/07/08 12:03:55.375798 [ 6864]: Set scheduler to SCHED_FIFO
2011/07/08 12:03:55.375871 [ 6864]: server/ctdb_logging.c:430 Created 
PIPE FD:7 for logging
2011/07/08 12:03:55.379323 [ 6864]: Vacuuming is disabled for persistent 
database share_info.tdb
2011/07/08 12:03:55.379344 [ 6864]: Attached to persistent database 
share_info.tdb
2011/07/08 12:03:55.379391 [ 6864]: Vacuuming is disabled for persistent 
database passdb.tdb
2011/07/08 12:03:55.379406 [ 6864]: Attached to persistent database 
passdb.tdb
2011/07/08 12:03:55.379454 [ 6864]: Vacuuming is disabled for persistent 
database registry.tdb
2011/07/08 12:03:55.379469 [ 6864]: Attached to persistent database 
registry.tdb
2011/07/08 12:03:55.379511 [ 6864]: Vacuuming is disabled for persistent 
database idmap2.tdb
2011/07/08 12:03:55.379527 [ 6864]: Attached to persistent database 
idmap2.tdb
2011/07/08 12:03:55.379574 [ 6864]: Vacuuming is disabled for persistent 
database account_policy.tdb
2011/07/08 12:03:55.379591 [ 6864]: Attached to persistent database 
account_policy.tdb
2011/07/08 12:03:55.379633 [ 6864]: Vacuuming is disabled for persistent 
database secrets.tdb
2011/07/08 12:03:55.379648 [ 6864]: Attached to persistent database 
secrets.tdb
2011/07/08 12:03:55.381002 [ 6864]: Keepalive monitoring has been started
2011/07/08 12:03:55.381057 [ 6864]: Monitoring has been started
2011/07/08 12:03:55.381171 [ 6869]: server/ctdb_recoverd.c:3360 Created 
PIPE FD:19 to recovery daemon
2011/07/08 12:03:55.381253 [ 6869]: monitor_cluster starting
2011/07/08 12:03:55.834110 [ 6864]: tcp/tcp_connect.c:261 Created SOCKET 
FD:24 to incoming ctdb connection
2011/07/08 12:03:59.340552 [ 6869]: server/ctdb_recoverd.c:905 Election 
timed out
2011/07/08 12:03:59.397117 [ 6869]: server/ctdb_recoverd.c:2340 in the 
middle of recovery or ip reallocation. skipping public ip address check
2011/07/08 12:03:59.397384 [ 6869]: server/ctdb_recoverd.c:2130 Node:1 
was in recovery mode. Restart recovery process
2011/07/08 12:03:59.397405 [ 6869]: server/ctdb_recoverd.c:1234 Starting 
do_recovery
2011/07/08 12:03:59.397418 [ 6869]: Taking out recovery lock from 
recovery daemon
2011/07/08 12:03:59.397436 [ 6869]: Take the recovery lock
2011/07/08 12:04:03.915544 [ 6864]: Freeze priority 1
2011/07/08 12:04:03.915949 [ 6864]: Freeze priority 2
2011/07/08 12:04:03.916289 [ 6864]: Freeze priority 3
2011/07/08 12:04:07.927278 [ 6864]: Freeze priority 1
2011/07/08 12:04:07.927620 [ 6864]: Freeze priority 2
2011/07/08 12:04:07.927985 [ 6864]: Freeze priority 3
2011/07/08 12:04:11.939460 [ 6864]: Freeze priority 1
2011/07/08 12:04:11.939852 [ 6864]: Freeze priority 2
2011/07/08 12:04:11.940204 [ 6864]: Freeze priority 3
2011/07/08 12:04:15.951252 [ 6864]: Freeze priority 1
2011/07/08 12:04:15.951633 [ 6864]: Freeze priority 2
2011/07/08 12:04:15.952033 [ 6864]: Freeze priority 3
2011/07/08 12:04:19.963176 [ 6864]: Freeze priority 1
2011/07/08 12:04:19.963512 [ 6864]: Freeze priority 2
2011/07/08 12:04:19.963893 [ 6864]: Freeze priority 3
2011/07/08 12:04:23.975116 [ 6864]: Freeze priority 1
2011/07/08 12:04:23.975500 [ 6864]: Freeze priority 2
2011/07/08 12:04:23.975813 [ 6864]: Freeze priority 3
2011/07/08 12:04:25.380502 [ 6864]: Release freeze handler for prio 1
2011/07/08 12:04:25.380670 [ 6864]: Release freeze handler for prio 2
2011/07/08 12:04:25.380895 [ 6864]: Release freeze handler for prio 3
2011/07/08 12:04:27.986839 [ 6864]: Freeze priority 1
2011/07/08 12:04:27.987756 [ 6864]: Freeze priority 2
2011/07/08 12:04:27.988467 [ 6864]: Freeze priority 3
2011/07/08 12:04:31.999668 [ 6864]: Freeze priority 1
2011/07/08 12:04:32.000493 [ 6864]: Freeze priority 2
2011/07/08 12:04:32.001943 [ 6864]: Freeze priority 3
2011/07/08 12:04:36.011031 [ 6864]: Freeze priority 1
2011/07/08 12:04:36.011348 [ 6864]: Freeze priority 2
2011/07/08 12:04:36.011657 [ 6864]: Freeze priority 3
2011/07/08 12:04:40.022785 [ 6864]: Freeze priority 1
2011/07/08 12:04:40.023184 [ 6864]: Freeze priority 2
2011/07/08 12:04:40.023412 [ 6864]: Freeze priority 3
2011/07/08 12:04:44.034657 [ 6864]: Freeze priority 1
2011/07/08 12:04:44.035006 [ 6864]: Freeze priority 2
2011/07/08 12:04:44.035310 [ 6864]: Freeze priority 3
2011/07/08 12:04:48.046488 [ 6864]: Freeze priority 1
2011/07/08 12:04:48.046806 [ 6864]: Freeze priority 2
2011/07/08 12:04:48.047086 [ 6864]: Freeze priority 3
2011/07/08 12:04:52.054598 [ 6864]: Freeze priority 1
2011/07/08 12:04:52.054951 [ 6864]: Freeze priority 2
2011/07/08 12:04:52.055293 [ 6864]: Freeze priority 3
2011/07/08 12:04:56.066139 [ 6864]: Freeze priority 1
2011/07/08 12:04:56.066457 [ 6864]: Freeze priority 2
2011/07/08 12:04:56.066838 [ 6864]: Freeze priority 3
2011/07/08 12:04:57.987741 [ 6864]: Release freeze handler for prio 1
2011/07/08 12:04:57.988370 [ 6864]: Release freeze handler for prio 2
2011/07/08 12:04:57.989012 [ 6864]: Release freeze handler for prio 3
2011/07/08 12:04:59.400809 [ 6864]: Recovery daemon ping timeout. Count : 0
2011/07/08 12:05:00.078206 [ 6864]: Freeze priority 1
2011/07/08 12:05:00.079234 [ 6864]: Freeze priority 2
2011/07/08 12:05:00.079922 [ 6864]: Freeze priority 3
2011/07/08 12:05:04.089986 [ 6864]: Freeze priority 1
2011/07/08 12:05:04.091286 [ 6864]: Freeze priority 2
2011/07/08 12:05:04.092179 [ 6864]: Freeze priority 3
2011/07/08 12:05:08.100709 [ 6864]: Freeze priority 1
2011/07/08 12:05:08.101047 [ 6864]: Freeze priority 2
2011/07/08 12:05:08.101301 [ 6864]: Freeze priority 3
2011/07/08 12:05:12.108635 [ 6864]: Freeze priority 1
2011/07/08 12:05:12.108969 [ 6864]: Freeze priority 2
2011/07/08 12:05:12.109272 [ 6864]: Freeze priority 3
2011/07/08 12:05:16.116421 [ 6864]: Freeze priority 1
2011/07/08 12:05:16.116728 [ 6864]: Freeze priority 2
2011/07/08 12:05:16.117088 [ 6864]: Freeze priority 3
2011/07/08 12:05:20.124435 [ 6864]: Freeze priority 1
2011/07/08 12:05:20.124784 [ 6864]: Freeze priority 2
2011/07/08 12:05:20.125117 [ 6864]: Freeze priority 3
2011/07/08 12:05:24.130379 [ 6864]: Banning this node for 300 seconds
2011/07/08 12:05:24.132183 [ 6864]: This node has been banned - forcing 
freeze and recovery
2011/07/08 12:05:24.793300 [ 6864]: This node has been banned - forcing 
freeze and recovery
2011/07/08 12:05:30.079164 [ 6864]: Release freeze handler for prio 1
2011/07/08 12:05:30.079856 [ 6864]: Release freeze handler for prio 2
2011/07/08 12:05:30.080530 [ 6864]: Release freeze handler for prio 3
2011/07/08 12:05:36.293973 [ 6864]: Shutting down recovery daemon
2011/07/08 12:05:36.294051 [ 6864]: Monitoring has been stopped


What's the problem?