[Samba] 4.9.x -> 4.10.x : any major things to consider?
Stefan G. Weichinger
lists at xunil.at
Tue Nov 26 19:29:26 UTC 2019
Am 25.11.19 um 16:07 schrieb Stefan G. Weichinger via samba:
> Am 25.11.19 um 11:49 schrieb L.P.H. van Belle via samba:
>> Hai Stefan,
>>
>> Yes, i do recommend the setup from 4.9 to 4.10 first.
>>
>> If you plan is to upgrade to buster.
>> 1) on stretch, update samba to 4.10
>> 2) Change apt sources do buster, * your now also able to add buster-samba411 of my repo.
>> 3) apt-get dist upgrade --autoremove --purge
>> And you able to upgrade to buster and samba 4.11.
>>
>> Do note, i should be possible to to it also from 4.9 to 4.11, but thats not what i've done.
>> I only advice what i also did in my network.
>>
>> And which order, that does not matter much, i mix that also, thats bit what you preffer.
Screwed up the DC2 now as well. Nice day.
Somehow I overlooked some "stretch" string below "sources.list.d", this
lead to rm-ing samba (and smb.conf etc) ...
Now I have that back up, but it seems I lost some tdb-files or so.
samba-ad-dc.service fails ...
Nov 26 20:24:42 adc2 samba[1033]: task[kccsrv][1033]:
task_server_terminate: task_server_terminate: [kccsrv: Failed to connect
to local samdb: WERR_DS_UNAVAILABLE
Nov 26 20:24:42 adc2 samba[1033]: task[kccsrv][1033]: ]
Nov 26 20:24:42 adc2 samba[1032]: task[ntp_signd][1032]: [2019/11/26
20:24:42.252243, 0]
../../source4/smbd/process_standard.c:84(sigterm_signal_handler)
Nov 26 20:24:42 adc2 samba[1032]: task[ntp_signd][1032]:
sigterm_signal_handler: Exiting pid 1032 on SIGTERM
Nov 26 20:24:42 adc2 samba[1037]: task[dns][1037]:
task_server_terminate: task_server_terminate: [Failed to obtain server
credentials, perhaps a standalone server?: NT_STATUS_CANT
Nov 26 20:24:42 adc2 samba[1037]: task[dns][1037]: ]
and it seems the cronjob with the samba4-backup didn't run on that machine.
I assume I have to start over: demote that DC2 etc
Should have left office when I could an hour ago.
More information about the samba
mailing list