search for: a9df

Hello all, I'm running Samba 3.5.5 on Debian 5, and following the documentation as closely as I can to install drivers using rpcclient. I first install the driver on a Windows 7 x65 workstation, then use rpcclient/smbclient to fetch the files. I then use smbclient to put those on the print$ share of the Samba server. So far, so good. Then I use rpcclient to add those files, and that

...management: handler returned: -1 The thing that is really strange is that in this case the uuid of node3 is d9047ecd-26b5-467b-8e91-50f76a0c4d16! The mapping nodename-uuid is: * (node1) virtnode-0-0-gluster: 2c6f154f-efe3-4479-addc-b2021aa9d5df * (node2) virtnode-0-1-gluster: e93ebee7-5d95-4100-a9df-4a3e60134b73 * (node3) virtnode-0-2-gluster: d9047ecd-26b5-467b-8e91-50f76a0c4d16 In this case restarting glusterd on node3 usually solve the issue. What could be the root cause of this behavior? How can I fix this once and for all? If needed I could provide the full log file. Greetings,...

...is really strange is that in this case the uuid of > node3 is d9047ecd-26b5-467b-8e91-50f76a0c4d16! > > The mapping nodename-uuid is: > > * (node1) virtnode-0-0-gluster: 2c6f154f-efe3-4479-addc-b2021aa9d5df > > * (node2) virtnode-0-1-gluster: e93ebee7-5d95-4100-a9df-4a3e60134b73 > > * (node3) virtnode-0-2-gluster: d9047ecd-26b5-467b-8e91-50f76a0c4d16 > > In this case restarting glusterd on node3 usually solve the issue. > > What could be the root cause of this behavior? How can I fix this > once and for all? > > I...

...brick1b-iso-images-repo.pid > -S /var/run/gluster/c779852c21e2a91eaabbdda3b9127262.socket > --brick-name /data/glusterfs/brick1b/iso-images-repo -l > /var/log/glusterfs/bricks/data-glusterfs-brick1b-iso-images-repo.log > --xlator-option > *-posix.glusterd-uuid=e93ebee7-5d95-4100-a9df-4a3e60134b73 > --brick-port 49163 --xlator-option > iso-images-repo-server.listen-port=49163) > > I've checked after the restart and indeed now the directory > 'entry-changes' is created, but why stopping the glusterd service has > not stopped also the brick proces...

...d9047ecd-26b5-467b-8e91-50f76a0c4d16! >> >> The mapping nodename-uuid is: >> >> * (node1) virtnode-0-0-gluster: >> 2c6f154f-efe3-4479-addc-b2021aa9d5df >> >> * (node2) virtnode-0-1-gluster: >> e93ebee7-5d95-4100-a9df-4a3e60134b73 >> >> * (node3) virtnode-0-2-gluster: >> d9047ecd-26b5-467b-8e91-50f76a0c4d16 >> >> In this case restarting glusterd on node3 usually solve the >> issue. >> >> What could be the root cause of this b...

...; The thing that is really strange is that in this case the uuid of node3 is > d9047ecd-26b5-467b-8e91-50f76a0c4d16! > > The mapping nodename-uuid is: > > * (node1) virtnode-0-0-gluster: 2c6f154f-efe3-4479-addc-b2021aa9d5df > > * (node2) virtnode-0-1-gluster: e93ebee7-5d95-4100-a9df-4a3e60134b73 > > * (node3) virtnode-0-2-gluster: d9047ecd-26b5-467b-8e91-50f76a0c4d16 > > In this case restarting glusterd on node3 usually solve the issue. > > What could be the root cause of this behavior? How can I fix this once > and for all? > > If needed I could pro...

