Bug 1243351
| Summary: | Warning messages seen in glusterd logs when installed from RHGS 3.1 ISO based on RHEL 7.1 | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> | |
| Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | |
| Status: | CLOSED ERRATA | QA Contact: | Byreddy <bsrirama> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.1 | CC: | amukherj, asrivast, nlevinki, olim, rhinduja, vbellur | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | RHGS 3.1.3 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | glusterd | |||
| Fixed In Version: | glusterfs-3.7.9-1 | Doc Type: | Bug Fix | |
| Doc Text: |
Incorrect voltypes were associated with the config.memory-accounting and config.transport options. This meant that permission warnings were logged erroneously when users ran 'gluster volume set help'. The voltypes for these options have been corrected, and the warnings are no longer logged in this situation.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1283485 (view as bug list) | Environment: |
RHEL7
|
|
| Last Closed: | 2016-06-23 05:26:44 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1283485, 1283833, 1283834 | |||
| Bug Blocks: | 1299184 | |||
|
Description
SATHEESARAN
2015-07-15 09:32:31 UTC
A customer has encountered this problem: $ cat etc/redhat-storage-release Red Hat Gluster Storage Server 3.1 Update 1 $ cat etc/redhat-release Red Hat Enterprise Linux Server release 7.1 (Maipo) [2015-11-12 09:51:52.086507] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/rpc-transport/socket.so: cannot open shared object file: No such file or directory [2015-11-12 09:51:52.112196] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/configuration.so: cannot open shared object file: No such file or directory [2015-11-13 08:48:32.185511] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/rpc-transport/socket.so: cannot open shared object file: No such file or directory [2015-11-13 08:48:32.209946] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/configuration.so: cannot open shared object file: No such file or directory [2015-11-13 08:48:32.185538] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/rpc-transport/socket.so: cannot open shared object file: No such file or directory [2015-11-13 08:48:32.209967] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/configuration.so: cannot open shared object file: No such file or directory [2015-11-13 14:45:48.944605] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/rpc-transport/socket.so: cannot open shared object file: No such file or directory [2015-11-13 14:45:48.970937] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/configuration.so: cannot open shared object file: No such file or directory [2015-11-13 14:45:48.944635] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/rpc-transport/socket.so: cannot open shared object file: No such file or directory [2015-11-13 14:45:48.970961] W [MSGID: 101095] [xlator.c:143:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.1/xlator/configuration.so: cannot open shared object file: No such file or directory First of all this doesn't have any functionality impact, so we can lower down the severity. RCA goes like this: socket.so doesn't follow the default xlator directory which is defined as XLATORDIR in libglusterfs/src/Makefile.am and hence in xlator_volopt_dynload it fails to load the object as the file resides in a different location. configure.so is absolutely invalid as we don't have any voltype as configure. config.memory-accounting & config.transport are the two options where we misplaced the voltype as configure where it should be mgmt/glusterd. I've sent an upstream fix http://review.gluster.org/12656 to address it. The fix is now available in rhgs-3.1.3 branch, hence moving the state to Modified. With below verification steps, Warning messages reported in the issue are not seen with the build "glusterfs-3.7.9-1" 1. Installed 3.1.2 RHGS ISO 2. Updated to 3.1.3 ( glusterfs-3.7.9-1 ) 3. Rebooted the node 4. Checked glusterd log for the warning messages reported. Moving to verified state. Looks good 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-2016:1239 |