Hello,
we’ve got a Primary Directory Node which always shows the setup screen on access with HTTP (“Choose your domain settings”) or SSH (“This system is not completely configured yet.”). I’m not sure whether this happens since installation time or started some time later during/after some updates.
On the CLI I see
root@vm01:~# ucr search system/setup/boot apache2/startsite
apache2/startsite: univention/setup/?username=root
system/setup/boot/fields/blacklist: password locale
system/setup/boot/help: <empty>
system/setup/boot/installer: true
system/setup/boot/minimal_memory: <empty>
system/setup/boot/nssldaptimeout:
system/setup/boot/pages/blacklist: locale welcome network
system/setup/boot/select/role: true
system/setup/boot/start: true
root@vm01:~# dpkg -l univention-system-setup univention-system-setup-boot
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version Architektur Beschreibung
+++-============================-============-============-=============================================
ii univention-system-setup 13.0.10-5 all UCS System Setup tools
ii univention-system-setup-boot 13.0.10-5 all Starting univention-system-setup on next boot
But I also see
root@vm01:~# univention-check-join-status
Joined successfully
What should I do to fix this? Is it sufficient to remove the packages?
apt purge univention-system-setup univention-system-setup-boot
Thanks!