search for: 492d

...c, Line 1007 (ast_rtp_write): Ooh, format changed from U NKN to ULAW DEBUG[294927]: File channel.c, Line 947 (ast_settimeout): Scheduling timer at 16 0 sample intervals -- Playing 'vm-login' DEBUG[81926]: File chan_sip.c, Line 540 (__sip_ack): Stopping retransmission on '6E5D898E-492D-400B-A42B-8B25FE25F2EE@192.168.7.3' of Response 1: Found DEBUG[294927]: File channel.c, Line 947 (ast_settimeout): Scheduling timer at 0 sample intervals DEBUG[294927]: File channel.c, Line 947 (ast_settimeout): Scheduling timer at 0 sample intervals WARNING[294927]: File app_voicemail2.c, Li...

...dc.augusta.domain.tld. Lookup of dc.augusta.domain.tld. succeeded, but we failed to find a matching DNS entry for AAAA dc.augusta.domain.tld 2003:d1:bf0d:3100:215:5dff:feb2:1901 need update: AAAA dc.augusta.domain.tld 2003:d1:bf0d:3100:215:5dff:feb2:1901 Looking for DNS entry CNAME 00f33ed3-e50c-492d-a4bd-ab6cc2a2e54a._msdcs.augusta.domain.tld dc.augusta.domain.tld as 00f33ed3-e50c-492d-a4bd-ab6cc2a2e54a._msdcs.augusta.domain.tld. The DNS entry CNAME 00f33ed3-e50c-492d-a4bd-ab6cc2a2e54a._msdcs.augusta.domain.tld dc.augusta.domain.tld, queried as 00f33ed3-e50c-492d-a4bd-ab6cc2a2e54a._msdcs....

...r DNS entry SRV _ldap._tcp.dc._msdcs.tuebingen.tst.loc node1.tuebingen.tst.loc 389 as _ldap._tcp.dc._msdcs.tuebingen.tst.loc. Checking 0 100 389 node1.tuebingen.tst.loc. against SRV _ldap._tcp.dc._msdcs.tuebingen.tst.loc node1.tuebingen.tst.loc 389 Looking for DNS entry SRV _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst .loc node1.tuebingen.tst.loc 389 as _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst .loc. Checking 0 100 389 node1.tuebingen.tst.loc. against SRV _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst...

...r DNS entry SRV _ldap._tcp.dc._msdcs.tuebingen.tst.loc node1.tuebingen.tst.loc 389 as _ldap._tcp.dc._msdcs.tuebingen.tst.loc. Checking 0 100 389 node1.tuebingen.tst.loc. against SRV _ldap._tcp.dc._msdcs.tuebingen.tst.loc node1.tuebingen.tst.loc 389 Looking for DNS entry SRV _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst .loc node1.tuebingen.tst.loc 389 as _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst .loc. Checking 0 100 389 node1.tuebingen.tst.loc. against SRV _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst...

Am 04.01.2024 um 13:28 schrieb lists--- via samba: > Am 04.01.2024 um 12:36 schrieb Rowland Penny via samba: >> On Thu, 4 Jan 2024 12:12:57 +0100 >> lists--- via samba <samba at lists.samba.org> wrote: >> >>> Am 04.01.2024 um 11:55 schrieb Rowland Penny via samba: >>>> On Thu, 4 Jan 2024 11:19:17 +0100 >>>> lists--- via samba <samba at

...r DNS entry SRV _ldap._tcp.dc._msdcs.tuebingen.tst.loc node1.tuebingen.tst.loc 389 as _ldap._tcp.dc._msdcs.tuebingen.tst.loc. Checking 0 100 389 node1.tuebingen.tst.loc. against SRV _ldap._tcp.dc._msdcs.tuebingen.tst.loc node1.tuebingen.tst.loc 389 Looking for DNS entry SRV _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst .loc node1.tuebingen.tst.loc 389 as _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst .loc. Checking 0 100 389 node1.tuebingen.tst.loc. against SRV _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs.tuebingen.tst...

I was browsing the applications developed in zaptel and came across zttest. After I run it, I get the following: Opened pseudo zap interface, measuring accuracy... 99.975586% 99.987793% 99.987793% 99.987793% 99.987793% 100.000000% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.975586% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%

...268 node1 _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs IN SRV 0 100 3268 node1 ; ; ldap servers _ldap._tcp IN SRV 0 100 389 node1 _ldap._tcp.dc._msdcs IN SRV 0 100 389 node1 _ldap._tcp.pdc._msdcs IN SRV 0 100 389 node1 _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs IN SRV 0 100 389 node1 _ldap._tcp.Default-First-Site-Name._sites IN SRV 0 100 389 node1 _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs IN SRV 0 100 389 node1 ; ; krb5 servers _kerberos._tcp IN SRV 0 100 88 node1 _kerb...

...268 node1 _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs IN SRV 0 100 3268 node1 ; ; ldap servers _ldap._tcp IN SRV 0 100 389 node1 _ldap._tcp.dc._msdcs IN SRV 0 100 389 node1 _ldap._tcp.pdc._msdcs IN SRV 0 100 389 node1 _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs IN SRV 0 100 389 node1 _ldap._tcp.Default-First-Site-Name._sites IN SRV 0 100 389 node1 _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs IN SRV 0 100 389 node1 ; ; krb5 servers _kerberos._tcp IN SRV 0 100 88 node1 _kerb...

...268 node1 _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs IN SRV 0 100 3268 node1 ; ; ldap servers _ldap._tcp IN SRV 0 100 389 node1 _ldap._tcp.dc._msdcs IN SRV 0 100 389 node1 _ldap._tcp.pdc._msdcs IN SRV 0 100 389 node1 _ldap._tcp.e67cd6da-dbd0-492d-96e2-2dc778abaebe.domains._msdcs IN SRV 0 100 389 node1 _ldap._tcp.Default-First-Site-Name._sites IN SRV 0 100 389 node1 _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs IN SRV 0 100 389 node1 ; ; krb5 servers _kerberos._tcp IN SRV 0 100 88 node1 _kerb...

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 7c933af1-3dd9-4688-8a4e-27a9dfd4f76a. sources=0 [2] sinks=1 [2017-10-25 10:39:41.289075] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on e426c1a7-2088-492d-b92a-6d8a7c667aef. sources=0 [2] sinks=1 [2017-10-25 10:39:41.291585] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on e426c1a7-2088-492d-b92a-6d8a7c667aef [2017-10-25 10:39:41.294946] I [MSGID: 108026] [afr-self-heal-c...