search for: 4e5b

Displaying 10 results from an estimated 10 matches for "4e5b".

Did you mean: 485b
2015 Mar 16
1
Asterisk 13.1.0/PJSIP outbound calling using SIP trunk: Unable to create request with auth.No auth credentials for any realms in challenge.
...e invite auth exchange and see if anything differs. > --------------------- > > Transmitting SIP request (885 bytes) to UDP:65.254.44.194:5060 ---> > INVITE sip:12025551212 at 65.254.44.194:5060 SIP/2.0 > Via: SIP/2.0/UDP > 18.18.19.123:5060;rport;branch=z9hG4bKPj70617ad5-d57a-4e5b-8043-086b0b8ebba2 > From: <sip:sonny at 192.168.13.121>;tag=6953923b-1798-41a0-a983-fe27ff6a1db8 > To: <sip:12025551212 at 65.254.44.194> > Contact: <sip:dea9e47d-3a06-4e6e-b88f-8bac70fb6e0b at 18.18.19.123:5060> > Call-ID: 012135e9-b05e-4ffd-8ed7-32b3160273e3 > CSe...
2015 Mar 15
0
Asterisk 13.1.0/PJSIP outbound calling using SIP trunk: Unable to create request with auth.No auth credentials for any realms in challenge.
...The sequence below just repeats ad-nauseam. Is this a SIP trunk issue? Thanks! --------------------- Transmitting SIP request (885 bytes) to UDP:65.254.44.194:5060 ---> INVITE sip:12025551212 at 65.254.44.194:5060 SIP/2.0 Via: SIP/2.0/UDP 18.18.19.123:5060 ;rport;branch=z9hG4bKPj70617ad5-d57a-4e5b-8043-086b0b8ebba2 From: <sip:sonny at 192.168.13.121>;tag=6953923b-1798-41a0-a983-fe27ff6a1db8 To: <sip:12025551212 at 65.254.44.194> Contact: <sip:dea9e47d-3a06-4e6e-b88f-8bac70fb6e0b at 18.18.19.123:5060> Call-ID: 012135e9-b05e-4ffd-8ed7-32b3160273e3 CSeq: 6753 INVITE Allow: OPT...
2015 Mar 15
4
Asterisk 13.1.0/PJSIP outbound calling using SIP trunk: Unable to create request with auth.No auth credentials for any realms in challenge.
Yes, I think the dial does get executed (sonny calling outbound 202-555-1212): core set verbose 3 Console verbose was OFF and is now 3. -- Executing [912025551212 at from-internal:1] Log("PJSIP/sonny-00000031", "NOTICE, Dialing out from "" <sonny> to 12025551212 through fromgw") in new stack [Mar 15 19:27:06] NOTICE[16648][C-00000022]: Ext. 912025551212:1 @
2017 Jul 19
2
[ovirt-users] ovirt 4.1 hosted engine hyper converged on glusterfs 3.8.10 : "engine" storage domain alway complain about "unsynced" elements
...4f-b6ed-ea789dd8821b/images/19d71267- > 52a4-42a3-bb1e-e3145361c0c2/7a215635-02f3-47db-80db-8b689c6a8f01 > <gfid:9a601373-bbaa-44d8-b396-f0b9b12c026f> > /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/dom_md/ids > <gfid:1e309376-c62e-424f-9857-f9a0c3a729bf> > <gfid:e3565b50-1495-4e5b-ae88-3bceca47b7d9> > <gfid:4e33ac33-dddb-4e29-b4a3-51770b81166a> > /__DIRECT_IO_TEST__ > <gfid:67606789-1f34-4c15-86b8-c0d05b07f187> > <gfid:9ef88647-cfe6-4a35-a38c-a5173c9e8fc0> > /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/images/88d41053- > a257-4272-9e2e-2f3de07...
2018 Apr 18
0
Bitrot - Restoring bad file
On 04/17/2018 06:25 PM, Omar Kohl wrote: > Hi, > > I have a question regarding bitrot detection. > > Following the RedHat manual (https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html/administration_guide/bitrot-restore_corrupt_file) I am trying out bad-file-restoration after bitrot. > > "gluster volume bitrot VOLNAME status" gets me the
2018 Apr 17
2
Bitrot - Restoring bad file
Hi, I have a question regarding bitrot detection. Following the RedHat manual (https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html/administration_guide/bitrot-restore_corrupt_file) I am trying out bad-file-restoration after bitrot. "gluster volume bitrot VOLNAME status" gets me the GFIDs that are corrupt and on which Host this happens. As far as I can tell
2017 Jul 19
0
[ovirt-users] ovirt 4.1 hosted engine hyper converged on glusterfs 3.8.10 : "engine" storage domain alway complain about "unsynced" elements
...789dd8821b/images/19d71267-52a4-42a3-bb1e-e3145361c0c2/7a215635-02f3-47db-80db-8b689c6a8f01 > <gfid:9a601373-bbaa-44d8-b396-f0b9b12c026f> > /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/dom_md/ids > <gfid:1e309376-c62e-424f-9857-f9a0c3a729bf> > <gfid:e3565b50-1495-4e5b-ae88-3bceca47b7d9> > <gfid:4e33ac33-dddb-4e29-b4a3-51770b81166a> > /__DIRECT_IO_TEST__ > <gfid:67606789-1f34-4c15-86b8-c0d05b07f187> > <gfid:9ef88647-cfe6-4a35-a38c-a5173c9e8fc0> > /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/images/88d41053-a257-427...
2017 Oct 26
0
not healing one file
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
2017 Oct 26
3
not healing one file
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
2017 Oct 26
2
not healing one file
...0A49EEFBD641E97 (dedb0f80-a621-4891-bb6a-3f89f5ab0e3f) on home-client-2 [2017-10-25 10:14:19.278184] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/749E508AD5AFDE9EF4D4DDD1CDB4B43002A11C37 (3dd52b84-2b06-4e5b-8748-194eb4b9aedf) on home-client-2 [2017-10-25 10:14:19.298333] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/658FFAEBF80F5B993E4F1CB9351035A37C4CCAB9 (40c9749d-a074-40d9-aeb9-eac73db805b9) on home-cli...