Comment 39 for bug 1572521
Revision history for this message
| Oleksiy Molchanov (omolchanov) wrote Re: Pacemaker resources are failed to start after the nodes cold reboot | #39 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
@Aleksandr, I want to comment under this:
---
2) `Non-controller nodes should sync time with the same ntp-server as controllers` approach couldn't working by the same reason: the cluster IS BROKEN. There is no difference between servers for sync, because ntp is not running.
---
For initial time sync we do not need any cluster to be working. In your test-case you are syncing controller nodes with master and non-controller nodes with ntp under pacemaker on controllers. Why don't you sync it with master too?
What I observed under my env where nodes have 3G and 1 CPU:
It took ~10 minutes to bring up ntp resource in pacemaker, after that I can easily run ntpdate pointing it to vrouter_vip.
http://
So, my suggestion is still the same:
>>> I think you should sync time with master node for all nodes. Or wait for ntp resource is up, but I prefere first approach.