search for: 93ce

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-0de3bf3f3a10.dtoe.etecsa.cu NS *zdtoe-01.dtoe.etecsa.cu -U administrator GENSEC backend 'gssapi_spnego' register...

...ld 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-0de3bf3f3a10.dtoe.etecsa.cu NS * >> zdtoe-01.dtoe.etecsa.cu -U administrator >&...

...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-0de3bf3f3a10.dtoe.etecsa.cu NS * > zdtoe-01.dtoe.etecsa.cu -U administrator > GENSEC backend '...

..."SIP/ed-1-fc54", "CALLERID(name)=Support") in new stack -- Executing Queue("SIP/ed-1-fc54", "support|t|||180") in new stack When I hang up the dialling phone there is no cli ouput and "show channels" shows the channel as still there: SIP/ed-1-93ce (macro-queueinbound s 4 ) Up Queue support|t|||180 Calling an agent produces the same result, and "show agents" on the CLI produces no output. We're using dynamic agents with agentcallbacklogin. Other calls seem to proceed OK, although it does seem to be rather...

...quot; (n0,r2) /local/domain/2/device-misc/console/nextDeviceID = "1" (n0,r2) /local/pool = "" (n0) /local/pool/0 = "" (n0) /local/pool/0/other_config = "" (n0) /local/pool/0/description = "Pool-0" (n0) /local/pool/0/uuid = "48211ce4-93ce-8c87-505e-5d2830cf1d13" (n0) /local/pool/0/name = "Pool-0" (n0) /vm = "" (n0) /vm/00000000-0000-0000-0000-000000000000 = "" (n0) /vm/00000000-0000-0000-0000-000000000000/on_xend_stop = "ignore" (n0) /vm/00000000-0000-0000-0000-000000000000/pool...

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

...n.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on 84a445f7-0455-4f35-84be-07d51470ebd2. sources=0 [2] sinks=1 [2017-10-25 10:40:28.965782] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on fb36d5fa-8d8d-4556-93ce-737afbdd7f26. sources=0 [2] sinks=1 [2017-10-25 10:40:29.114691] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 164a0023-d6e3-4128-b2cb-81c2c92e3e0e. sources=0 [2] sinks=1 [2017-10-25 10:40:29.123705] I [MSGID: 108026] [afr-self-h...