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

Jan Pokorný jpokorny at redhat.com
Thu Jun 21 09:48:58 EDT 2018

On 21/06/18 07:05 -0400, 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:
>>> 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.

What about syslog entries (may boil down to /var/log/messages,
journald log, or whatever sink is configured)?

>> 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

You are likely using libqb v1.0.1.

Ability to figure out the proper package version is one of the most
basic skills to provide useful diagnostics about the issues with
distro-provided packages.

With Debian, the proper incantation seems to be

  dpkg -s libqb-dev | grep -i version


  apt list libqb-dev

(or substitute libqb0 for libqb-dev).

As Chrissie mentioned, there is some fishiness possible if you happen
to use ld linker from binutils 2.29+ for the building with this old
libqb in the mix, so if the issues persist and logging seems to be
missing, try recompiling with the downgraded binutils package below
said breakage point.

Hope this helps.

Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180621/f954dc82/attachment-0002.sig>

More information about the Users mailing list