search for: beb4

...etc/hosts and /etc/resolv.conf . > > Send the output of "ping -c5 fs1" command from your machine? [gruss at ws1 ~]$ cat /etc/resolv.conf # Generated by NetworkManager domain tss-engineering.com search tss-engineering.com tss-engineering.com. nameserver 192.168.1.1 nameserver fd78:beb4:a733::1 [gruss at ws1 ~]$ cat /etc/hosts 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 [gruss at ws1 ~]$ ping -c5 fs1 PING fs1.tss-engineering.com (192.168.1.10) 56(84) bytes of data. 64 bytes from FS1.tss-engineering.com (192.168.1.10): icmp_seq=1 ttl=64 tim...

Replication has been running smoothly until I upgraded to 4.5.0. I had various errors with all BDCs and a force sync didn't resolve it. I shutdown all BDCs, demoted them with --remove-other-dead-server then joined new BDCs with new names. At first replication was intermittently failing (consecutive failures counter kept resetting), but it seemed OK, just slow if anything. Now they all

...xecuting the following with nsupdate seems to have fixed replication. update add 28f7281f-3955-4885-8a7d-42a36ee87590._msdcs.mediture.dom. 900 A 192.168.222.5 show send update add 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa._msdcs.mediture.dom. 900 A 172.16.1.106 show send update add fe066b13-6f9e-4f3c-beb4-37df1292b8cb._msdcs.mediture.dom. 900 A 192.168.168.65 show send New DNS records I create don't resolve though. Also, I get an error when I open Active Directory Users and Computers, "The RPC server is unavailable". Thanks, Arthur On 10/17/2016 11:44 AM, Arthur Ramsey wrote: >...

...Send the output of "ping -c5 fs1" command from your machine? >> > > [gruss at ws1 ~]$ cat /etc/resolv.conf > # Generated by NetworkManager > domain tss-engineering.com > search tss-engineering.com tss-engineering.com. > nameserver 192.168.1.1 > nameserver fd78:beb4:a733::1 > > [gruss at ws1 ~]$ cat /etc/hosts > 127.0.0.1 localhost.localdomain localhost > ::1 localhost6.localdomain6 localhost6 > > [gruss at ws1 ~]$ ping -c5 fs1 > PING fs1.tss-engineering.com (192.168.1.10) 56(84) bytes of data. > 64 bytes from...

I increased the debug level to 10 and found this dreplsrv_notify: Failed to send DsReplicaSync to fe066b13-6f9e-4f3c-beb4-37df1292b8cb._msdcs.mediture.dom for DC=DomainDnsZones,DC=mediture,DC=dom - NT_STATUS_OBJECT_NAME_NOT_FOUND : WERR_BADFILE. I manually created the DNS entry, but it doesn't resolve. Other DNS records supplied by BIND_DLZ are working. I tried adding a host file entry, but that didn't...

Changes replicate to it, but not from it. vsc\VSC-DC02 DSA Options: 0x00000001 DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom vsc\DC01 via RPC DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 Last attempt @ Tue Mar 14 09:26:12 2017 CDT was su...

Hi All, I've configured a Fedora 20 server with samba to share a few user directories and a printer. From a Windows 8 laptop, I am able to address the samba server by it's name (fs1) From a Fedora 20 client (ws1), I am able to address the samba server by IP address, but not by name. [gruss at ws1 ~]$ smbclient --version Version 4.1.15 [gruss at ws1 ~]$ smbclient -L 192.168.1.10

On 3/14/2017 10:29 AM, Arthur Ramsey wrote: > Changes replicate to it, but not from it. > > vsc\VSC-DC02 > DSA Options: 0x00000001 > DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb > DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 > > ==== INBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=mediture,DC=dom > vsc\DC01 via RPC > DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 > Last attempt @...

I forgot to associate inter-site links (all using default), which fixed a lot though I'm still having an issue. * vsc site o vsc-dc01 o vsc-dc02 * aws site o aws-dc01 * epo site o epo-dc01 * vsc-dc01 => anywhere: OK * vsc-dc02 => anywhere: not replicating * aws-dc01 => anywhere: OK * epo-dc01 => anywhere: OK I've tried with samba_kcc =

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

...358/A6448BE11DA9DEAF941A5CC258E7537C3775BE3C (0d6d4775-0874-49b3-9f98-21383642872a) on home-client-2 [2017-10-25 10:14:20.352684] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/FAFB4DB3C76E3367FC1E9C020C0BEB409F7F38A7 (96ed5cc4-842e-4c68-9885-c6c8b2a6cc61) on home-client-2 [2017-10-25 10:14:20.372743] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/D66455923D9E5387AECFF6197B04DB63255BE6D0 (ac3342a7-9ed0-436b-a...