you can upgrade from 4.7 to 4.9. but you must run samba-tool dbcheck that should work also. after the check run samba-tool dbcheck --reindex Main difference, a few depends and there versions. debian has tracker 1.0, ubuntu tracker 2.0 for example. Greetz Louis Op 30 mrt. 2019, om 16:20, Viktor Trojanovic <viktor at troja.ch> schreef: Thanks Louis, appreciate it! The main reason I'm aching to get my hands on it is because of the broken upgrade path between 4.7.4 (Bionic default) and 4.9.4 (currently only version for Bionic in your repo). Just out of curiosity, what is the major difference between the versions for Stretch and those for Bionic? - Viktor On Sat, 30 Mar 2019 at 10:13, L.P.H. van Belle <belle at bazuin.nl> wrote: 4.10 is not yet in the repo. almost.. im preparing for it. i think next week. Greetz, Louis Op 29 mrt. 2019, om 21:28, Viktor Trojanovic <viktor at troja.ch> schreef: Hi Louis, I see that you already offer 4.10 in your repo for Stretch. Would be great if you could make it available for Bionic, too. Thanks. - Viktor
On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl> wrote:> > you can upgrade from 4.7 to 4.9. > but you must run samba-tool dbcheck > that should work also. after the check run samba-tool dbcheck --reindex >I thought that maybe indeed I did something wrong the last time so I followed your advice. Unfortunately, it broke my DC again. (Luckily, I made a snapshot before doing this so I should be able to easily revert). So I went through with the update from 4.7.4 to 4.9.4, and after the update I ran: # samba-tool dbcheck Checking 322 objects Checked 322 objects (0 errors) # samba-tool dbcheck --reindex Re-indexing completed re-index OK # ldbedit -H /var/lib/samba/private/sam.ldb (shows contents of sam.ldb, closing the file) # 0 adds 0 modifies 0 deletes # reboot # journalctl -xe Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: /usr/sbin/samba_dnsupdate: ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 11:43:52.021002, 0] ../lib/util/ util_runcmd.c:327(samba_runcmd_io_handler) Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: /usr/sbin/samba_dnsupdate: File "/usr/lib /python2.7/dist-packages/samba/netcmd/__init__.py", line 177, in _run Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 11:43:52.021202, 0] ../lib/util/ util_runcmd.c:327(samba_runcmd_io_handler) Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: /usr/sbin/samba_dnsupdate: return self. run(*args, **kwargs) Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 11:43:52.021375, 0] ../lib/util/ util_runcmd.c:327(samba_runcmd_io_handler) Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: /usr/sbin/samba_dnsupdate: File "/usr/lib /python2.7/dist-packages/samba/netcmd/dns.py", line 945, in run Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 11:43:52.021539, 0] ../lib/util/ util_runcmd.c:327(samba_runcmd_io_handler) Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: /usr/sbin/samba_dnsupdate: raise e Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 11:43:52.047043, 0] ../source4/d sdb/dns/dns_update.c:330(dnsupdate_nameupdate_done) Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: ../source4/dsdb/dns/dns_update.c:330: Faile d DNS update - with error code 26 Does anyone have an idea what causes these errors? - Viktor
On Sun, 31 Mar 2019 13:55:18 +0200 Viktor Trojanovic via samba <samba at lists.samba.org> wrote:> On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl> > wrote: > > > > you can upgrade from 4.7 to 4.9. > > but you must run samba-tool dbcheck > > that should work also. after the check run samba-tool dbcheck > > --reindex > > I thought that maybe indeed I did something wrong the last time so I > followed your advice. Unfortunately, it broke my DC again. (Luckily, I > made a snapshot before doing this so I should be able to easily > revert). > > So I went through with the update from 4.7.4 to 4.9.4, and after the > update I ran: > > # samba-tool dbcheck > Checking 322 objects > Checked 322 objects (0 errors) > > # samba-tool dbcheck --reindex > Re-indexing > completed re-index OK > > # ldbedit -H /var/lib/samba/private/sam.ldb > (shows contents of sam.ldb, closing the file) > # 0 adds 0 modifies 0 deletes > > # reboot > > # journalctl -xe > > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: > /usr/sbin/samba_dnsupdate: ERROR(runtime): > uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 > 11:43:52.021002, 0] ../lib/util/ > util_runcmd.c:327(samba_runcmd_io_handler) > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: > /usr/sbin/samba_dnsupdate: File "/usr/lib > /python2.7/dist-packages/samba/netcmd/__init__.py", line 177, in _run > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 > 11:43:52.021202, 0] ../lib/util/ > util_runcmd.c:327(samba_runcmd_io_handler) > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: > /usr/sbin/samba_dnsupdate: return self. > run(*args, **kwargs) > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 > 11:43:52.021375, 0] ../lib/util/ > util_runcmd.c:327(samba_runcmd_io_handler) > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: > /usr/sbin/samba_dnsupdate: File "/usr/lib > /python2.7/dist-packages/samba/netcmd/dns.py", line 945, in run > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 > 11:43:52.021539, 0] ../lib/util/ > util_runcmd.c:327(samba_runcmd_io_handler) > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: > /usr/sbin/samba_dnsupdate: raise e > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: [2019/03/31 > 11:43:52.047043, 0] ../source4/d > sdb/dns/dns_update.c:330(dnsupdate_nameupdate_done) > Mar 31 11:43:52 dc1 samba[224]: task[dnsupdate][224]: > ../source4/dsdb/dns/dns_update.c:330: Faile > d DNS update - with error code 26 > > Does anyone have an idea what causes these errors? > > - Viktor >Yes, it appears that the change to the GUID index mode that first appeared in 4.8.0 is the culprit. I don't think anybody really knows why it fails, but it is believed to be that 4.9.x thinks the GUID index mode is being used, but the database is still the 4.7.x type. There have been a few workarounds suggested, but, to my knowledge, the only real upgrade path is to 'walk' up the versions. From 4.7.x upgrade to 4.8.x, run this so the database is changed to the GUID index mode and then upgrade to 4.9.x or higher. Rowland