similar to: changes on DC not replicated, while showrepl reports no issues

On 17/11/2020 11:54, mj via samba wrote: > Hi, > > Checking a bit more today, as the two changes on DC4 have *still* not > propagated? to DC2/DC3, I discovered the > ?samba-tool drs uptodateness > command. > > I gives the following output, not sure what "unknown invocation ID" > means. I hope someone here is able to explain..? > > It's output: >

Hi, Checking a bit more today, as the two changes on DC4 have *still* not propagated to DC2/DC3, I discovered the samba-tool drs uptodateness command. I gives the following output, not sure what "unknown invocation ID" means. I hope someone here is able to explain..? It's output: > root at dc2:~# samba-tool drs uptodateness > Unknown invocation ID

Same as MJ and You. So you have 5 DC's running. > >>> Unknown invocation ID 556b2cb4-e576-48e2-bb7c-7f62caee84fc > >>> Unknown invocation ID 7281ff0f-5af2-4ded-bdaf-362f1545d221 > >>> Unknown invocation ID 82b24c02-16cb-4ed1-b68b-a047c26886a9 > >>> Unknown invocation ID b97cc603-6d03-4ad0-8629-be408fed8d69 > >>> Unknown invocation

Hi all, Samba (sernet) 4.1.7, and we're getting high cpu usage on dc1, and on dc2 (my 'secondary' dc): root at dc2:~# samba-tool drs showrepl Default-First-Site-Name\DC2 DSA Options: 0x00000001 DSA object GUID: 5e93a102-2963-496a-af16-0c51eebb2e31 DSA invocationId: 82b24c02-16cb-4ed1-b68b-a047c26886a9 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=samba,DC=domain,DC=com

We have setup an asterisk box to let everybody call into the university internal network, but I get unexpected hangups when doing an outbound call from SIP to the ISDN interface, and it happens from 20 seconds to some minutes into the call. ----------the dial and the problem----------- -- Executing Dial("SIP/57966-a19d", "Modem/g1:96121||rt|") in new stack --

Hi, Sorry to bother you on this mailing list, however I tried everything else and I am desperate to get this running. Please send me any hints you can think of. I have installed openssh-3.7.1p2 on a ppc target and trying to connect to an sshd running on a redhat 9 with openssh-3.5p1. I keep getting the error "Disconnecting: Corrupted check bytes on input" no matter what I tried. I

Hi, A client had some issues with their glusterfs cluster and botched an update. Currently they have loads of broken symlinks in their bricks .glusterfs folder Like the second one below lrwxrwxrwx 1 root root 55 Jul 14 2017 591c33db-e88b-4544-9372-bea4ec362360 -> ../../83/4a/834a8af8-95a4-4f8a-9810-4e4d829e87f9/394947 lrwxrwxrwx 1 root root 74 Jul 17 2017

Anyone got a recommendation for a cheap (but good) colour laser printer that runs under CentOS-5.5 ? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

Hello, I have a centos 5.2 core 2 duo 3.0 GHZ with 2 GB ram which is working as a Virtual machine. i've just upgraded the hosting physical server from 32 GB to 64 GB of ram. which in turn, would require me to upgrade the VM to 8 GB. this is a 32 bit centos installation, would the system recognize and use the 8 GB? the option of using a 64 bit centos isnt possible. So i'm turning to you

Hi. Red Hat is saying that AMD Liano A8 CPU's are not supported by RHEL/CentOS 6: https://access.redhat.com/knowledge/articles/65431 Is that true? What can I expect if I try to install CentOS 6.3 on PC with that CPU? -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe Google is the Mother, Google is the Father, and traceroute is your trusty Spiderman... StarOS,

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