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

[Christine Caulfield]

On 21/06/18 12:05, Jason Gauthier wrote:
> On Thu, Jun 21, 2018 at 5:11 AM Christine Caulfield <ccaulfie at redhat.com> wrote:
>>
>> On 19/06/18 18:47, Jason Gauthier wrote:
>>> 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!
>>>
>>
>> That's very odd. I can see communication with the server and corosync in
>> there (do it's doing something) but no logging at all. When I start
>> qdevice on my systems it logs loads of messages even if it doesn't
>> manage to contact the server. Do you have any logging entries in
>> corosync.conf that might be stopping it?
> 
> I haven't checked the corosync logs for any entries before, but I just
> did.  There isn't anything logged.
> 
>> Where did the binary come from? did you build it yourself or is it from
>> a package? I wonder if it's got corrupted or is a bad version. Possibly
>> linked against a 'dodgy' libqb - there have been some things going on
>> there that could cause logging to go missing in some circumstances.
>>
>> Honza (the qdevice expert) is away at the moment, so I'm guessing a bit
>> here anyway!
> 
> Hmm. Interesting.  I installed the debian package.  When it didn't
> work, I grabbed the source from github.  They both act the same way,
> but if there is an underlying library issue then that will continue to
> be a problem.
> 
> It doesn't say much:
> /usr/lib/x86_64-linux-gnu/libqb.so.0.18.1
> 
> 

I just tried this on my Debian VM and it does exactly the same as yours.
So I think you should report it to the Debian maintainer as it doesn't
happen on my Fedora or RHEL systems

Chrissie