Bug 1243351 - Warning messages seen in glusterd logs when installed from RHGS 3.1 ISO based on RHEL 7.1
Summary: Warning messages seen in glusterd logs when installed from RHGS 3.1 ISO based...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHGS 3.1.3
Assignee: Atin Mukherjee
QA Contact: Byreddy
URL:
Whiteboard: glusterd
Depends On: 1283485 1283833 1283834
Blocks: 1299184
TreeView+ depends on / blocked
 
Reported: 2015-07-15 09:32 UTC by SATHEESARAN
Modified: 2019-09-12 08:38 UTC (History)
6 users (show)

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.
Clone Of:
: 1283485 (view as bug list)
Environment:
RHEL7
Last Closed: 2016-06-23 05:26:44 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1239 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 Update 3 2016-06-23 08:51:44 UTC

Description SATHEESARAN 2015-07-15 09:32:31 UTC
Description of problem:
-----------------------
When installed RHGS 3.1 ISO based on RHEL 7.1, warning messages about missing socket.so and configuration.so are reported in glusterd logs, as these .so files are looked up in the wrong location.

However there is no functional impact

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHGS 3.1 ISO ( based on RHEL 7.1 ) - [ http://download.eng.bos.redhat.com/composes/nightly/RHGSS-3.1-RHEL-7-20150714.n.1/compose/RHGSS/x86_64/iso/RHGSS-3.1-RHEL-7-20150714.n.1-RHGSS-x86_64-dvd1.iso ]

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Install RHGS 3.1 ISO which is based on RHEL 7.1
2. Post installation reboot the machine
3. Check for glusterd logs

Actual results:
---------------
Warning messages are seen in glusterd logs ( /var/log/glusterfs/etc-glusterfs-glusterd.vol.log as below :

<snip>
[2015-07-15 11:48:38.130329] 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-07-15 11:48:38.223781] 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-07-15 11:48:42.822541] I [MSGID: 106487] [glusterd-handler.c:1402:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
[2015-07-15 11:48:38.130383] 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-07-15 11:48:38.223849] 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
</snip>

Expected results:
-----------------
There should be any warning messages seen without justification

Additional info:
----------------
This problem is not seen when remove glusterfs packages and re-installed it again

Comment 1 Oonkwee Lim 2015-11-13 20:02:49 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

Comment 4 Atin Mukherjee 2015-11-19 06:45:07 UTC
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.

Comment 8 Atin Mukherjee 2016-03-22 12:13:13 UTC
The fix is now available in rhgs-3.1.3 branch, hence moving the state to Modified.

Comment 9 Byreddy 2016-04-04 11:29:12 UTC
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.

Comment 11 Atin Mukherjee 2016-06-02 11:59:31 UTC
Looks good

Comment 13 errata-xmlrpc 2016-06-23 05:26:44 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-2016:1239


Note You need to log in before you can comment on or make changes to this bug.