search for: 4d1f

Displaying 7 results from an estimated 7 matches for "4d1f".

Did you mean: 41df
2004 Jun 30
0
Dial plan errors
...xten => s-.,1,Voicemail(u${ARG1}) But this is what happens when no-one answers: -- Executing Macro("SIP/201-c410", "stdexten|201|SIP/201") in new stack -- Executing Dial("SIP/201-c410", "SIP/201|20|r") in new stack -- Called 201 -- SIP/201-4d1f is ringing -- Nobody picked up in 20000 ms -- Executing Goto("SIP/201-c410", "s-NOANSWER") in new stack -- Goto (macro-stdexten,s,0) -- Timeout on SIP/201-c410 == CDR updated on SIP/201-c410 -- Executing Hangup("SIP/201-c410", "") in new...
2004 Jul 01
0
Invalid context
...xten => s-.,1,Voicemail(u${ARG1}) But this is what happens when no-one answers: -- Executing Macro("SIP/201-c410", "stdexten|201|SIP/201") in new stack -- Executing Dial("SIP/201-c410", "SIP/201|20|r") in new stack -- Called 201 -- SIP/201-4d1f is ringing -- Nobody picked up in 20000 ms -- Executing Goto("SIP/201-c410", "s-NOANSWER") in new stack -- Goto (macro-stdexten,s,0) -- Timeout on SIP/201-c410 == CDR updated on SIP/201-c410 -- Executing Hangup("SIP/201-c410", "") in new...
2004 Jul 20
0
R: Dial plan errors
...xten => s-.,1,Voicemail(u${ARG1}) But this is what happens when no-one answers: -- Executing Macro("SIP/201-c410", "stdexten|201|SIP/201") in new stack -- Executing Dial("SIP/201-c410", "SIP/201|20|r") in new stack -- Called 201 -- SIP/201-4d1f is ringing -- Nobody picked up in 20000 ms -- Executing Goto("SIP/201-c410", "s-NOANSWER") in new stack -- Goto (macro-stdexten,s,0) -- Timeout on SIP/201-c410 == CDR updated on SIP/201-c410 -- Executing Hangup("SIP/201-c410", "") in new...
2012 Aug 31
0
oops with btrfs on zvol
...I add a layer on top of zvol (losetup, or iscsi export-import) then btrfs works just fine. Syslog shows this (from Ubuntu''s 3.2 kernel): #===== Aug 31 20:30:13 DELL kernel: [34307.828311] zd0: unknown partition table Aug 31 20:30:34 DELL kernel: [34328.129249] device fsid cfd88ff9-def8-4d1f-9435-65becd5fa2b7 devid 1 transid 4 /dev/zd0 Aug 31 20:30:34 DELL kernel: [34328.134001] btrfs: disk space caching is enabled Aug 31 20:30:34 DELL kernel: [34328.135701] BUG: unable to handle kernel NULL pointer dereference at (null) Aug 31 20:30:34 DELL kernel: [34328.137200] IP: [<ff...
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
...27:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 2e706752-f1d5-49f4-b710-801c7a12f7de. sources=0 [2] sinks=1 [2017-10-25 10:40:26.006899] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on bbd03131-84c8-4d1f-9c77-36fa8ad34869 [2017-10-25 10:40:26.009588] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on bbd03131-84c8-4d1f-9c77-36fa8ad34869. sources=0 [2] sinks=1 [2017-10-25 10:40:26.025823] I [MSGID: 108026] [afr-self-heal-common.c:132...