On Sun, 08 Apr 2018 13:34:52 +0200 Kris via samba <samba at lists.samba.org> wrote:> W dniu 2018-04-08 12:49, Rowland Penny via samba napisał(a): > > On Sun, 08 Apr 2018 12:31:26 +0200 > > Kris via samba <samba at lists.samba.org> wrote: > > > >> I should try this command sooner. Now I have made full backup and > >> something is missing: > >> > >> [root at dc ~]# cd /opt/samba-4.7.6/bin > >> [root at dc bin]# ./samba_upgradeprovision --realm=DOMAIN.NET.PL -U > >> Administrator > >> Traceback (most recent call last): > >> File "./samba_upgradeprovision", line 36, in <module> > >> import ldb > >> > >> I have the same output running the script from > >> /opt/samba-4.7.6/source4/scripting/bin/ directory. > >> OS is CentOS 6. Google returns nothing really special about it. > >> > >> Any hint? > >> > > > > Have you got python-ldb installed ? > > I think it is called pyldb on Centos. > > > > Rowland > > I do now. One step further, but now: > "Traceback (most recent call last): > File "./samba_upgradeprovision", line 37, in <module> > import samba > ImportError: No module named samba > > I hope it's the last problem... > > Regards, > Kris >AH, light dawns ;-) Your python doesn't know where all the python modules are, investigate on how to set 'PYTHONPATH' on Centos. Rowland
W dniu 2018-04-08 14:06, Rowland Penny via samba napisał(a):> On Sun, 08 Apr 2018 13:34:52 +0200 > Kris via samba <samba at lists.samba.org> wrote: > >> W dniu 2018-04-08 12:49, Rowland Penny via samba napisał(a): >> > On Sun, 08 Apr 2018 12:31:26 +0200 >> > Kris via samba <samba at lists.samba.org> wrote: >> > >> >> I should try this command sooner. Now I have made full backup and >> >> something is missing: >> >> >> >> [root at dc ~]# cd /opt/samba-4.7.6/bin >> >> [root at dc bin]# ./samba_upgradeprovision --realm=DOMAIN.NET.PL -U >> >> Administrator >> >> Traceback (most recent call last): >> >> File "./samba_upgradeprovision", line 36, in <module> >> >> import ldb >> >> >> >> I have the same output running the script from >> >> /opt/samba-4.7.6/source4/scripting/bin/ directory. >> >> OS is CentOS 6. Google returns nothing really special about it. >> >> >> >> Any hint? >> >> >> > >> > Have you got python-ldb installed ? >> > I think it is called pyldb on Centos. >> > >> > Rowland >> >> I do now. One step further, but now: >> "Traceback (most recent call last): >> File "./samba_upgradeprovision", line 37, in <module> >> import samba >> ImportError: No module named samba >> >> I hope it's the last problem... >> >> Regards, >> Kris >> > > AH, light dawns ;-) > > Your python doesn't know where all the python modules are, investigate > on how to set 'PYTHONPATH' on Centos. > > RowlandThat did the trick. Thank you. But unfortunately... [root at dc bin]# ./samba_upgradeprovision --realm=DOMAIN.NET.PL -U Administrator Found 5 domain controllers. For the moment upgradeprovision is not able to handle an upgrade on a domain with more than one DC. Please demote the other DC(s) before upgrading Sanity checks for the upgrade have failed. Check the messages and correct the errors before rerunning upgradeprovision Is there any other way to increase KVNO, or I should try with demote and rejoin the main DC (with FSMO roles transter)? Regards, Kris
On Sun, 08 Apr 2018 17:04:02 +0200 Kris via samba <samba at lists.samba.org> wrote:> > AH, light dawns ;-) > > > > Your python doesn't know where all the python modules are, > > investigate on how to set 'PYTHONPATH' on Centos. > > > > Rowland > > That did the trick. Thank you. > But unfortunately... > > [root at dc bin]# ./samba_upgradeprovision --realm=DOMAIN.NET.PL -U > Administrator > Found 5 domain controllers. For the moment upgradeprovision is not > able to handle an upgrade on a domain with more than one DC. Please > demote the other DC(s) before upgrading > Sanity checks for the upgrade have failed. Check the messages and > correct the errors before rerunning upgradeprovision > > Is there any other way to increase KVNO, or I should try with demote > and rejoin the main DC (with FSMO roles transter)? > > Regards, > Kris >Bit of a catch 22 situation here, You want to join a DC but cannot, but a potential fix wants you to remove most of the DCs but doesn't guarantee you will be able to re-join them :-( Sorry, but I have run out of ideas for the moment, let me think about it. Rowland