...registered. Where do you geht the filenames, the drivers needs? as i cant use rpcclient to register the drivers from commandline. best regards thomas # Thomas Stegbauer # https://keyserver1.pgp.com/vkd/SubmitSearch.event?SearchCriteria=3Dthomas= @steg bauer.info # PGP Fingerprint: C5B5 BDBD 6607 A9DF E545 0EC5 9DDF 9749 BD05 808A Am 10.02.2011 15:37, schrieb Laurent Blume: > Hello all, > > I'm running Samba 3.5.5 on Debian 5, and following the documentation=20 > as closely as I can to install drivers using rpcclient. > > I first install the driver on a Windows 7 x65 wor...

...de-0-1-gluster-data-glusterfs-brick1b-iso-images-repo.pid -S /var/run/gluster/c779852c21e2a91eaabbdda3b9127262.socket --brick-name /data/glusterfs/brick1b/iso-images-repo -l /var/log/glusterfs/bricks/data-glusterfs-brick1b-iso-images-repo.log --xlator-option *-posix.glusterd-uuid=e93ebee7-5d95-4100-a9df-4a3e60134b73 --brick-port 49163 --xlator-option iso-images-repo-server.listen-port=49163) I've checked after the restart and indeed now the directory 'entry-changes' is created, but why stopping the glusterd service has not stopped also the brick processes? Now how can I recover from...

...trange is that in this case the uuid of node3 >> is d9047ecd-26b5-467b-8e91-50f76a0c4d16! >> >> The mapping nodename-uuid is: >> >> * (node1) virtnode-0-0-gluster: 2c6f154f-efe3-4479-addc-b2021aa9d5df >> >> * (node2) virtnode-0-1-gluster: e93ebee7-5d95-4100-a9df-4a3e60134b73 >> >> * (node3) virtnode-0-2-gluster: d9047ecd-26b5-467b-8e91-50f76a0c4d16 >> >> In this case restarting glusterd on node3 usually solve the issue. >> >> What could be the root cause of this behavior? How can I fix this once >> and for all? &gt...

...eht the filenames, the drivers needs?=20 as i cant use rpcclient to register the drivers from commandline.=20 best regards=20 thomas=20 # Thomas Stegbauer=20 #=20 https://keyserver1.pgp.com/vkd/SubmitSearch.event?SearchCriteria=3Dthomas at s= teg=20 bauer.info=20 # PGP Fingerprint: C5B5 BDBD 6607 A9DF E545 0EC5 9DDF 9749 BD05 808A=20 Am 10.02.2011 15:37, schrieb Laurent Blume:=20 > Hello all,=20 >=20 > I'm running Samba 3.5.5 on Debian 5, and following the documentation=20 > as closely as I can to install drivers using rpcclient.=20 >=20 > I first install the driver on a...

...; -S /var/run/gluster/c779852c21e2a91eaabbdda3b9127262.socket >> --brick-name /data/glusterfs/brick1b/iso-images-repo -l >> /var/log/glusterfs/bricks/data-glusterfs-brick1b-iso-images-repo.log >> --xlator-option >> *-posix.glusterd-uuid=e93ebee7-5d95-4100-a9df-4a3e60134b73 >> --brick-port 49163 --xlator-option >> iso-images-repo-server.listen-port=49163) >> >> I've checked after the restart and indeed now the directory >> 'entry-changes' is created, but why stopping the glusterd service >>...

...usterfs-brick1b-iso-images-repo.pid -S /var/run/gluster/ > c779852c21e2a91eaabbdda3b9127262.socket --brick-name > /data/glusterfs/brick1b/iso-images-repo -l /var/log/glusterfs/bricks/ > data-glusterfs-brick1b-iso-images-repo.log --xlator-option > *-posix.glusterd-uuid=e93ebee7-5d95-4100-a9df-4a3e60134b73 --brick-port > 49163 --xlator-option iso-images-repo-server.listen-port=49163) > > I've checked after the restart and indeed now the directory > 'entry-changes' is created, but why stopping the glusterd service has not > stopped also the brick processes? >...

