search for: 422c

...etwork-bridge status ============================================================ 7: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether 00:14:4f:eb:42:2c brd ff:ff:ff:ff:ff:ff inet 10.245.144.19/24 brd 10.245.4.255 scope global eth0 inet6 fe80::214:4fff:feeb:422c/64 scope link valid_lft forever preferred_lft forever 7: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether 00:14:4f:eb:42:2c brd ff:ff:ff:ff:ff:ff inet 10.245.144.19/24 brd 10.245.4.255 scope global eth0 inet6 fe80::214:4fff:feeb:422c/64 scope link...

...2017 16:24:31 +0100 L.P.H. van Belle <belle at bazuin.nl> wrote: > Hai Rowland, > > Can post your exact command you used, so im sure i dont get different > outputs. > OK, on a windows 21012R2 DC: Get-Acl C:|Windows\SYSVOL\sysvol\domain.local\Policies\'{5FD30AA2-B678-422C-9C0E-4E270488EDE4}' | Format-List NOTE: The above is all one line. Which leads to this output: Path :sysvol\DOMAIN.LOCAL\Policies\{5FD30AA2-B678-422C-9C0E-4E270488EDE4} Owner : HOME\Domain Admins Group : HOME\Domain Admins Access : CREATOR OWNER Allow FullControl NT AUTHORITY\ENTERPRI...

On Tue, 7 Mar 2017 10:26:03 -0800 Kris Lou via samba <samba at lists.samba.org> wrote: > Hang on, can you explain this a little further? I thought that Domain > Admins was issued gidNumber 512 by default. In addition, sysvolreset > is not recommended to fix potential SysVol replication problems with > GPO perms? > No Domain Admins doesn't get gidNumber 512 by default,

...t; wrote: > > > Hai Rowland, > > > > Can post your exact command you used, so im sure i dont get different > > outputs. > > > > OK, on a windows 21012R2 DC: > > Get-Acl > C:|Windows\SYSVOL\sysvol\domain.local\Policies\'{5FD30AA2-B678-422C-9C0E- > 4E270488EDE4}' > | Format-List > > NOTE: The above is all one line. > > Which leads to this output: > > Path   :sysvol\DOMAIN.LOCAL\Policies\{5FD30AA2-B678-422C-9C0E- > 4E270488EDE4} > Owner  : HOME\Domain Admins Group  : HOME\Domain Admins &g...

...************************************************ Tcpdump from the 1.0-test-56 server of failed fetch request: 14:43:43.214921 IP noctis.shsu.edu.61362 > unxmail.shsu.edu.imap: P 177:253(76) ack 608 win 65535 <nop,nop,timestamp 519041530 438977827> 0x0000: 4500 0080 ae0c 4000 4006 422c 9e87 0bfc E..... at .@.B,.... 0x0010: 9e87 0135 efb2 008f 2fa2 46d7 61ef eaee ...5..../.F.a... 0x0020: 8018 ffff b026 0000 0101 080a 1eef f1fa .....&.......... 0x0030: 1a2a 4523 4130 3038 2055 4944 2046 4554 .*E#A008.UID.FET 0x0040: 4348 2032 2028 5549 44...

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

...eb9358/310DA2AE5A71340F1B63A1B3B2D8F9B5804FF0FD (86052494-81ba-4342-b538-8df4893e32c9) on home-client-2 [2017-10-25 10:14:18.690814] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/1363D2A7B3A36A3399ECE8C2422C1A933F20202E (1d904a1d-d276-4420-884d-9c26c8ea8108) on home-client-2 [2017-10-25 10:14:18.764458] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/BAC1C2816A4BC68140C0E13A453EC7C6970E9397 (31adf01e-5a08-492...