RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1446254 - libqb does not support filesystem sockets for IPC on Linux [NEEDINFO]
Summary: libqb does not support filesystem sockets for IPC on Linux
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libqb
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-27 14:13 UTC by Christine Caulfield
Modified: 2017-08-01 18:00 UTC (History)
8 users (show)

Fixed In Version: libqb-1.0.1-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 18:00:14 UTC
Target Upstream Version:
Embargoed:
jpokorny: needinfo?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1896 0 normal SHIPPED_LIVE libqb bug fix and enhancement update 2017-08-01 18:04:56 UTC

Description Christine Caulfield 2017-04-27 14:13:36 UTC 
Description of problem:

libqb currently uses abstract sockets for Inter-Process Communication on Linux - and filesystem sockets on other platforms that don't support abstract sockets.

For use inside containers (where abstract socket names are shared with other containers and the host) this causes name clashes that prevent multiple containers running the same daemons.

Version-Release number of selected component (if applicable):
all Linux versions of libqb

How reproducible:
easily.

Steps to Reproduce:
1. Try to start up 2 containers each running corosync

Actual results:
The second container will fail to bind to the first abstract IPC socket and quit.

Expected results:
Both containers start cleanly and use their own sockets for intra-container communication.

Additional info:
Comment 2 Christine Caulfield 2017-04-28 15:15:05 UTC 
  Branch: refs/heads/master
  Home:   https://github.com/ClusterLabs/libqb
  Commit: 41a24a3df7f894ceb0d66824b52c08e0365c6fc1
      https://github.com/ClusterLabs/libqb/commit/41a24a3df7f894ceb0d66824b52c08e0365c6fc1
  Author: Chrissie Caulfield <ccaulfie>
  Date:   2017-04-28 (Fri, 28 Apr 2017)

  Changed paths:
    M configure.ac
    M docs/mainpage.h
    M lib/ipc_int.h
    M lib/ipc_setup.c
    M lib/ipc_socket.c
    M tests/check_ipc.c
Comment 3 Jan Pokorný [poki] 2017-05-04 13:20:44 UTC 
In re reproducer:

As containers are often used to run parallel instances, corosync is not
really the best example (running with realtime scheduling priority...)
and furthermore, for a production use, creating a pseudo-cluster within
containers is completely superfluous and waste of resources, so putting
corosync and containers into a single sentence should be frowned upon.

This may be a bit better:

0. have a top-level machine + container within
1. in both:
   # yum install pacemaker
2. in a top-level:
   # /usr/libexec/pacemaker/lrmd
>  [daemonized and still runs]
3. in a container:
   # /usr/libexec/pacemaker/lrmd
   # tail /var/log/pacemaker.log
>  May 04 15:04:38 [4244] f26       lrmd:     info: crm_log_init:       Changed active directory to /var/lib/pacemaker/cores
>  May 04 15:04:38 [4244] f26       lrmd:     info: qb_ipcs_us_publish: server name: lrmd
>  May 04 15:04:38 [4244] f26       lrmd:     info: main:       Starting
>  May 04 15:07:00 [4249] f26       lrmd:     info: crm_log_init:       Changed active directory to /var/lib/pacemaker/cores
>  May 04 15:07:00 [4249] f26       lrmd:     info: qb_ipcs_us_publish: server name: lrmd
>  May 04 15:07:00 [4249] f26       lrmd:    error: qb_ipcs_us_publish: Could not bind AF_UNIX (): Address already in use (98)
   ^ this line is clear on what's wrong
>  May 04 15:07:00 [4249] f26       lrmd:     info: qb_ipcs_us_withdraw:        withdrawing server sockets
>  May 04 15:07:00 [4249] f26       lrmd:    error: mainloop_add_ipc_server:    Could not start lrmd IPC server: Address already in use (-98)
>  May 04 15:07:00 [4249] f26       lrmd:    error: main:       Failed to create IPC server: shutting down and inhibiting respawn
>  May 04 15:07:00 [4249] f26       lrmd:     info: crm_xml_cleanup:    Cleaning up memory from libxml2
Comment 4 Jan Pokorný [poki] 2017-05-04 13:23:48 UTC 
With the fix and when the step 3. is modified as follows:

3. in a container:
   # touch /etc/libqb/force-filesystem-sockets
   # /usr/libexec/pacemaker/lrmd
 
the lrmd process should keep running in the container,
just as it keeps running outside.
Comment 6 Jan Pokorný [poki] 2017-05-17 08:26:50 UTC 
This enforcing feature raises the importance of having memleaks
identified a while back finally fixed at the same time the feature
is rolled out:

https://github.com/ClusterLabs/libqb/pull/194

(Perhaps as the whole new upstream release + rebase?)
Comment 14 errata-xmlrpc 2017-08-01 18:00:14 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1896
Note You need to log in before you can comment on or make changes to this bug.