search for: samba_spnupdate

...daemon died with exit status 1 [2018/05/29 10:54:01.635491, 0] ../source4/smbd/service_task.c:36(task_server_terminate) task_server_terminate: task_server_terminate: [winbindd child process exited] [2018/05/29 10:54:01.732553, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) /usr/sbin/samba_spnupdate: Processing section "[netlogon]" [2018/05/29 10:54:01.732736, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) /usr/sbin/samba_spnupdate: Processing section "[sysvol]" [2018/05/29 10:54:01.732769, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) /usr/sbin/s...

Hi, It's my first try to setup RODC using Samba 4.8. We have latest Samba 4.7 environnement with 2 DC and some file servers. Joining the DC to the domain is OK using samba-tool domain join command. The domain controller appears in the DC list (MMC) However, users cannot be authenticated. Samba is running but these ports are closed : netbios-ssn 139/tcp # NETBIOS session service

...the log.samba file I see the following messages: [2013/06/23 21:30:44, 0] ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) /usr/bin/samba_dnsupdate: Failed to exec child - No such file or directory [2013/06/23 21:30:44, 0] ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) /usr/bin/samba_spnupdate: Failed to exec child - No such file or directory Also I can confirm that the DNS is not updating. If try to execute manually the dns update (samba_dnsupdate --verbose --all-names ) I get: -bash: /usr/bin/samba_dnsupdate: /usr/bin/python2#: bad interpreter: No such file or directory Any ideas ab...

Hello All, Anyone have seen this before? Did samba_spnupdate really caused the crash??? [ 49.753564] block drbd1: drbd_sync_handshake: [ 49.753571] block drbd1: self BB16E125AF60AEDC:0000000000000000:30D97136FB1DA7A3:30D87136FB1DA7A3 bits:0 flags:0 [ 49.753576] block drbd1: peer 6365B5AFF049F16D:BB16E125AF60AEDD:30D97136FB1DA7A2:30D87136FB1DA7A3 bits...

...cache) Mar 23 13:46:50 orion2 winbindd[7485]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2 Mar 23 13:46:50 orion2 samba[7479]: [2018/03/23 13:46:50.798737,  0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) Mar 23 13:46:50 orion2 samba[7479]:   /usr/sbin/samba_spnupdate: Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs Mar 23 13:46:50 orion2 samba[7479]: [2018/03/23 13:46:50.799042,  0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) Mar 23 13:46:50 orion2 samba[7479]:   /usr/sbin/samba_spnupdate: Mar 23 13:46:50...

...50 orion2 winbindd[7485]:   initialize_winbindd_cache: > clearing cache and re-creating with version number 2 > Mar 23 13:46:50 orion2 samba[7479]: [2018/03/23 13:46:50.798737,  0] > ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) > Mar 23 13:46:50 orion2 samba[7479]:   /usr/sbin/samba_spnupdate: > Unable to determine the DomainSID, can not enforce uniqueness > constraint on local domainSIDs > Mar 23 13:46:50 orion2 samba[7479]: [2018/03/23 13:46:50.799042,  0] > ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) > Mar 23 13:46:50 orion2 samba[7479]:   /usr/sbin/samba_sp...

On 3/16/2018 10:07 AM, barış tombul via samba wrote: > same problem. > Never pass the 4.8 version. > > samba-tool dbcheck --cross-ncs --fix > Unable to determine the DomainSID, can not enforce uniqueness constraint on > local domainSIDs > > Searching for dsServiceName in rootDSE failed: operations error at > ../source4/dsdb/samdb/ldb_modules/rootdse.c:516 > Failed

...d' process model [2015/12/31 13:22:48.358595, 0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'samba' finished starting up and ready to serve connections [2015/12/31 13:22:50.709103, 0] ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) /usr/local/samba/sbin/samba_spnupdate: ldb: unable to dlopen /usr/local/samba/lib/ldb/dns_notify.so : /usr/local/samba/lib/private/liberrors-samba4.so: version `SAMBA_4.3.0' not found (require d by /usr/local/samba/lib/ldb/dns_notify.so) [2015/12/31 13:22:51.022158, 0] ../lib/util/util_runcmd.c...

..., eg > the A record for the domain only exists for the initial server, not > the newly joined one. The same with all the SRV records. I am going to fix this in the wiki, after you join a new DC, you need to start and then restart Samba, this will then run 'samba_dnsupdate' & 'samba_spnupdate' > > So I issue this command to add them: > > samba_dnsupdate --verbose > > > > Is Bind9 running on both DCs at this point. > > Is everything working as expected ? > > Yes. > > > You now turn off the first DC > > You now seize all FSMO r...

