Description of problem:
When starting the openais service via the init script, it fails to start.
[root@morph-01 init.d]# service openais start
Starting OpenAIS (corosync): corosync [MAIN ] Corosync Cluster Engine ('1.1.2'): started and ready to provide service.
corosync [MAIN ] Corosync built-in features: nss rdma
corosync [MAIN ] Corosync Executive couldn't open configuration component 'openaisserviceenable'
corosync [MAIN ] Corosync Cluster Engine exiting with status -9 at main.c:900.
It appears the export in the init script to set the config parser is incorrect.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create /etc/corosync/openais.conf
2. service openais start
For individuals reading this bug, note the steps to reproduce are to have a proper /etc/corosync/corosync.conf. /etc/corosync/openais.conf is not used.
The problem is that the export line in the init scripts should match that of /usr/sbin/aisexec.
Created attachment 372942 [details]
Patch to openais init script
I spent quite a bit of time figuring out why on earth openais wouldn't start on my F12 test rig - having never played with it before it took a while before I finally figured it out.
I've attached a one-line patch that fixed it for me.
thanks merged upstream. F12 updates are frozen at the moment but we will release an update as soon as the repos become unlocked.
The repos for F12 are open (-updates). I can either fix this by pulling the single patch or wait for another upstream tarball release.
Steven, please let me know what you prefer and timeline for it. I am about to push an update for cluster very soon (aka one or max two days) and I can add openais to the pool.