Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have developed an external Heartbeat v1 plugin, which expects its configuration by means of environment variables.

AFAIK, this is what Heartbeat provides when configuring the plugin using the following entry in /etc/heartbeat/

stonith external/my_plugin /etc/ha.d/my_plugin-hostname.conf

What I am not quite certain about is the format that /etc/ha.d/my_plugin-<hostname>.conf is supposed to have (as documentation seem to be somewhat non-existent). Right now, I used the following attempt:

<hostname> target <hostname>
<hostname> auth_token <some_token>
<hostname> proxy_uri <some_url>

Unfortunately, my_plugin is called with the following parameters:

target: <hostname>
auth_token: proxy_uri
proxy_uri <some_url>

So, the auth_token parameter is messed up and I frankly have no clue why... I am dumping the environment using export at the beginning of the script, so I am quite certain that this is what heartbeat supplies the script with.

Any ideas?

share|improve this question
up vote 0 down vote accepted

Got it: The config file format is actually a space-delimited list of the configuration parameters in the order returned by the getconfignames operation (target auth_token proxy_uri in my case), so the file correctly looks like this:

<hostname> <some_token> <some_url>
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.