similar to: Samba suddenly restart and replication does not works anymore

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

>> >> 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 >>

I'd check for differences in the ldap trees with samba-tool ldapcmp first If such are found try an manual full sync replication to fix the difference. I had an similar issue a while back and an deleted object on one dc caused such sigterm's. Had to get that deleted object out of the way afterwards the dc's where stable again. Am 30.03.2016 um 14:35 schrieb Prunk Dump: > Hello

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 receive the SIGTERM signal and > restart even if I remove it from the logrotate configuration. On >

2017-06-21 14:29 GMT+02:00 Prunk Dump <prunkdump at gmail.com>: > Thank you very much Louis, Rowland, Mike ! > > I have made all the changes proposed by Louis but still have the same problem. > > -> kinit works now with /var/lib/samba/private/secrets.keytab > ------------------------ > ~# kinit -k -t /var/lib/samba/private/secrets.keytab FICHDC$ > ~# >

Hi, I'm resending this to the list since I cannot see it on the archive, for some reason... I recently upgraded two (running stable) systems from Debian Wheezy to Jessie. Samba version has not changed since on Wheezy I was using the one from wheezy-backports (v4.1.17), same as on jessie. These are 2 basic DCs without any additional config. Since the upgrade, every day at either at 10 PM or 8

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

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, I'm currently planning an environment which will survive any disaster like domain controller crash: PDC02 | VPN | switch | | PDC01 client01 PDC01 and PDC02 are domain controllers, and have identical smb.confs. client01 is a client, has WINS servers set to PDC01 and PDC02. users / passwords are replicated using LDAP. Now, under normal

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.

Hi, I used Samba 4.0.5 in Wheezy. Here is that I have done: --------------------------------------------------------------- samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI \ --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123' echo "nameserver 192.168.0.21" > /etc/resolv.conf samba ln -s /usr/local/samba/lib/libnss_winbind.so

I'm testing a samba4 server join AD (had 1 win2003 dc) as dc. Version: Samba4 DC: samba 4.1.1 with ubuntu (172.16.3.8) Win2003 DC: Win2003 SP2 (172.16.3.3) AD domain name: dotest.com The samba server had joined to AD as DC. When win2003 dc online, it seems works fine. When I test win2003 dc online, simulate the win2003 DC was failue, found the samba4 DC can't work fine along. The AD

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

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

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 Samba team ! I'am in a very delicate situation. After an upgrade to debian Stretch my DRS stopped working. I have three DCs (fichdc, fichds01, fichds02), all Debian Stretch, all with the same problem. Everything seems to be fine except DRS. -> File shares works -> DNS (with bind9 DLZ) works -> "kinit administrator" works -> "kinit -k FICHDC$" works ->

On Tue, 20 Jun 2017 22:31:02 +1200 Andrew Bartlett via samba <samba at lists.samba.org> wrote: > On Tue, 2017-06-20 at 11:13 +0200, L.P.H. van Belle via samba wrote: > > Now choose, of > > dedicated keytab file = /etc/krb5.keytab > > To be clear, this parameter is not used in the AD DC. > > Thanks, > > Andrew Bartlett > Shouldn't that be

Thank you very much Louis, Rowland, Mike ! I have made all the changes proposed by Louis but still have the same problem. -> kinit works now with /var/lib/samba/private/secrets.keytab ------------------------ ~# kinit -k -t /var/lib/samba/private/secrets.keytab FICHDC$ ~# ------------------------ -> but samba-tool authentication with machine account fail : ------------------------ ~#

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