search for: 106301

...erd-handler.c:1484:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req [2018-02-06 13:48:57.283814] E [MSGID: 106429] [glusterd-utils.c:1156:glusterd_brickinfo_new_from_brick] 0-management: Failed to convert hostname pri.ostechnix.lan to uuid [2018-02-06 13:48:57.283871] E [MSGID: 106301] [glusterd-syncop.c:1322:gd_stage_op_phase] 0-management: Staging of operation 'Volume Create' failed on localhost : Host pri.ostechnix.lan is not in 'Peer in Cluster' state [2018-02-06 13:49:33.997818] E [MSGID: 106429] [glusterd-utils.c:1156:glusterd_brickinfo_new_from_brick] 0-ma...

...terd_handle_cli_list_friends] 0-glusterd: > Received cli list req > [2018-02-06 13:48:57.283814] E [MSGID: 106429] > [glusterd-utils.c:1156:glusterd_brickinfo_new_from_brick] 0-management: > Failed to convert hostname pri.ostechnix.lan to uuid > [2018-02-06 13:48:57.283871] E [MSGID: 106301] > [glusterd-syncop.c:1322:gd_stage_op_phase] 0-management: Staging of > operation 'Volume Create' failed on localhost : Host pri.ostechnix.lan is > not in 'Peer in Cluster' state > [2018-02-06 13:49:33.997818] E [MSGID: 106429] > [glusterd-utils.c:1156:glusterd_brick...

...glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req > [2018-02-06 13:48:57.283814] E [MSGID: 106429] [glusterd-utils.c:1156: > glusterd_brickinfo_new_from_brick] 0-management: Failed to convert > hostname pri.ostechnix.lan to uuid > [2018-02-06 13:48:57.283871] E [MSGID: 106301] [glusterd-syncop.c:1322:gd_stage_op_phase] > 0-management: Staging of operation 'Volume Create' failed on localhost : > Host pri.ostechnix.lan is not in 'Peer in Cluster' state > [2018-02-06 13:49:33.997818] E [MSGID: 106429] [glusterd-utils.c:1156: > glusterd_brickinfo...

...r.c:1484:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req > [2018-02-06 13:48:57.283814] E [MSGID: 106429] [glusterd-utils.c:1156:glusterd_brickinfo_new_from_brick] 0-management: Failed to convert hostname pri.ostechnix.lan to uuid > [2018-02-06 13:48:57.283871] E [MSGID: 106301] [glusterd-syncop.c:1322:gd_stage_op_phase] 0-management: Staging of operation 'Volume Create' failed on localhost : Host pri.ostechnix.lan is not in 'Peer in Cluster' state > [2018-02-06 13:49:33.997818] E [MSGID: 106429] [glusterd-utils.c:1156:glusterd_brickinfo_new_from_brick]...

...y is installed (2.6.9-2etch1). I ran strace on both side and attach the last lines of both strace ouputs to this message. Best regards, Mario Domg?rgen -------------- next part -------------- open("var/log/auth.log", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|0640, st_size=106301, ...}) = 0 read(3, "Oct 7 06:25:04 newsletter CRON["..., 106301) = 106301 close(3) = 0 open("var/log/daemon.log", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|0640, st_size=265082, ...}) = 0 mmap2(NULL, 266240, PROT_READ|PROT_WRITE, MAP_P...

On 2017-08-24 13:00, Rowland Penny via samba wrote: > On Thu, 24 Aug 2017 12:41:36 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> On 2017-08-24 12:27, Rowland Penny via samba wrote: >>> On Thu, 24 Aug 2017 12:03:42 +0200 >>> Sven Schwedas via samba <samba at lists.samba.org> wrote: >>> >>>> >>>>

Hai, To recover from that problem, read : The "Why" i setup like this. http://lists-archives.com/samba/106301-can-t-create-update-group-policy-in-samba-4-6-5.html And howto fix. http://lists-archives.com/samba/106333-can-t-create-update-group-policy-in-samba-4-6-5.html Note on this last link, the part.: A good tip to restore the defaults with samba-tool without errors. move you domain folder out of t...

...] I [glusterd-locks.c:729:gd_mgmt_v3_unlock_timer_cbk] 0-management: In gd_mgmt_v3_unlock_timer_cbk [2017-12-15 18:06:34.304868] I [MSGID: 106499] [glusterd-handler.c:4303:__glusterd_handle_status_volume] 0-management: Received status volume req for volume gv0 [2017-12-15 18:06:34.306603] E [MSGID: 106301] [glusterd-syncop.c:1353:gd_stage_op_phase] 0-management: Staging of operation 'Volume Status' failed on localhost : Volume gv0 is not started [2017-12-15 18:11:39.412700] I [glusterd-utils.c:5926:glusterd_brick_start] 0-management: starting a fresh brick process for brick /exp/b2/gv0 [2017...

...Onderwerp: Re: [Samba] sysvolreset doesn't reset all ACLs > > On 2017-08-24 15:13, L.P.H. van Belle via samba wrote: > > Hai, > > > > To recover from that problem, read : > > The "Why" i setup like this. > > > http://lists-archives.com/samba/106301-can-t-create-update-group-polic > > y-in-samba-4-6-5.html > > > > And howto fix. > > > http://lists-archives.com/samba/106333-can-t-create-update-group-polic > > y-in-samba-4-6-5.html > > Note on this last link, the part.: > > Okay, I set up `acl_xat...

...gmt_v3_unlock_timer_cbk] > 0-management: In gd_mgmt_v3_unlock_timer_cbk > > [2017-12-15 18:06:34.304868] I [MSGID: 106499] [glusterd-handler.c:4303:__glusterd_handle_status_volume] > 0-management: Received status volume req for volume gv0 > > [2017-12-15 18:06:34.306603] E [MSGID: 106301] [glusterd-syncop.c:1353:gd_stage_op_phase] > 0-management: Staging of operation 'Volume Status' failed on localhost : > Volume gv0 is not started > > [2017-12-15 18:11:39.412700] I [glusterd-utils.c:5926:glusterd_brick_start] > 0-management: starting a fresh brick process fo...

