On Thursday, January 08, 2015 02:25:50 pm Gao,Yan wrote:
> Actually, for corosync-2, the decent way would be an init script or a
> systemd service file for mgmtd to start it after pacemaker. Patches are
> welcome ;)
>
Your wish is my command ;)
You can find systemd pacemaker-mgmt.service at
http
Hi all,
In the past I have put to good use the pacemaker-mgmt (crm_gui) , mostly when
I have to
delegate management of cluster to third person, so much easier to explain ...
So for latest cluster I managed to get pacemaker-mgmt working on Fedora 20
(since it is not so straight forward
I include
Hi all,
anybody knows why am i getting these messages in my logs:
...
Mar 28 10:50:11 i2 systemd: pacemaker.service: Got notification message from
PID 23055, but reception only permitted for PID 4726
Mar 28 10:50:21 i2 systemd: pacemaker.service: Got notification message from
PID 23055, but rec
On Friday, March 21, 2014 08:59:27 pm David Vossel wrote:
>
> This could be a pcs bug. If using --force works, this is definitely a pcs
> bug. pcs is supposed to be looking through /etc/init.d/* on the local
> machine for valid lsb scripts before applying a lsb resource into the cluster
> conf
Hi all,
I'm trying to create a lsb resource with pcs on fedora 20 and I'm failing
miserably every time: (have sucessfully created ocf resources though)
# pcs resource create impulz_dosemu lsb:impulz op stop interval=0 timeout=60s
monitor interval=60s timeout=5s start interval=0 timeout=60s
Erro
