Seems cannot isntall or reinstall using univention-install or univention-remove
and cannot run univention-upgrade
I get this error
Upgraded to 4.1-5 last night.
Any help would be appreciated.
error log:
Nov 02 09:45:15 monitoring univention-management-console-web-server[6505]: BType = self.build_backend_type(ffi, finishlist)
Nov 02 09:45:15 monitoring univention-management-console-web-server[6505]: File "/usr/local/lib/python2.7/dist-packages/cffi/model.py", line 507, in build_backend_type
Nov 02 09:45:15 monitoring univention-management-console-web-server[6505]: base_btype = self.build_baseinttype(ffi, finishlist)
Nov 02 09:45:15 monitoring univention-management-console-web-server[6505]: File "/usr/local/lib/python2.7/dist-packages/cffi/model.py", line 525, in build_baseinttype
Nov 02 09:45:15 monitoring univention-management-console-web-server[6505]: % self._get_c_name())
Nov 02 09:45:15 monitoring univention-management-console-web-server[6505]: cffi.api.CDefError: 'point_conversion_form_t' has no values explicitly defined: refusing to guess which integer type ..., int/long)
Nov 02 09:45:15 monitoring univention-management-console-web-server[6505]: failed!
I think that while univention server is still on version 4.1-5, it has updated some packages to 4.2-0
cat /etc/apt/sources.list.d/00_ucs_update_in_progress.list
deb https://updates.software-univention.de/4.2/maintained/ 4.2-0/all/
deb https://updates.software-univention.de/4.2/maintained/ 4.2-0/amd64/
deb https://updates.software-univention.de/4.2/unmaintained/ 4.2-0/all/
deb https://updates.software-univention.de/4.2/unmaintained/ 4.2-0/amd64/
so maybe python-cffi is from version 4.2 and it is not working with the rest of the installed packages from version 4.1-5
Running preup.sh script
Fri 2 Nov 10:47:27 GMT 2018
HINT:
Please check the release notes carefully BEFORE updating to UCS 4.2-0:
English version: https://docs.software-univention.de/release-notes-4.2-0-en.html
German version: https://docs.software-univention.de/release-notes-4.2-0-de.html
Please also consider documents of following release updates and
3rd party components.
Do you want to continue [Y/n]?
Trying to detect if migration to dependency based boot will fail:
WARNING: Removed, but configured, package cgroupfs-mount left /etc/init.d/cgroupfs-mount behind
WARNING: Removed, but configured, package plymouth left /etc/init.d/plymouth behind
WARNING: Removed, but configured, package plymouth left /etc/init.d/plymouth-log behind
insserv: warning: script 'K01univention-system-setup-boot' missing LSB tags and overrides
insserv: warning: script 'univention-system-setup-boot-prepare' missing LSB tags and overrides
insserv: warning: script 'univention-system-setup-boot' missing LSB tags and overrides
insserv: remove service /etc/init.d/../rc0.d/K01urandom
insserv: enable service ../init.d/urandom -> /etc/init.d/../rc0.d/K02urandom
insserv: remove service /etc/init.d/../rc0.d/K02cgproxy
insserv: enable service ../init.d/cgproxy -> /etc/init.d/../rc0.d/K01cgproxy
insserv: remove service /etc/init.d/../rc1.d/K02cgproxy
insserv: enable service ../init.d/cgproxy -> /etc/init.d/../rc1.d/K01cgproxy
insserv: remove service /etc/init.d/../rc6.d/K01urandom
insserv: enable service ../init.d/urandom -> /etc/init.d/../rc6.d/K02urandom
insserv: remove service /etc/init.d/../rc6.d/K02cgproxy
insserv: enable service ../init.d/cgproxy -> /etc/init.d/../rc6.d/K01cgproxy
insserv: dryrun, not creating .depend.boot, .depend.start, and .depend.stop
insserv --dryrun: OK
Aborting, because the update would likely fail.
Please check and fix the aforementioned issues.
(To ignore, set the UCRV variable update42/ignore_insserv to yes)
Error: Update aborted by pre-update script of release 4.2-0
exitcode of univention-updater: 1
ERROR: update failed. Please check /var/log/univention/updater.log
For the last problem: purge all packages that are in state removed, configured
List all of those packages: dpkg -l | grep '^rc'
If nothing seems too unusual about them, purge them: dpkg -l | awk '/^rc/ { print $2 }' | xargs -r dpkg --purge
Background: old init scripts count as configuration files in the Debian package management, and configuration files aren’t removed automatically when you remove the corresponding package (e.g. via apt-get remove <packagename>). Such a package transits from state installed (ii in the first column of the dpkg -l output) to removed, configured (rc in the first column). Such init scripts are problematic during the switch to systemd, so you’ll have to fully purge those packages (and with that the init scripts).
Please move the init scripts that are reported with a warning to a backup location, e.g. under /root/, those are generally not required anymore, but they block the update. Then retry the update to UCS 4.2