I managed to force stopping geo replication using the "force" parameter after the "stop" but there are still other issues related to the fact that my geo replication setup was created before I added the additional arbiter node to my replca. For example when I would like to stop my volume I simply can't and I get the following error: volume stop: myvolume: failed: Staging

...;> > >> On 2017-08-24 15:13, L.P.H. van Belle via samba wrote: > >>> Hai, > >>> > >>> To recover from that problem, read : > >>> The "Why" i setup like this. > >>> > >> > http://lists-archives.com/samba/106301-can-t-create-update-group-poli > >> c > >>> y-in-samba-4-6-5.html > >>> > >>> And howto fix. > >>> > >> > http://lists-archives.com/samba/106333-can-t-create-update-group-poli > >> c > >>> y-in-samba-4-6-5.ht...

...n 2017-08-24 15:13, L.P.H. van Belle via samba wrote: >>>>> Hai, >>>>> >>>>> To recover from that problem, read : >>>>> The "Why" i setup like this. >>>>> >>>> >> http://lists-archives.com/samba/106301-can-t-create-update-group-poli >>>> c >>>>> y-in-samba-4-6-5.html >>>>> >>>>> And howto fix. >>>>> >>>> >> http://lists-archives.com/samba/106333-can-t-create-update-group-poli >>>> c >>>&...

...ch: 106049-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106271-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105755-06 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106033-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106301-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105490-04 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWarc, SUNWbtool, SUNWhea, SUNWtoo, SUNWosdem, SUNWxcu4 Patch: 106226-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105568-11 Obsole...

On 8/02/2018 4:45 AM, Gaurav Yadav wrote: > After seeing command history, I could see that you have 3 nodes, and > firstly you are peer probing 51.15.90.60? and 163.172.151.120 from? > 51.15.77.14 > So here itself you have 3 node cluster, after all this you are going > on node 2 and again peer probing 51.15.77.14. > ?Ideally it should work, with above steps, but due to some