[Bugs] [Bug 1532238] New: Failed to access volume via Samba with undefined symbol from socket.so

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1532238

            Bug ID: 1532238
           Summary: Failed to access volume via Samba with undefined
                    symbol from socket.so
           Product: GlusterFS
           Version: mainline
         Component: build
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: anoopcs at redhat.com
                CC: bugs at gluster.org



Description of problem:
Following error was seen in gfapi log while trying to access a basic GlusterFS
volume via Samba.

[2018-01-08 09:21:20.026546] E [rpc-transport.c:284:rpc_transport_load]
0-rpc-transport: /usr/local/lib/glusterfs/4.0dev1/rpc-transport/socket.so:
undefined symbol: rpc_transport_notify
[2018-01-08 09:21:20.026606] W [rpc-transport.c:288:rpc_transport_load]
0-rpc-transport: volume 'gfapi': transport-type 'socket' is not valid or not
found on this machine
[2018-01-08 09:21:20.026616] W [rpc-clnt.c:1065:rpc_clnt_connection_init]
0-gfapi: loading of new rpc-transport failed
[2018-01-08 09:21:20.026632] W [MSGID: 104026]
[glfs-mgmt.c:1005:glfs_mgmt_init] 0-gfapi: failed to create rpc clnt
[2018-01-08 09:21:20.030210] I [timer.c:88:gf_timer_call_cancel]
(-->/usr/local/lib/libglusterfs.so.0(gf_log_fini+0x42) [0x7f07f38d15db]
-->/usr/local/lib/libglusterfs.so.0(gf_log_disable_suppression_before_exit+0x52)
[0x7f07f38d1575] -->/usr/local/lib/libglusterfs.so.0(gf_timer_call_cancel+0xcd)
[0x7f07f38e197a] ) 0-timer: ctx cleanup started


Version-Release number of selected component (if applicable):
master

How reproducible:
Always

Steps to Reproduce:
1. Create a basic 2x2 volume 
2. Try accessing the volume via Samba using any of the following means:
    a) Kernel CIFS client
    b) smbclient utility
    c) Windows/Mac OS

Actual results:
# smbclient -U root%smb \\\\192.168.122.102\\gluster-vol
tree connect failed: NT_STATUS_UNSUCCESSFUL

Connection failed with error mentioned above in client logs.

Expected results:
# smbclient -U root%smb \\\\192.168.122.102\\gluster-vol
Try "help" to get a list of possible commands.
smb: \>

Connection should be successful without any errors.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.