OCF_HEARTBEAT_EDIR88(7)
π ocf_heartbeat_eDir88 β the girlies' guide to running Novell eDirectory as an HA resource π
okay bestie, sit down, grab a strawberry π, because we're about to talk about ocf_heartbeat_eDir88 β it's the eDir88 resource agent, and it manages a Novell eDirectory directory server. That's the whole NAME situation, no cap. β¨
β¨ SYNOPSIS β¨
eDir88 [start | stop | monitor | meta-data | validate-all]
that's it. that's the whole vibe check. π¦
πΈ DESCRIPTION πΈ
So this is a resource script for managing an eDirectory instance, right? It manages a single instance of eDirectory as an HA resource. The "multiple instances" feature of eDirectory was added in version 8.8, and here's the thing β this script will not work for any version of eDirectory prior to 8.8. π So don't come crying to me with your 8.7, bestie, I can't help you. But if you are on 8.8+, this RA can be used to load multiple eDirectory instances on the same host. slay. π
okay listen, this part is IMPORTANT: it is very strongly recommended to put eDir configuration files (as per the eDir_config_file parameter) on local storage on each node. Why? because this RA needs to be able to handle situations where the shared storage has become unavailable. And if the eDir configuration file isn't available, this RA will fail, and heartbeat will be unable to manage the resource. Side effects include STONITH actions, unmanageable resources, etc... π like, the drama is real.
Setting a high action timeout value is _very_ _strongly_ recommended. eDir with IDM can take in excess of 10 minutes to start. And if heartbeat times out before eDir has had a chance to start properly, mayhem _WILL ENSUE_. not "might". not "could". WILL. periodt. π
Also, tea time β: the LDAP module seems to be one of the very last to start. So this script will take even longer to start on installations with IDM and LDAP if the monitoring of IDM and/or LDAP is enabled, because the start command will wait for IDM and LDAP to be available. it's giving "patiently waiting for the last girl to get ready" energy. π
π SUPPORTED PARAMETERS π
eDir_config_fileβ Path to configuration file for eDirectory instance.- (unique, optional, string, default
/etc/opt/novell/eDirectory/conf/nds.conf)
- (unique, optional, string, default
eDir_monitor_ldapβ Should we monitor if LDAP is running for the eDirectory instance?- (optional, boolean, default
0)
- (optional, boolean, default
eDir_monitor_idmβ Should we monitor if IDM is running for the eDirectory instance?- (optional, boolean, default
0)
- (optional, boolean, default
eDir_jvm_initial_heapβ Value for theDHOST_INITIAL_HEAPjava environment variable. If unset, java defaults will be used.- (optional, integer, no default)
eDir_jvm_max_heapβ Value for theDHOST_MAX_HEAPjava environment variable. If unset, java defaults will be used.- (optional, integer, no default)
eDir_jvm_optionsβ Value for theDHOST_OPTIONSjava environment variable. If unset, original values will be used.- (optional, string, no default)
π SUPPORTED ACTIONS π
This resource agent supports the following actions (operations), bestie β memorize them, there's a quiz later (there is not a quiz):
startβ Starts the resource. Suggested minimum timeout: 600s. β°stopβ Stops the resource. Suggested minimum timeout: 600s. β°monitorβ Performs a detailed status check. Suggested minimum timeout: 60s. Suggested interval: 30s. πmeta-dataβ Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s.validate-allβ Performs a validation of the resource configuration. Suggested minimum timeout: 5s.
π¦ EXAMPLE CRM SHELL π¦
The following is an example configuration for a eDir88 resource using the crm(8) shell:
primitive p_eDir88 ocf:heartbeat:eDir88 \
op monitor timeout="60s" interval="30s"
look at her. iconic. π
π EXAMPLE PCS π
The following is an example configuration for a eDir88 resource using pcs(8):
pcs resource create p_eDir88 ocf:heartbeat:eDir88 \
op monitor timeout="60s" interval="30s"
same energy, different tool. we love versatility. π«Ά
π SEE ALSO π
π§ AUTHOR π§
ClusterLabs contributors (see the resource agent source for information about individual authors)
and that's the whole page, bestie!! this wasresource-agents UNKNOWN, dated04/08/2026, and it lives in theOCF_HEARTBEAT_EDIR88(7)manual section. go forth and manage your eDirectory instance responsibly, mwah πβ¨
π¦ where this page comes from
- fedora 43: resource-agents 4.18.0-1.fc43 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
- fedora 44: resource-agents 4.18.0-1.fc44 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms