search for: 41f9

2015-11-10 22:07 GMT+08:00 James <lingpanda101 at gmail.com>: > I't appears all versions of Samba 4.2.X allow secure updates. It's >> transitioning to any version of Samba 4.3.X that prevents secure >> updates. Looking at the Wireshark captures of a successful update >> >> https://www.cloudshark.org/captures/79e72c42de44 >> >>

...princ2.samdom.example.lan. against SRV > _ldap._tcp.dc._msdcs.samdom.example.lan dc-site1.samdom.example.lan 389 > Failed to find matching DNS entry SRV > _ldap._tcp.dc._msdcs.samdom.example.lan dc-site1.samdom.example.lan 389 > Looking for DNS entry SRV > _ldap._tcp.4e70c2a8-652f-41f9-8713-385fcd661d44.domains._msdcs.samdom.example.lan > dc-site1.samdom.example.lan 389 as > _ldap._tcp.4e70c2a8-652f-41f9-8713-385fcd661d44.domains._msdcs.samdom.example.lan. > Checking 0 100 389 dc-princ1.samdom.example.lan. against SRV > _ldap._tcp.4e70c2a8-652f-41f9-8713-385fcd661d...

...89 Checking 0 100 389 dc-princ2.samdom.example.lan. against SRV _ldap._tcp.dc._msdcs.samdom.example.lan dc-site1.samdom.example.lan 389 Failed to find matching DNS entry SRV _ldap._tcp.dc._msdcs.samdom.example.lan dc-site1.samdom.example.lan 389 Looking for DNS entry SRV _ldap._tcp.4e70c2a8-652f-41f9-8713-385fcd661d44.domains._msdcs.samdom.example.lan dc-site1.samdom.example.lan 389 as _ldap._tcp.4e70c2a8-652f-41f9-8713-385fcd661d44.domains._msdcs.samdom.example.lan. Checking 0 100 389 dc-princ1.samdom.example.lan. against SRV _ldap._tcp.4e70c2a8-652f-41f9-8713-385fcd661d44.domains._msdcs.sa...

...11.11-300. Current boot sequence that works with 4.11.11-300 is: ======================================================== load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 46985d35-b7e3-41f9-9bc0-8ae6c11bc84c else search --no-floppy --fs-uuid --set=root 46985d35-b7e3-41f9-9bc0-8ae6c11bc84c fi linuxefi /vmlinuz-4.11.11-300.fc26.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap nouveau.runpm=0 rhgb quiet resume=/dev/dm-1 initrdefi /initramfs-4.11.11-300...

Hi Jeremy, Am 02.06.2015 um 17:10 schrieb Jeremy Allison <jra at samba.org>: > Thanks a lot for checking these things ! No one on the Team > runs OS/2 so it isn't easy to test we still work with it, > although we should. > > Can you log bugs for these issues and we will work through > them with you if you're willing to do the testing work ? Sure, I will comment

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

...common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on 1dc26993-8716-414b-a727-95140ace8220. sources=0 [2] sinks=1 [2017-10-25 10:40:22.626476] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on a8da7977-30c9-41f9-bd6b-1a3f71d0a951. sources=0 [2] sinks=1 [2017-10-25 10:40:22.627893] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on a8da7977-30c9-41f9-bd6b-1a3f71d0a951 [2017-10-25 10:40:22.639699] I [MSGID: 108026] [afr-self-heal-c...