On Thu, Oct 27, 2016 at 2:47 PM, Josep Manel Andrés <josep.andres@xxxxxx> wrote:
Hi all,
I had set up a 2 nodes cluster over 2 SLES 12 SP0 and 3.8.0 at first... then I moved one node to SLES 12 SP1 and therefor upgraded to 3.8.4 this node, and I ran into this bug ( I think)
https://bugzilla.redhat.com/show_bug.cgi?id=1350326
No, this is a different bug.
That is why I upgraded to 3.8.5 this box, so the final setup is one server SLES 12 SP0 3.8.0 and the other SLES 12 SP1 3.8.5.
But when trying to start the server on SLES12SP1 I can see in the logs:
[2016-10-27 09:16:48.211143] I [MSGID: 100030] [glusterfsd.c:2454:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.8.5 (args: /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO)
[2016-10-27 09:16:48.212535] W [MSGID: 101095] [xlator.c:198:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/3.8.0/xlator/mgmt/glusterd.so: cannot open shared object file: No such file or directory
It's unable to load glusterd.so because its still trying to refer to 3.8.0 path instead of 3.8.5. I remember seeing a similar email thread few months back but unable to recollect the workaround. Let me try to dig in the archive and fetch that for you.
[2016-10-27 09:16:48.212614] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume 'management', line 2: type 'mgmt/glusterd' is not valid or not found on this machine
[2016-10-27 09:16:48.212680] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume management
[2016-10-27 09:16:48.212747] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2016-10-27 09:16:48.213042] E [graph.c:979:glusterfs_graph_destroy] (-->/usr/sbin/glusterd(gluster fs_volumes_init+0xc2) [0x4098e2] -->/usr/sbin/glusterd(glusterf s_process_volfp+0x111) [0x4097a1] -->/usr/lib64/libglusterfs.so. 0(glusterfs_graph_destroy+0x84 ) [0x7f850ddf45e4] ) 0-graph: invalid argument: graph [Invalid argument]
[2016-10-27 09:16:48.213111] W [glusterfsd.c:1327:cleanup_and_exit] (-->/usr/sbin/glusterd(gluster fs_volumes_init+0xc2) [0x4098e2] -->/usr/sbin/glusterd(glusterf s_process_volfp+0x13a) [0x4097ca] -->/usr/sbin/glusterd(cleanup_ and_exit+0x5f) [0x408e5f] ) 0-: received signum (1), shutting down
Does anyone has an idea of what is going on?
Cheers.
--
Josep Manel Andrés (josep.andres@xxxxxx)
Operations - Barcelona Supercomputing Center
C/ Jordi Girona, 31 http://www.bsc.es
08034 Barcelona, Spain Tel: +34-93-401 25 73
e-mail: systems@xxxxxx Fax: +34-93-413 77 21
-----------------------------------------------
WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.
http://www.bsc.es/disclaimer
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
--
~ Atin (atinm)
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
