[Debian-ha-maintainers] Bug#902117: Bug#902117: corosync-qdevice will not daemonize/run

[Jason Gauthier]

On Fri, Jul 6, 2018 at 10:20 AM Valentin Vidic <Valentin.Vidic at carnet.hr> wrote:
>
> On Fri, Jun 22, 2018 at 09:46:36AM -0400, Jason Gauthier wrote:
> > corosync-qdevice is a daemon that runs on each cluster node that help
> > provide a voting subsystem that utilizes corosync-qnet outside the
> > cluster.
> >
> > After installing the packages from debian stretch, and configuring the
> > application, it does not run.  One can use -d and -f to troubleshoot
> > issues, and even in this situation no data is logged to the console,
> > or any syslog messages generated.  The application immediately fails.
>
> corosync-qdevice is configured in corosync.conf, can you share the
> quorum block from there?
>
> If this is not configured I get the following error:
>
> Jul  6 16:08:08 node1 corosync-qdevice[2778]: Can't read quorum.device.model cmap key.
>
> But with a correct configuration it starts fine for me.
>

Interesting.  Let me make some notes.  First, on a 3rd node, I ran
corosync-qnetd, and if not setup then it gives you a nice bulleted
list to complete a certificate based set up.  I did that, and
corosync-qnetd is launched and active on a 3rd node.

Now, it's entirely possible that I do have a configuration issue
causing corosync-qdevice to not start.  However, the real issue is
that corosync-qdevice does not log anything to stdout when run with
"-f -d"  (foreground, debug).

So, if there is a configuration problem I cannot troubleshoot it.  If
I understand the issue correctly, this has something to do with libqb
and (perhaps) the way that it is built.

I grabbed the source code for corosync-qdevice and when I replaced the
logging functionality with a simple varargs based function I was able
to get some output and troubleshoot a little further.

Let me demonstrate:
root at alpha:/home/jgauthier# corosync-qdevice -f -d
root at alpha:/home/jgauthier#

This should result in some form of output.  (This would be a great
test as for you as well)

Now, all that aside, my quorum block looks like this:

quorum {
        # Enable and configure quorum subsystem (default: off)
        # see also corosync.conf.5 and votequorum.5
        #  two_node: 1
        provider: corosync_votequorum
        expected_votes: 3
        device {
            votes: 1
            model: net
            net {
              host: delta
              }
        }

delta is the host for corosync-qnetd.

Jason