similar to: How to keep samba4 dc work fine when windows dc offline?

Hello, I configured a main DC and secondary domain controller successfully. The only problem is that I want the secondary DC to Stand By, so most of the time it is shutdown. The problem is that when the secondary DC is shutdown on the primary DC I receive continously the following error which is filling the logs: Feb 1 14:23:56 saturno samba[3217]: [2014/02/01 14:23:56.021591, 0]

Hello all this morning i followed wiki in subject to replicate my active directory, but it fails with this error: [root at dc1 etc]#  samba-tool drs showrepl Default-First-Site-Name\DC1 DSA Options: 0x00000001 DSA object GUID: 8ba457e4-815d-4bd3-a748-8b5ddb53fd5f DSA invocationId: 834770f4-c5a7-48c7-bc77-66e2cf37e557 ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=lxcerruti,DC=com        

Hi, Having an test environment here with four sites, sites 2-4 are connected to site 1 via vpn. No vpn tunnels between sites 2-4, so the sites 2-4 can only communicate with site 1. Each site has it's samba4 AD DC server and they are all part of the same domain. Did abit of reading and found that i must use so called SiteLinks to replicate the site objects between sites 2-4 via site 1.

hii all i have some issue with my samba 4 installation, i use samba 4.1.3, suddenty my dns stop working and i try to restart the service but nothing good happen i check on samba log i found this Aug 25 21:15:39 pdc samba[6605]: [2014/08/25 21:15:39.206091, 0] ../lib/util/fault.c:72(fault_report) Aug 25 21:15:39 pdc samba[6605]: ===============================================================

I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is showing the following: root at dtdc03:~# tail -f /usr/local/samba/var/log.samba [2016/12/01 10:14:39.167794, 0] ../source4/librpc/rpc/dcerpc_sock.c:245(continue_ip_open_socket) Failed to connect host 192.168.16.50 (aa03011a-94c2-4c52-bc60-6fd2f75d35e5._msdcs.dtshrm.dt) on port 135 - NT_STATUS_CONNECTION_REFUSED.

Hello Samba team ! On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) : -> One PDC : pdc01 -> Two "slave" DC : sdc02, sdc03 I don't know why, but sometimes Samba receive the SIGTERM signal and restart even if I remove it from the logrotate configuration. On "pdc01" I see : ---------- pdc01 (log.samba) ---------- SIGTERM: killing children

Hi, I've been running samba on a linux machine (dslkayak) to share a folder and a printer with several windows machines on a home network for a couple of years without problems. I've recently added a second linux machine (ps3ydl) to the network, but I cannot access it from any other machines on the network even though it can access the other network shares. There error I get is:

On 2016-12-04 09:11, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is >> showing the following: >> >> root at dtdc03:~# tail -f /usr/local/samba/var/log.samba >> [2016/12/01

Dear All, Recently I notice that sometime the AD DC will die sometime. Any one have see this issue before? And yesterday case lead me to believes that this error message was the issue... They are repetitive and thus I only show 2... [2015/07/29 00:00:04.620033, 0] ../source4/librpc/rpc/dcerpc_util.c:681(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for

New to linux and new to Samba so any direction in troubleshooting would be helpful. Here is what I have so far. Within a half an hour of a reboot of the server my cpu reaches high numbers and becomes slow to respond on all actions. With my limited understanding I have used vmstat to observe the system. I noticed is that the numbers of forks grows from 1-2k to 43k within 30 minutes after reboot. I

On 18/12/14 16:19, Germ van Eck wrote: > Not sure about the high CPU load, but you have the [netlogon] share > twice in your smb.conf. Your first matches mine, have you added the > second yourself? > The second one looks weird with 2 path definitions. > Cj Tibbetts schreef op do 18-12-2014 om 08:59 [-0700]: >> New to linux and new to Samba so any direction in troubleshooting

Hi there, I posted earlier asking about testing named routes in functional tests, but got no response, so I''m making my question less specific. It seems from the docs that it''s possible to to test named routes in cases such as: asserts_redirect_to name_url(:param => "whatever") but I haven''t seen any mention of it being used with any other tests and I keep

What Samba version are you using? I have seen a similar problem triggered by connectivity issues between the DCs. What's the output from samba-tool drs showrepl? Still, I haven't found a solution... On Sat, Aug 1, 2015 at 5:30 AM, Min Wai Chan <dcmwai at gmail.com> wrote: > Just to ask. > Anyone can shard some light on that wrong is that? > > Thank you. > > Min

>> >> Hello Samba team ! >> >> On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) >> : >> -> One PDC : pdc01 >> -> Two "slave" DC : sdc02, sdc03 >> >> I don't know why, but sometimes Samba receive the SIGTERM signal and >> restart even if I remove it from the logrotate configuration. On >>

On 2016-12-04 10:25, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 09:43:25 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > I have two DC's running

2016-04-01 23:36 GMT+02:00 Rowland penny <rpenny at samba.org>: > On 30/03/16 13:35, Prunk Dump wrote: >> >> Hello Samba team ! >> >> On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) >> : >> -> One PDC : pdc01 >> -> Two "slave" DC : sdc02, sdc03 >> >> I don't know why, but sometimes Samba

Hi, i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached. Anyone who have an information about that or a solution? Thanks Sven orion:~ # samba-tool drs showrepl Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -

Hello all this morning i followed wiki in subject to replicate my active directory, but it fails with this error: [root at dc1 etc]#  samba-tool drs showrepl Default-First-Site-Name\DC1 DSA Options: 0x00000001 DSA object GUID: 8ba457e4-815d-4bd3-a748-8b5ddb53fd5f DSA invocationId: 834770f4-c5a7-48c7-bc77-66e2cf37e557 ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=lxcerruti,DC=com        

Hi David, Chandler, I see lldb tests hang often, and then I kill the dotest process. I'd like to stop running check-all too, but I feel it's important when I modify FileCheck. The flakiness that Chandler mentioned makes it time-consuming to verify test results. Joel On Wed, Jan 2, 2019 at 4:41 PM Chandler Carruth via llvm-dev < llvm-dev at lists.llvm.org> wrote: > What

> On Jun 13, 2018, at 11:18 AM, Jonas Devlieghere via lldb-dev <lldb-dev at lists.llvm.org> wrote: > > Hi Pavel, > >> On Jun 13, 2018, at 6:56 AM, Pavel Labath <labath at google.com <mailto:labath at google.com>> wrote: >> >> Hello again, >> >> It's been nearly six months since my first email, so it's a good time >> to