search for: dnsupdate_spnupdate_done

...I renamed the windows server after the join, and there was now matching DNS record then. And I see stuff like this: /var/log/samba# tail -f log.samba ../source4/dsdb/dns/dns_update.c:353: Failed SPN update - with error code 1 [2019/07/09 19:16:32.921798, 0] ../source4/dsdb/dns/dns_update.c:353(dnsupdate_spnupdate_done) ../source4/dsdb/dns/dns_update.c:353: Failed SPN update - with error code 1 thanks for any help here

...and > there was now matching DNS record then. > > And I see stuff like this: > > /var/log/samba# tail -f log.samba > ../source4/dsdb/dns/dns_update.c:353: Failed SPN update - with error > code 1 > [2019/07/09 19:16:32.921798, 0] > ../source4/dsdb/dns/dns_update.c:353(dnsupdate_spnupdate_done) > ../source4/dsdb/dns/dns_update.c:353: Failed SPN update - with error > code 1 rejoined the server and removed the DNS entry inbetween manually join worked ok, no DNS record after that more of this: Jul 10 08:16:36 pre01svdeb02 samba[25451]: task[dnsupdate][25451]: [2019/07/10 08:16:...

...56.634639, 0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT Aug 13 04:08:56 samba samba [8575]: [13/08/2015 04: 08: 56.933596, 0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done) Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_IO_TIMEOUT 2) the stations have the following problems: 2.1) many machines when they log say the time is wrong, then you have to restart the windows to get login. 2.2) I believe after upgradi...

...pdate.c:290: Failed DNS update - with error code 110 [2018/12/21 03:16:03.413186, 0] ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110 [2018/12/21 03:16:03.741426, 0] ../source4/dsdb/dns/dns_update.c:313(dnsupdate_spnupdate_done) ../source4/dsdb/dns/dns_update.c:313: Failed SPN update - with error code 110 [2018/12/21 03:26:03.562027, 0] ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110 [2018/12/21 03:26:03.831110, 0] ../sourc...

...ource4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) >> Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT >> Aug 13 04:08:56 samba samba [8575]: [13/08/2015 04: 08: 56.933596, 0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done) >> Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_IO_TIMEOUT >> >> 2) the stations have the following problems: >> >> 2.1) many machines when they log say the time is wrong, then you have to restart the window...

...> 4.8.x to 4.9.x > > Am 10.07.19 um 08:40 schrieb Stefan G. Weichinger via samba: > > > more of this: > > > > Jul 10 08:16:36 pre01svdeb02 samba[25451]: task[dnsupdate][25451]: > > [2019/07/10 08:16:36.662971, 0] > > ../source4/dsdb/dns/dns_update.c:353(dnsupdate_spnupdate_done) > > Jul 10 08:16:36 pre01svdeb02 samba[25451]: task[dnsupdate][25451]: > > ../source4/dsdb/dns/dns_update.c:353: Failed SPN update - > with error code 1 > > Jul 10 08:26:36 pre01svdeb02 samba[25451]: task[dnsupdate][25451]: > > [2019/07/10 08:26:36.544214, 0] > >...

...th error > code 110 > [2018/12/21 03:16:03.413186, 0] > ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) > ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error > code 110 > [2018/12/21 03:16:03.741426, 0] > ../source4/dsdb/dns/dns_update.c:313(dnsupdate_spnupdate_done) > ../source4/dsdb/dns/dns_update.c:313: Failed SPN update - with error > code 110 > [2018/12/21 03:26:03.562027, 0] > ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) > ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error > code 110 > [2018/...

...ource4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) >> Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT >> Aug 13 04:08:56 samba samba [8575]: [13/08/2015 04: 08: 56.933596, 0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done) >> Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_IO_TIMEOUT >> >> 2) the stations have the following problems: >> >> 2.1) many machines when they log say the time is wrong, then you have to restart the window...

I was too quick to send my previous email. It can't really be a problem of the package since I have, as mentioned, another system with the exact same setup and the exact same package versions and it all works there... On Sun, 23 Dec 2018 at 11:18, Viktor Trojanovic <viktor at troja.ch> wrote: > Yes, I tried running dbcheck (see first email), it showed 0 errors from > the start, I

...update_nameupdate_done)Jun 30 06:37:41 bubba-b3-two samba[3238]: task[dnsupdate][3238]: ../source4/dsdb/dns/dns_update.c:330: Failed DNS update - with error code 110Jun 30 06:37:41 bubba-b3-two samba[3238]: task[dnsupdate][3238]: [2020/06/30 06:37:41.231985, 0] ../source4/dsdb/dns/dns_update.c:353(dnsupdate_spnupdate_done)Jun 30 06:37:41 bubba-b3-two samba[3238]: task[dnsupdate][3238]: ../source4/dsdb/dns/dns_update.c:353: Failed SPN update - with error code 110* I guess this is normal, since samba cannot "update" the db.ads file, where we are master for. So, any ideas how I can combine this? So make DNS...

