search for: 4f43

I need to delete the DNS record and I could not have any idea something that is going bad root at zdtoe-02:~# dig axfr dtoe.etecsa.cu |grep zdtoe-01 *_msdcs\010CNF:946b89d3-b07b-4f43-a6b9-0de3bf3f3a10.dtoe.etecsa.cu. 900 IN NS zdtoe-01.dtoe.etecsa.cu.* *_msdcs\010CNF:4b642bd5-765f-4b16-93ce-3921b46ce220.dtoe.etecsa.cu. 900 IN NS zdtoe-01.dtoe.etecsa.cu. *root at zdtoe-02:~#*samba-tool dns delete 192.168.157.84 dtoe.etecsa.cu _msdcs\010CNF:946b89d3-b07b-4f43-a6b9-0de3bf3f3a1...

I could delete all records of this server that no longer exists no problem even record type NS I only have these two that there has been no way to erase any other ideas thanks samba-tool dns delete zdtoe-02.dtoe.etecsa.cu dtoe.etecsa.cu _msdcs\010CNF:946b89d3-b07b-4f43-a6b9-0de3bf3f3a10.dtoe.etecsa.cu. NS zdtoe-01.dtoe.etecsa.cu -U administrator GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego' registered GENSEC backend 'schann...

Hi, As the error message said "Cannot do GSSAPI to an IP address" perhaps you should try to replace DC IP address by its FQDN: samba-tool dns delete <DC_FQDN> dtoe.etecsa.cu _msdcs\010CNF: 946b89d3-b07b-4f43-a6b9-0de3bf3f3a10.dtoe.etecsa.cu NS * zdtoe-01.dtoe.etecsa.cu -U administrator Cheers, mathias 2015-11-12 20:20 GMT+01:00 Karel González Herrera <karel.gonzalez at etecsa.cu> : > I need to delete the DNS record and I could not have any idea something > that is going bad > > ro...

...le:CoGetClassObject CLSCTX_REMOTE_SERVER not supported err:ole:CoGetClassObject no class object {babf35c3-8706-4256-a0be-f72164bdf27c} could be created for context 0x15 fixme:actctx:FindActCtxSectionStringW 00000000 (null) 2 L"msvcr80.dll" 0x336b04 err:ole:CoGetClassObject class {12421eb7-4f43-a0d4-830a-f8d0eea8e231} not registered err:ole:create_server class {12421eb7-4f43-a0d4-830a-f8d0eea8e231} not registered fixme:ole:CoGetClassObject CLSCTX_REMOTE_SERVER not supported err:ole:CoGetClassObject no class object {12421eb7-4f43-a0d4-830a-f8d0eea8e231} could be created for context 0x15...

...afr_log_selfheal] 2-gv_cdn_001-replicate-1: Completed metadata selfheal on 97ad48bc-8873-4700-9f82-4 7130cd031a1. sources=[0] sinks= [2017-07-23 20:38:04.837770] I [MSGID: 108026] [afr-self-heal- common.c:1077:afr_log_selfheal] 2-gv_cdn_001-replicate-1: Completed metadata selfheal on 041e58e2-9afe-4f43-ba0b-d 11e80b5053b. sources=[0] sinks= In order to "fix" the situation I had to kill off the new brick process so now I'm in a situation with a distribute replica volume with one of the replica sets in a degraded state. Is there any way I can re-add the old brick back to get back t...

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...eal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on ea69e2f6-ab47-4e96-8863-52e21b31d893. sources=0 [2] sinks=1 [2017-10-25 10:40:11.770035] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 94a051ce-e0b1-4f43-93e8-c962d380007a. sources=0 [2] sinks=1 [2017-10-25 10:40:11.779213] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on a0d7c1c0-f7f8-4cc7-8db2-7cfeb551d8a2. sources=0 [2] sinks=1 [2017-10-25 10:40:11.787770] I [MSGID: 108026] [afr-s...