search for: 49ad

...===== ================ ================ ================ SIP/8484-00000000 Am conf-adminmenu 8484 SIP/8484-00000001 m conf-menu 8484 SIP/8484-00000002 Am conf-adminmenu 8484 -- Channel SIP/8484-00000001 left 'softmix' base-bridge <485fcffc-49ad-4e86-8d1b-4655631a232a> -- Channel CBAnn/1701414-00000000;2 joined 'softmix' base-bridge <485fcffc-49ad-4e86-8d1b-4655631a232a> -- <CBAnn/1701414-00000000;1> Playing 'confbridge-leave.gsm' (language '') -- Channel CBAnn/1701414-00000000;2 left '...

...d' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create vdi-uuid=c95af56f-799f-49ad-a64f-82eca3299b50 vm-uuid=d859ed1a-760f-9928-b5be-f0ab1790b15f type=Disk mode=RW device=2 b2e8f7b3-34c4-fe9a-486e-6551b8ba4165 # xe vbd-plug uuid=b2e8f7b3-34c4-fe9a-486e-6551b8ba4165 # ls /dev/xv* ls: cannot access /dev/xv*: No such file or directory Data from different logs: SMlog: [12866] 20...

...n grub entry: menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set root='(hd0,msdos2)' search --no-floppy --fs-uuid --set 935213fd-c3c6-49ad-b818-a3b67704c585 echo 'Loading Linux 2.6.32-5-xen-amd64 ...' multiboot /xen-4.0-amd64.gz placeholder acpi=off module /vmlinuz-2.6.32-5-xen-amd64 placeholder root=/dev/mapper/main-root ro quiet echo 'Loading initial ramdisk ...' module /initrd....

...Zap/g2/64290118 Zap/19-1 (default s 1 ) Dialing AppDial (Outgoing Line) SIP/1007-dc3c (network 965627640 2 ) Ring Dial Zap/g2/65627640 Zap/18-1 (default s 1 ) Dialing AppDial (Outgoing Line) SIP/1007-49ad (network 964255575 2 ) Ring Dial Zap/g2/64255575 Zap/17-1 (default s 1 ) Up Bridged Call SIP/1007-de63 SIP/1007-de63 (network 965699062 2 ) Up Dial Zap/g2/65699062 Regards, Antonio Rabena -------------- next part -...

Assume the following question is in regards to Puppet 3.3.2. So my question is in relation to audit. file { ''/some/random/path/through/the/tree/to/a/file'': owner => ''luke'', group => ''rebelalliance'', mode => ''0444'', audit => all } And more specifically: will the named file be force-owned to luke with the

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

...2CF388A5764A052 (1ac15de5-7f4b-44da-9f76-974e92b94d16) on home-client-2 [2017-10-25 10:14:12.330767] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/ADFFEFF5C34202705A66703CF4A3A372BC83C369 (6981b1d5-c775-49ad-94f7-8a5e8c74e42c) on home-client-2 [2017-10-25 10:14:12.350768] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/F43BB1B3AA18D6EDE80BE656AB77DB3998DA12EB (618aab40-15fc-4f18-a8df-78abd0a35f3e) on home-cli...