...ump is handled by helper binary specified at /proc/sys/kernel/core_pattern Mar 19 11:32:10 dc-linux-09 samba: task[dnsupdate][12956]: [2018/03/19 11:32:10.369699,  0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) Mar 19 11:32:10 dc-linux-09 samba: task[dnsupdate][12956]: /opt/samba/sbin/samba_spnupdate: Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs Mar 19 11:32:10 dc-linux-09 samba: task[dnsupdate][12956]: [2018/03/19 11:32:10.374885,  0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) Mar 19 11:32:10 dc-linux-09 samba: task[dnsupdate][12956...

.../db1 > > TERMSRV/db1.mydom > > TERMSRV/db1.mydom.lan > > > > > > Samba is 4.7.8 and one DC with 4.8.3. > > > > I am fairly sure that 'TERMSRV' is coming from 'spn_update_list' and it > is trying to be added by 'samba_spnupdate'. > There is however a problem, this is the bottom of 'spn_update_list': > > # Only used on Terminal Server mode: > # TERMSRV/${HOSTNAME} > # TERMSRV/${NETBIOSNAME} > > As you can see, all the lines are commented out and should be ignored. > > Have you modi...

....mydom.lan > > > > > > > > > > > > Samba is 4.7.8 and one DC with 4.8.3. > > > > > > > > > > I am fairly sure that 'TERMSRV' is coming from 'spn_update_list' > > > and it is trying to be added by 'samba_spnupdate'. > > > There is however a problem, this is the bottom of 'spn_update_list': > > > > > > # Only used on Terminal Server mode: > > > # TERMSRV/${HOSTNAME} > > > # TERMSRV/${NETBIOSNAME} > > > > > > As you can see, all the l...

Hello, I've got some log entries like these on our DCs: Failed to modify SPNs on CN=db1,CN=Computers,DC=mydom,DC=lan: acl: spn validation failed for spn[TERMSRV/DB1.MYDOM] uac[0x1000] account[db1$] hostname[(null)] nbname[mydom] ntds[(null)] forest[mydom.lan] domain[mydom.lan] At first I thought it was about missing SPN entries, but adding these did not resolve the problem: # samba-tool

...tname=231cc777-1ab8-4b15-be6c-dcd218df48e9._msdcs.samba.domain.tld,abstract_syntax=e3514235-4b06-11d1-ab04-00c04fc2dcd2/0x00000004,localaddress=10.156.248.221] > NT_STATUS_INVALID_PARAMETER > > Digging a bit further there is no "servicePrincipalName" for last added DC. > Using samba_spnupdate on FSMO owner or on newly added DC has no effect. > > I'm about to create these servicePrincipalName by hand to see if it could > solve my little issue. > > Cheers, > > mathias > > > 2015-11-16 14:40 GMT+01:00 mathias dufresne <infractory at gmail.com>: >...

.../31 13:22:48.358595, 0] > ../lib/util/become_daemon.c:124(daemon_ready) > STATUS=daemon 'samba' finished starting up and ready to serve > connections > [2015/12/31 13:22:50.709103, 0] > ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) > /usr/local/samba/sbin/samba_spnupdate: ldb: unable to dlopen > /usr/local/samba/lib/ldb/dns_notify.so : > /usr/local/samba/lib/private/liberrors-samba4.so: version > `SAMBA_4.3.0' not found (require d by > /usr/local/samba/lib/ldb/dns_notify.so) > [2015/12/31 13:22:51.022158, 0]...

.../smbd.pid /var/log/upstart/smbd.log.1.gz nmbd /usr/local/samba/sbin/nmbd /usr/local/samba/share/man/man8/nmbd.8 /var/log/upstart/nmbd.log.1.gz samba /usr/local/samba/sbin/nmbd /usr/local/samba/sbin/samba /usr/local/samba/sbin/samba_dnsupdate /usr/local/samba/sbin/samba_kcc /usr/local/samba/sbin/samba_spnupdate /usr/local/samba/sbin/samba_upgradedns /usr/local/samba/sbin/smbd /usr/local/samba/sbin/winbind If I'm overlooking something obvious please let me know. JS On Wed, Mar 2, 2016 at 5:42 PM, Marc Muehlfeld <mmuehlfeld at samba.org> wrote: > Am 02.03.2016 um 18:52 schrieb IT Admin: &g...

...> > > > > > Samba is 4.7.8 and one DC with 4.8.3. > > > > > > > > > > > > > > > > I am fairly sure that 'TERMSRV' is coming from 'spn_update_list' > > > > > and it is trying to be added by 'samba_spnupdate'. > > > > > There is however a problem, this is the bottom of > > > > > 'spn_update_list': > > > > > > > > > > # Only used on Terminal Server mode: > > > > > # TERMSRV/${HOSTNAME} > > > > > # TERM...

...cord for the domain only exists for the initial server, not >> the newly joined one. The same with all the SRV records. > I am going to fix this in the wiki, after you join a new DC, you need > to start and then restart Samba, this will then run 'samba_dnsupdate' & > 'samba_spnupdate' Is samba_spnupdate the crux of this issue then? > >> So I issue this command to add them: >> >> samba_dnsupdate --verbose >> >> >>> Is Bind9 running on both DCs at this point. >>> Is everything working as expected ? >> Yes. >> &g...

...ba-technical for more real time support. > >Matthieu. I've restarted samba with log level 5, above is what i've see ( full log is to big ) sync appears to be doing fine, i think: /usr/local/samba/sbin/samba_dnsupdate: schema_fsmo_init: we are master: yes Child /usr/local/samba/sbin/samba_spnupdate exited with status 0 - Success Completed SPN update check OK Child /usr/local/samba/sbin/samba_dnsupdate exited with status 0 - Success Completed DNS update check OK and dreplsrv_notify: DsReplicaSync OK for c0f2d2cc-eab6-4704-9046-1b9566ed85e3._msdcs.samba4.casa if i understood right, my samba...

Hi all, I have 3 DCs running Samba 4.3.1 in the same domain. They seem to work quiet well with coherent databases on each of them. After rebuilding my RPM to include systemd units, I've joined a Samba 4.3.1 today, using --domain-critical-only. The join was successful, the replication was not. This DC has only 146 objects in the DB when it should have a bit less than 50000 objects. As I was