[Pacemaker] Strange behavior when starting up Corosync in a single node setup

[Stephan-Frank Henry]

Hello again,

new week new problem. :D

Setup:
Single node setup (default via my installer)
/etc/hosts
127.0.0.1	localhost
172.16.0.1	cmsserver001

the installer basically already takes care of setting everything up for a single node by using both above as nodes in the drbd.conf. This has been proven to work in other setups, though we are having problems with exactly these settings.

When corosync starts up, it throws these errors a few times:

Sep 10 09:50:04 cmsserver001 crmd: [4990]: info: crm_timer_popped: Election Trigger (I_DC_TIMEOUT) just popped!
Sep 10 09:50:04 cmsserver001 crmd: [4990]: WARN: do_log: FSA: Input I_DC_TIMEOUT from crm_timer_popped() received in state S_PENDING
Sep 10 09:50:04 cmsserver001 crmd: [4990]: info: do_state_transition: State transition S_PENDING -> S_ELECTION [ input=I_DC_TIMEOUT cause=C_TIMER_POPPED origin=crm_timer_popped ]

I have checked all the usual suspects (hosts, interfaces, ifconfig, et al) and found nothing that could indicate a problem.

A quick google indicated that it could be a firewall issue. Though we are using a firewall (firehol), it is by default set to pass-through all traffic.

Though what we can see are a lot of ntp messages:
Sep 10 09:49:57 cmsserver001 named[3360]: network unreachable resolving '2.debian.pool.ntp.org/A/IN': 2001:dc3::35#53

Could this be the issue?

Funny thing is, as soon as we set up the node with an 'real' ip in the network, it works fine.

Does anyone have any ideas?

thanks

Frank
-- 
GMX DSL SOMMER-SPECIAL: Surf & Phone Flat 16.000 für nur 19,99 Euro/mtl.!*
http://portal.gmx.net/de/go/dsl