Seems to work here... [root@pcmk-4 ~]# service corosync start Starting corosync (via systemctl): [ OK ] [root@pcmk-4 ~]# systemctl start pacemaker.service [root@pcmk-4 ~]# ps axf PID TTY STAT TIME COMMAND 2 ? S 0:00 [kthreadd] ... 3513 ? Ssl 0:00 corosync 3525 ? S 0:00 /usr/sbin/pacemakerd 3528 ? Ss 0:00 \_ /usr/lib64/heartbeat/stonithd 3529 ? Ss 0:00 \_ /usr/lib64/heartbeat/cib 3530 ? Ss 0:00 \_ /usr/lib64/heartbeat/lrmd 3531 ? Ss 0:00 \_ /usr/lib64/heartbeat/attrd 3532 ? Ss 0:00 \_ /usr/lib64/heartbeat/pengine 3533 ? Ss 0:00 \_ /usr/lib64/heartbeat/crmd [root@pcmk-4 ~]# cat /etc/fedora-release Fedora release 16 (Verne)
On Tue, Dec 6, 2011 at 8:29 AM, Charles DeVoe <scarecrow...@yahoo.com>wrote: > Running Fedora 16. When doing a systemctl start pacemaker.service I get > the following error. > > [root@node2 ]# systemctl status pacemaker.service > pacemaker.service - Pacemaker High Availability Cluster Manager > Loaded: loaded (/lib/systemd/system/pacemaker.service; enabled) > Active: failed since Mon, 05 Dec 2011 15:37:16 -0500; 2min 28s ago > Process: 1947 ExecStart=/usr/sbin/pacemakerd (code=exited, > status=200/CHDIR) > CGroup: name=systemd:/system/pacemaker.service > > However, if I change to /etc/init.d and then enter ./pacemaker it starts. > > Any idea why? > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > >
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org