[Samba] accidentally upgraded DC to 4.17.3 ... didn't work
Stefan G. Weichinger
lists at xunil.at
Tue Nov 22 13:07:23 UTC 2022
Forgive my flooding, but I really search for a solution and would like
to avoid downgrading again.
Compared the ouput of
ps axf | egrep "samba|smbd|winbindd"
on both DCs. Yes, different samba-versions.
adc1, samba 4.16.6:
938 ? S 0:00 \_ samba: tfork waiter process(941)
941 ? S 0:04 | \_ samba: task[winbindd] pre-fork master
946 ? S 0:00 | \_ samba: tfork waiter process(950)
950 ? Ss 0:39 | \_ /usr/sbin/winbindd -D
--option=server role check:inhibit=yes --foreground
1125 ? S 0:03 | \_ winbindd: domain child
[ARBEITSGRUPPE]
1128 ? S 0:03 | \_ winbindd: idmap child
adc2, samba 4.17.3:
6203 ? S 0:00 \_ samba: tfork waiter process(6205)
6205 ? S 0:00 | \_ samba: task[winbindd] pre-fork master
6209 ? S 0:00 | \_ samba: tfork waiter process(6218)
6218 ? Ss 0:00 | \_ /usr/sbin/winbindd -D
--option=server role check:inhibit=yes --foreground
6229 ? S 0:00 | \_ winbindd: domain child
[ARBEITSGRUPPE]
here that "idmap child" process is missing.
Is that OK? good or bad?
So far I always checked stuff like "wbinfo -u" after upgrades and
interpreted a working output as "things went OK".
More information about the samba
mailing list