[Pacemaker] monitor domain controller

Michael Schwartzkopff misch at clusterbau.com
Thu May 2 04:39:28 EDT 2013

Am Donnerstag, 2. Mai 2013, 08:32:19 schrieb James Harper:
> Currently I am using a ping resource to ensure that other windows VM's don't
> start up until the domain controllers are started. This helps prevent
> things like Exchange not starting properly because they can't find a domain
> controller.
> On a complete network shutdown (eg a long power failure), windows domain
> controllers can take quite a while to start servicing active directory
> requests if there are no other domain controllers on the network, in the
> order of 5-20 minutes, but they do respond to pings (depending on firewall
> rules) so my other VM's start up too early.
> Has anyone else solved this problem? I'm thinking that I'll simply have a
> resource that does an nslookup for the active directory domain name on the
> selected domain controllers, like ping does, (dns won't service active
> directory related requests until domain services are active), but maybe
> someone else has done it better?
> Thanks
> James


the VirtualDomain resource agent provides the parameter monitor_scripts. This 
hook is a space separated list of your scripts that monitors the virtual 
machine. You can take some inspriration the nagios check scripts to monitor 
your domain controller.

Be sure to make the timeout of the start operation long enough.


Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130502/9790e126/attachment-0003.html>

More information about the Pacemaker mailing list