...the uuid of node3 >>> is d9047ecd-26b5-467b-8e91-50f76a0c4d16! >>> >>> The mapping nodename-uuid is: >>> >>> * (node1) virtnode-0-0-gluster: 2c6f154f-efe3-4479-addc-b2021aa9d5df >>> >>> * (node2) virtnode-0-1-gluster: e93ebee7-5d95-4100-a9df-4a3e60134b73 >>> >>> * (node3) virtnode-0-2-gluster: d9047ecd-26b5-467b-8e91-50f76a0c4d16 >>> >>> In this case restarting glusterd on node3 usually solve the issue. >>> >>> What could be the root cause of this behavior? How can I fix this once &...

...4d16! >>> >>> The mapping nodename-uuid is: >>> >>> * (node1) virtnode-0-0-gluster: >>> 2c6f154f-efe3-4479-addc-b2021aa9d5df >>> >>> * (node2) virtnode-0-1-gluster: >>> e93ebee7-5d95-4100-a9df-4a3e60134b73 >>> >>> * (node3) virtnode-0-2-gluster: >>> d9047ecd-26b5-467b-8e91-50f76a0c4d16 >>> >>> In this case restarting glusterd on node3 usually solve the >>> issue. >>> >>> What c...

...-iso-images-repo.pid -S >> /var/run/gluster/c779852c21e2a91eaabbdda3b9127262.socket --brick-name >> /data/glusterfs/brick1b/iso-images-repo -l /var/log/glusterfs/bricks/data >> -glusterfs-brick1b-iso-images-repo.log --xlator-option >> *-posix.glusterd-uuid=e93ebee7-5d95-4100-a9df-4a3e60134b73 --brick-port >> 49163 --xlator-option iso-images-repo-server.listen-port=49163) >> >> I've checked after the restart and indeed now the directory >> 'entry-changes' is created, but why stopping the glusterd service has not >> stopped also the b...

...2c21e2a91eaabbdda3b9127262.socket >>> --brick-name /data/glusterfs/brick1b/iso-images-repo -l >>> /var/log/glusterfs/bricks/data-glusterfs-brick1b-iso-images-repo.log >>> --xlator-option >>> *-posix.glusterd-uuid=e93ebee7-5d95-4100-a9df-4a3e60134b73 >>> --brick-port 49163 --xlator-option >>> iso-images-repo-server.listen-port=49163) >>> >>> I've checked after the restart and indeed now the directory >>> 'entry-changes' is created, but why stop...

On Wed, Jun 28, 2017 at 9:45 PM, Ravishankar N <ravishankar at redhat.com> wrote: > On 06/28/2017 06:52 PM, Paolo Margara wrote: > >> Hi list, >> >> yesterday I noted the following lines into the glustershd.log log file: >> >> [2017-06-28 11:53:05.000890] W [MSGID: 108034] >> [afr-self-heald.c:479:afr_shd_index_sweep] >>

...The mapping nodename-uuid is: >>>> >>>> * (node1) virtnode-0-0-gluster: >>>> 2c6f154f-efe3-4479-addc-b2021aa9d5df >>>> >>>> * (node2) virtnode-0-1-gluster: >>>> e93ebee7-5d95-4100-a9df-4a3e60134b73 >>>> >>>> * (node3) virtnode-0-2-gluster: >>>> d9047ecd-26b5-467b-8e91-50f76a0c4d16 >>>> >>>> In this case restarting glusterd on node3 usually solve >>>> the issue....

...te: Mon, 27 Feb 2006 17:21:30 +0100 > From: David Z?lke <dz-c16oUwy5/3O+XT7JhA+gdA@public.gmane.org> > Subject: Re: [Rails-spinoffs] Disabling anchor clicking in a draggable > To: rails-spinoffs-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > Message-ID: <87C5C86C-CE67-431A-A9DF-33E57355A79D-c16oUwy5/3O+XT7JhA+gdA@public.gmane.org> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Assign an event handler to the links that stops event propagation > (a.k.a "bubbling"). > > - David > > > > Am 27.02.2006 um 12...