> On 14 Nov 2014, at 6:54 am, Grüninger, Andreas (LGL Extern) > <andreas.gruenin...@lgl.bwl.de> wrote: > > I am really sorry but I forgot the reason. It is now 2 years ago when I had > problems with starting pacemaker as root. > When I remember well pacemaker got always access denied when connection to > corosync. > With a non-root account it worked flawlessly.
Oh!!!! That would be this patch: https://github.com/beekhof/pacemaker/commit/3c9275e9 I always thought there was a philosophical objection. > > The pull request from branch upstream3 can be closed. > There is a new pull request from branch upstream4 with the changes against > the current master. Excellent > > > -----Ursprüngliche Nachricht----- > Von: Andrew Beekhof [mailto:and...@beekhof.net] > Gesendet: Donnerstag, 13. November 2014 12:11 > An: The Pacemaker cluster resource manager > Betreff: Re: [Pacemaker] Notes on pacemaker installation on OmniOS > > >> On 13 Nov 2014, at 9:50 pm, Grüninger, Andreas (LGL Extern) >> <andreas.gruenin...@lgl.bwl.de> wrote: >> >> I added heartbeat and corosync to have both available. >> Personally I use pacemaker/corosync. >> >> There is no need any more to run pacemaker as non-root with the newest >> version of pacemaker. > > I'm curious... what was the old reason? > >> >> The main problems with pacemaker are the changes in the last months >> especially in services_linux.c. >> As the name implies this must be a problem with non-linux systems. >> What is your preferred way to handle e.g. pure linux kernel functions? > > Definitely to isolate them with an appropriate #define (preferably by feature > availability rather than OS) > >> >> I compiled a version of pacemaker yesterday but with a revision of pacemaker >> from august. >> There are pull requests waiting with patches for Solaris/Illumos. >> I guess it would be better to add this patches from august and my patches >> from yesterday to the current master. >> Following the patch from Vincenco I changed services_os_action_execute in >> services_linux.c and added for non-linux systems the synchronous wait with >> ppoll which is available for Solaris/BSD/MacOS. Should be same >> functionality as this function uses file descriptors and signal handlers. >> Can pull requests be rejected or redrawn? > > Is there anything left in them that needs to go in? > If so, can you indicate which parts are needed in those pull requests please? > The rest we can close - I didn't want to close them in case there was > something I had missed. > >> >> Andreas >> >> >> -----Ursprüngliche Nachricht----- >> Von: Andrew Beekhof [mailto:and...@beekhof.net] >> Gesendet: Donnerstag, 13. November 2014 11:13 >> An: The Pacemaker cluster resource manager >> Betreff: Re: [Pacemaker] Notes on pacemaker installation on OmniOS >> >> Interesting work... a couple of questions... >> >> - Why heartbeat and corosync? >> - Why the need to run pacemaker as non-root? >> >> Also, I really encourage the kinds of patches referenced in these >> instructions to bring them to the attention of upstream so that we can work >> on getting them merged. >> >>> On 13 Nov 2014, at 7:09 pm, Vincenzo Pii <p...@zhaw.ch> wrote: >>> >>> Hello, >>> >>> I have written down my notes on the setup of pacemaker and corosync on >>> IllumOS (OmniOS). >>> >>> This is just the basic setup, to be in condition of running the Dummy >>> resource agent. It took me quite some time to get this done, so I want to >>> share what I did assuming that this may help someone else. >>> >>> Here's the link: >>> http://blog.zhaw.ch/icclab/use-pacemaker-and-corosync-on-illumos-omni >>> o >>> s-to-run-a-ha-activepassive-cluster/ >>> >>> A few things: >>> >>> * Maybe this setup is not optimal for how resource agents are managed >>> by the hacluster user instead of root. This led to some problems, >>> check this thread: >>> https://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg20834.h >>> t >>> ml >>> * I took some scripts and the general procedure from Andreas and his page >>> here: http://grueni.github.io/libqb/. Many thanks! >>> >>> Regards, >>> Vincenzo. >>> >>> -- >>> Vincenzo Pii >>> Researcher, InIT Cloud Computing Lab >>> Zurich University of Applied Sciences (ZHAW) blog.zhaw.ch/icclab >>> _______________________________________________ >>> 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 >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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
