search for: 89e3

...*CLI> Jul 25 16:49:25 WARNING[114695]: chan_sip.c:2820 process_sdp: No compatible codecs! Jul 25 16:49:28 WARNING[114695]: chan_sip.c:2820 process_sdp: No compatible codecs! Jul 25 16:49:28 WARNING[114695]: chan_sip.c:2820 process_sdp: No compatible codecs! -- Executing Dial("SIP/andrew-89e3", "SIP/jeremy|20") in new stack -- Called jeremy -- SIP/jeremy-b7a9 is ringing -- SIP/jeremy-b7a9 answered SIP/andrew-89e3 -- Attempting native bridge of SIP/andrew-89e3 and SIP/jeremy-b7a9 Jul 25 16:49:36 WARNING[851980]: rtp.c:1392 ast_rtp_bridge: codec0 = 12 is not...

...eth0" HWADDR=52:54:00:76:0D:7F ONBOOT=yes UUID="8ab7ac2c-c089-4f9f-bb65-1abb781fe912" IPV6INIT=no BOOTPROTO=none TYPE=Ethernet IPADDR=96.92.106.4 PREFIX=29 GATEWAY=96.92.106.6 NOZEROCONF=yes and NAME="eth1" HWADDR=52:54:00:B3:03:66 ONBOOT=yes UUID="1d590cef-d5a2-400e-89e3-3c618f785c41" IPV6INIT=no BOOTPROTO=none TYPE=Ethernet IPADDR=192.168.6.222 PREFIX=24 DNS1=192.168.6.1 IPV4_FAILURE_FATAL=no NOZEROCONF=yes Emmett

On 10/12/2015 10:17 AM, Gordon Messmer wrote: > On 10/11/2015 03:00 PM, Emmett Culley wrote: >> I just noticed that when rebooting a CentOS 7 server the firewall comes back up with both interfaces set to REJECT, instead of the eth1 interface set to ACCEPT as defined in 'permanent' firewalld configuration files. > > Rather than paraphrasing, could you show the specific

Hi xen developers, Does any of you know how to disable the cirrus-vga emulation for hvm in xen? I have been trying to disable that from the source codes, but even with that, I still see a VGA controller when I boot up my guest domain. In particular, I would like to do this because I am passing through a graphics card to my guest domain using direct pass through. Thanks, - billy

...87 74fa 6db1 fa99 0e5f \.gm....t.m...._ 0x0640: f0c6 c1fa 5afd 9cd6 22cb 7b14 a9f3 f4c2 ....Z...".{..... 0x0650: 6417 a0da 0932 4090 96ad 037e 08dc 0af7 d....2 at ....~.... 0x0660: 5c43 f09b b347 556d ad85 35c1 07b9 55a6 \C...GUm..5...U. 0x0670: b55f 20ae b2b7 3a8a 6afc 89e3 5516 35c9 ._....:.j...U.5. 0x0680: 9303 7389 f539 0776 ee6f 4eb2 d1df aad8 ..s..9.v.oN..... 0x0690: 35bc 5b18 cbfd be8a 78b6 a559 f6ea 7455 5.[.....x..Y..tU 0x06a0: 332f cb63 f205 30fa a6c4 3226 59da 557e 3/.c..0...2&Y.U~ 0x06b0: df7c 5441 3890 8164 a7a5 aee0 3213 e439 ....

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

...D70DC37B06DB2209E8368C7E4 (4e715144-9dfa-4bf9-88de-b900c1bdde82) on home-client-2 [2017-10-25 10:13:56.775635] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/1F6C6ACD29430104EAA6A5DB50C9F833F64CA1BF (083889e3-a827-44e0-8aa3-93b74df30c2d) on home-client-2 [2017-10-25 10:13:56.805393] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/8CFE862B002838B8030D0D7C2F53CC5030C706DB (afc23745-89f6-4bbe-8bb3-f2ba1c32251f) o...