[Bugs] [Bug 1550894] New: GD2 fails to dlopen server xlator
bugzilla at redhat.com
bugzilla at redhat.com
Fri Mar 2 08:23:13 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1550894
Bug ID: 1550894
Summary: GD2 fails to dlopen server xlator
Product: GlusterFS
Version: 4.0
Component: core
Keywords: Triaged
Severity: urgent
Priority: urgent
Assignee: kaushal at redhat.com
Reporter: kaushal at redhat.com
CC: bugs at gluster.org
Blocks: 1539842 (glusterfs-4.0.0)
Description of problem:
GD2 fails to open the server xlator to read its options. This causes GD2 to
fail to start.
The reason for this is because, server xlator uses two external function from
glusterfsd, glusterfs_mgmt_pmap_signout and glusterfs_autoscale_threads. These
functions are not resolved when dlopen tries to load the xlator, causing it to
fail with 'undefined symbol' error.
This is not a problem with normal brick operation, as the server xlator is
loaded by glusterfsd, which already has the relevant symbols defined.
Version-Release number of selected component (if applicable):
4.0.0rc1
How reproducible:
Reproducible on packaged RPMs of GlusterFS-v4.0.0rc1 on Fedora and
GlusterD2-v4.0.0rc1 always.
Steps to Reproduce:
1. On Fedora 27, install GlusterFS-v4.0.0rc1 from [1] and GlusterD2-v4.0.0rc1
2. Start glusterd2.
Actual results:
GD2 fails to start with logged error,
```
FATA[2018-02-28 15:02:53.345686] Failed to load xlator options
error="dlopen(/usr/lib64/glusterfs/4.0.0rc1/xlator/protocol/server.so) failed;
dlerror = /usr/lib64/glusterfs/4.0.0rc1/xlator/protocol/server.so: undefined
symbol: glusterfs_mgmt_pmap_signout" source="[main.go:79:main.main]"
```
Expected results:
GD2 should not fail to start.
Additional info:
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1539842
[Bug 1539842] GlusterFS 4.0.0 tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=D6vPNRzBxv&a=cc_unsubscribe
More information about the Bugs
mailing list