...dns_update.c:294(dnsupdate_nameupdate_done) >>>> Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT >>>> Aug 13 04:08:56 samba samba [8575]: [13/08/2015 04: 08: 56.933596, 0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done) >>>> Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_IO_TIMEOUT >>>> >>>> 2) the stations have the following problems: >>>> >>>> 2.1) many machines when they log say the time is wr...

...0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) > Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT > Aug 13 04:08:56 samba samba [8575]: [13/08/2015 04: 08: 56.933596, 0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done) > Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_IO_TIMEOUT > > 2) the stations have the following problems: > > 2.1) many machines when they log say the time is wrong, then you have to restart the windows to get login. > &...

...0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) > Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT > Aug 13 04:08:56 samba samba [8575]: [13/08/2015 04: 08: 56.933596, 0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done) > Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_IO_TIMEOUT > > 2) the stations have the following problems: > > 2.1) many machines when they log say the time is wrong, then you have to restart the windows to get login. > &...

I get problems with group policies not applied ... seems an older problem surfacing now. Before I debug at current level I consider upgrading the 2 DCs from 4.8.12 (Debian Stretch) to 4.9.9 Anything specific to consider here?

...uf, None) Rowland Penny explained that this could be ignored because Daniel Betschart joined a Windows DC, but I'm getting these errors on a Linux DC. I don't seem to have a real DNS update problem, because I have [2020/05/12 14:46:38.288004, 3] ../../source4/dsdb/dns/dns_update.c:111(dnsupdate_spnupdate_done) samba_runcmd_io_handler: Child /usr/sbin/samba_dnsupdate exited 0 [2020/05/12 14:46:38.410990, 3] ../../source4/dsdb/dns/dns_update.c:88(dnsupdate_nameupdate_done) Completed DNS update check OK in /var/log/samba/log.samba for the automatic updates. Still I would like to have the error ab...

...8:40 schrieb Stefan G. Weichinger via samba: > >> > >>> more of this: > >>> > >>> Jul 10 08:16:36 pre01svdeb02 samba[25451]: task[dnsupdate][25451]: > >>> [2019/07/10 08:16:36.662971, 0] > >>> ../source4/dsdb/dns/dns_update.c:353(dnsupdate_spnupdate_done) > >>> Jul 10 08:16:36 pre01svdeb02 samba[25451]: task[dnsupdate][25451]: > >>> ../source4/dsdb/dns/dns_update.c:353: Failed SPN update - > >> with error code 1 > >>> Jul 10 08:26:36 pre01svdeb02 samba[25451]: task[dnsupdate][25451]: > >>> [...

...86108, 3] ../source4/dsdb/dns/dns_update.c:340(dnsupdate_check_names) Calling DNS name update script [2015/04/28 17:29:48.989054, 3] ../source4/dsdb/dns/dns_update.c:355(dnsupdate_check_names) Calling SPN name update script [2015/04/28 17:29:49.505209, 3] ../source4/dsdb/dns/dns_update.c:325(dnsupdate_spnupdate_done) Completed SPN update check OK [2015/04/28 17:29:49.576183, 3] ../source4/dsdb/dns/dns_update.c:296(dnsupdate_nameupdate_done) Completed DNS update check OK 7. Kerberos -- I don't believe this is working yet and will need to RTFM to figure out how to chase it down. [root at a10 etc]# ls -...

...sdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) >>> Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT >>> Aug 13 04:08:56 samba samba [8575]: [13/08/2015 04: 08: 56.933596, 0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done) >>> Aug 13 04:08:56 samba samba [8575]: ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_IO_TIMEOUT >>> >>> 2) the stations have the following problems: >>> >>> 2.1) many machines when they log say the time is wrong, then you have to...

...pear every 10 minutes in the samba log files: [2014/08/27 20:00:13.783274, 0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT [2014/08/27 20:00:13.854986, 0] ../source4/dsdb/dns/dns_update.c:323(dnsupdate_spnupdate_done) ../source4/dsdb/dns/dns_update.c:323: Failed SPN update - NT_STATUS_IO_TIMEOUT It starts about 20 seconds after Samba starts up, and then 10 minute intervals thereafter. I ran the debug level 5 to see if it helped, but I don't see anything useful. These errors show up in between D...

Thanks, Rowland. I'll give it some thought. At this point, I may even go back to slackware or gentoo. It is a bit much learning all the new system tools (systemd, systemctl, firewalld, NetworkManager, etc.) while moving from a samba standalone configuration to AD/DC, DNS, Kerberos, all for the first time. I'm also considering calling Pantek.com - - - I've had some very good