search for: s30samba

...(-->/usr/lib64/glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdb46a) [0x7f30460bc46a] -->/usr/lib64/glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdaf2d) [0x7f30460bbf2d] -->/lib64/libglusterfs.so.0(runner_log+0x115) [0x7f3051532255] ) 0-management: Ran script: /var/lib/glusterd/hooks/1/set/post/S30samba-set.sh --volname=intermediate01 -o features.trash=on --gd-workdir=/var/lib/glusterd [2017-06-16 16:08:14.453290] I [run.c:191:runner_log] (-->/usr/lib64/glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdb46a) [0x7f30460bc46a] -->/usr/lib64/glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdaf2d) [0x7f3...

.../glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdb46a) [0x7f30460bc46a] -- > >/usr/lib64/glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdaf2d) [0x7f30460bbf2d] -- > >/lib64/libglusterfs.so.0(runner_log+0x115) [0x7f3051532255] ) 0-management: Ran script: > /var/lib/glusterd/hooks/1/set/post/S30samba-set.sh --volname=intermediate01 -o features.trash=on > --gd-workdir=/var/lib/glusterd > [2017-06-16 16:08:14.453290] I [run.c:191:runner_log] ( > -->/usr/lib64/glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdb46a) [0x7f30460bc46a] -- > >/usr/lib64/glusterfs/3.10.1/xlator/mgmt/gluster...

...->/usr/lib64/glusterfs/3.12.1/xlator/mgmt/glusterd.so(+0xde17a) [0x7fc23442117a] -->/usr/lib64/glusterfs/3.12.1/xlator/mgmt/glusterd.so(+0xddc3d) [0x7fc234420c3d] -->/lib64/libglusterfs.so.0(runner_log+0x115) [0x7fc23f915da5] ) 0-management: Ran script: /var/lib /glusterd/hooks/1/set/post/S30samba-set.sh --volname=gv0 -o cluster.halo-enabled=yes --gd-workdir=/var/lib/glusterd [2017-11-07 22:20:15.255777] I [run.c:190:runner_log] (-->/usr/lib64/glusterfs/3.12.1/xlator/mgmt/glusterd.so(+0xde17a) [0x7fc23442117a] -->/usr/lib64/glusterfs/3.12.1/xlator/mgmt/glusterd.so(+0xddc3d) [0x7fc2344...

...s/3.12.1/xlator/mgmt/glusterd.so(+0xde17a) > [0x7fc23442117a] > -->/usr/lib64/glusterfs/3.12.1/xlator/mgmt/glusterd.so(+0xddc3d) > [0x7fc234420c3d] -->/lib64/libglusterfs.so.0(runner_log+0x115) > [0x7fc23f915da5] ) 0-management: Ran script: /var/lib > /glusterd/hooks/1/set/post/S30samba-set.sh --volname=gv0 -o > cluster.halo-enabled=yes --gd-workdir=/var/lib/glusterd > [2017-11-07 22:20:15.255777] I [run.c:190:runner_log] > (-->/usr/lib64/glusterfs/3.12.1/xlator/mgmt/glusterd.so(+0xde17a) > [0x7fc23442117a] > -->/usr/lib64/glusterfs/3.12.1/xlator/mgmt/glusterd...

...gluster volume set gv1 client.ssl on gluster volume set gv1 server.ssl on When mounting the volume on the peers, I get the following messages: ------------------- _64-linux-gnu/libglusterfs.so.0(runner_log+0x100) [0x7ffa11782640] ) 0-management: Ran script: /var/lib/glusterd/hooks/1/start/post/S30samba-start.sh --volname=gv1 --first=yes --version=1 --volume-op=start --gd-workdir=/var/lib/glusterd 0-socket.management: SSL support for MGMT is ENABLED IO path is ENABLED certificate depth is 1 for peer 192.168.57.42:49147 0-socket.management: SSL support for MGMT is ENABLED IO path is ENABLED ce...

...er volume set gv1 client.ssl on gluster volume set gv1 server.ssl on When mounting the volume on the peers, I get the following messages: ------------------- _64-linux-gnu/libglusterfs.so.0(runner_log+0x100) [0x7ffa11782640] ) 0-management: Ran script: /var/lib/glusterd/hooks/1/start/post/S30samba-start.sh --volname=gv1 --first=yes --version=1 --volume-op=start --gd-workdir=/var/lib/glusterd 0-socket.management: SSL support for MGMT is ENABLED IO path is ENABLED certificate depth is 1 for peer 192.168.57.42:49147 0-socket.management: SSL support for MGMT is ENABLED IO path is ENABLED...

...4/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0xdbd7a) [0x7fbb107e5d7a] -->/usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0xdb79b) [0x7fbb107e579b] -->/lib64/libglusterfs.so.0(runner_log+0x115) [0x7fbb1bc5c385] ) 0-management: Failed to execute script: /var/lib/glusterd/hooks/1/start/post/S30samba-start.sh --volname=gv0 --first=yes --version=1 --volume-op=start --gd-workdir=/var/lib/glusterd Looks like this was related to Samba that I do not use. The same E error happens even I use transport=tcp. No error in brick logs. Below is what was written to data-brick1-gv0.log: [2017-08-16 10:59...

On Tue, Aug 15, 2017 at 01:04:11PM +0000, Hatazaki, Takao wrote: > Ji-Hyeon, > > You're saying that "stripe=2 transport=rdma" should work. Ok, that > was firstly I wanted to know. I'll put together logs later this week. Note that "stripe" is not tested much and practically unmaintained. We do not advise you to use it. If you have large files that you

...4/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0xdbd7a) [0x7fbb107e5d7a] -->/usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0xdb79b) [0x7fbb107e579b] -->/lib64/libglusterfs.so.0(runner_log+0x115) [0x7fbb1bc5c385] ) 0-management: Failed to execute script: /var/lib/glusterd/hooks/1/start/post/S30samba-start.sh --volname=gv0 --first=yes --version=1 --volume-op=start --gd-workdir=/var/lib/glusterd > > Looks like this was related to Samba that I do not use. The same E error happens even I use transport=tcp. No error in brick logs. Below is what was written to data-brick1-gv0.log: > >...

i usually change event threads to 4. But those logs are from a default installation. On Sun, Sep 3, 2017 at 9:52 PM, Ben Turner <bturner at redhat.com> wrote: > ----- Original Message ----- >> From: "Ben Turner" <bturner at redhat.com> >> To: "Serkan ?oban" <cobanserkan at gmail.com> >> Cc: "Gluster Users" <gluster-users at

----- Original Message ----- > From: "Ben Turner" <bturner at redhat.com> > To: "Serkan ?oban" <cobanserkan at gmail.com> > Cc: "Gluster Users" <gluster-users at gluster.org> > Sent: Sunday, September 3, 2017 2:30:31 PM > Subject: Re: [Gluster-users] Glusterd proccess hangs on reboot > > ----- Original Message ----- > >