[ClusterLabs] corosync-qdevice doesn't daemonize (or stay running)

[Jason Gauthier]

On Tue, Jun 19, 2018 at 6:58 AM Christine Caulfield <ccaulfie at redhat.com> wrote:
>
> On 19/06/18 11:44, Jason Gauthier wrote:
> > On Tue, Jun 19, 2018 at 3:25 AM Christine Caulfield <ccaulfie at redhat.com> wrote:
> >>
> >> On 19/06/18 02:46, Jason Gauthier wrote:
> >>> Greetings,
> >>>
> >>>    I've just discovered corosync-qdevice and corosync-qnet.
> >>> (Thanks Ken Gaillot) . Set up was pretty quick.
> >>>
> >>> I enabled qnet off cluster.  I followed the steps presented by
> >>> corosync-qdevice-net-certutil.    However, when running
> >>> corosync-qdevice it exits.  Even with -f -d there isn't a single
> >>> output presented.
> >>>
> >>
> >> It sounds like the first time you ran it (without -d -f)
> >> corosync-qdevice started up and daemonised itself. The second time you
> >> tried (with -d -f) it couldn't run because there was already one
> >> running. There's a good argument for it printing an error if it's
> >> already running I think!
> >>
> >
> > The process doesn't stay running.  I've showed in output of qnet below
> > that it launches, connected, and disconnects. I've rebooted several
> > times since then (testing stonith). I can provide strace output if
> > it's helpful.
> >
>
> yes please

Attached!


>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qdevice.log
Type: application/octet-stream
Size: 53307 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180619/09ea3570/attachment-0002.obj>