---
name: "ocf_heartbeat_eDir88"
section: "7"
platform: "linux"
package: "resource-agents"
version: "1:4.16.0-3+deb13u2"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/ocf_heartbeat_eDir88"
---

# ocf\_heartbeat\_eDir88(7)

Manages a Novell eDirectory directory server

## NAME

ocf\_heartbeat\_eDir88 - Manages a Novell eDirectory directory server

## SYNOPSIS

**eDir88** \[start \| stop \| monitor \| meta-data \| validate-all\]

## DESCRIPTION

Resource script for managing an eDirectory instance. Manages a single instance of eDirectory as an HA resource. The "multiple instances" feature or eDirectory has been added in version 8.8. This script will not work for any version of eDirectory prior to 8.8. This RA can be used to load multiple eDirectory instances on the same host.

It is very strongly recommended to put eDir configuration files (as per the eDir\_config\_file parameter) on local storage on each node. This is necessary for this RA to be able to handle situations where the shared storage has become unavailable. If the eDir configuration file is not available, this RA will fail, and heartbeat will be unable to manage the resource. Side effects include STONITH actions, unmanageable resources, etc...

Setting a high action timeout value is \_very\_ \_strongly\_ recommended. eDir with IDM can take in excess of 10 minutes to start. If heartbeat times out before eDir has had a chance to start properly, mayhem \_WILL ENSUE\_.

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, as the start command will wait for IDM and LDAP to be available.

## SUPPORTED PARAMETERS

**eDir\_config\_file**

Path to configuration file for eDirectory instance.

(unique, optional, string, default "/etc/opt/novell/eDirectory/conf/nds.conf")

**eDir\_monitor\_ldap**

Should we monitor if LDAP is running for the eDirectory instance?

(optional, boolean, default 0)

**eDir\_monitor\_idm**

Should we monitor if IDM is running for the eDirectory instance?

(optional, boolean, default 0)

**eDir\_jvm\_initial\_heap**

Value for the DHOST\_INITIAL\_HEAP java environment variable. If unset, java defaults will be used.

(optional, integer, no default)

**eDir\_jvm\_max\_heap**

Value for the DHOST\_MAX\_HEAP java environment variable. If unset, java defaults will be used.

(optional, integer, no default)

**eDir\_jvm\_options**

Value for the DHOST\_OPTIONS java environment variable. If unset, original values will be used.

(optional, string, no default)

## SUPPORTED ACTIONS

This resource agent supports the following actions (operations):

**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)](/crm/8.md) shell:

```
primitive p_eDir88 ocf:heartbeat:eDir88 \
  op monitor timeout="60s" interval="30s"
```

## EXAMPLE PCS

The following is an example configuration for a eDir88 resource using [**pcs**(8)](/pcs/8.md)

```
pcs resource create p_eDir88 ocf:heartbeat:eDir88 \
  op monitor timeout="60s" interval="30s"
```

## SEE ALSO

**http://clusterlabs.org/**

## AUTHOR

**ClusterLabs contributors (see the resource agent source for information about individual authors)**