Latest Upgrade to (UCS version is 4.2-0 errata4) from (UCS version is 4.2-0 errata2) appears to fail....regardless of type of server, Master or Backup

ucs-4-2

#1

Latest Upgrade to (UCS version is 4.2-0 errata4) from (UCS version is 4.2-0 errata2) appears to fail…regardless of type of server, Master or Backup.

root@bebucsbdcsvrp1:~# univention-upgrade

Starting univention-upgrade. Current UCS version is 4.2-0 errata2

Checking for local repository: none
Checking for package updates: found

The following packages will be upgraded:
univention-errata-level,univention-management-console-module-setup,univention-system-setup,univention-web-js,univention-web-style

Do you want to continue [Y|n]? y

Starting package upgrade ERROR: update failed. Please check /var/log/univention/updater.log

root@bebucsbdcsvrp1:~#

But appears to actually be successful…when you try to re-run the update.

root@bebucsmdcsvrp1:~# univention-upgrade

Starting univention-upgrade. Current UCS version is 4.2-0 errata4

Checking for local repository: none
Checking for package updates: none
Checking for app updates: none
Checking for release updates: none

When upgrading our UCS Mail Server which is a member server there appears to be NO issues with the upgrade.

When upgrading our UCS Windows/Linux Fileservers which are also UCS Member Servers there appears

Checking the UCS domain join status on all nodes, everything appears OK.

root@bebucsmailsvrp1:~# univention-check-join-status
Joined successfully

Also running UCS Diagnostics, returns:

Warning: Package status corrupt

The package status of 1 packages is corrupt.
Login to the system as root via ssh and run the command “dpkg --configure -a” in order to correct the packages status.
More information about the cause can be gained by executing “dpkg --audit”.

I have held off running the above commands to possibly correct until someone confirms this is what should be done on these failed updates.


#2

At least we have to know wich package is corrupt, so a dpkg --audit is in order and would not hurt. Are there additional hints in the updater.log?


#3

The results on our Master Controller is…
root@bebucsmdcsvrp1:~# dpkg --audit
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure or the configure menu option in dselect:
univention-s4-connector UCS - Modules for sync UCS and Samba4 LDB directory

The results on our Backup Controller is…
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure or the configure menu option in dselect:
univention-s4-connector UCS - Modules for sync UCS and Samba4 LDB directory

I have updater logs, but I see no way to attach them here…so here is a from the Master’s updater.log…the backup updater logs is similar in output…
Starting univention-upgrade. Current UCS version is 4.2-0 errata2

Checking for package updates: found
Please rerun command without --check argument to install.

Starting univention-upgrade. Current UCS version is 4.2-0 errata2

Checking for package updates: found
Please rerun command without --check argument to install.

Starting univention-upgrade. Current UCS version is 4.2-0 errata2

Checking for package updates: found
Please rerun command without --check argument to install.

Starting univention-upgrade. Current UCS version is 4.2-0 errata2

Checking for package updates: found
Please rerun command without --check argument to install.

Starting univention-upgrade. Current UCS version is 4.2-0 errata2

Checking for local repository: none
Checking for package updates: found

The following packages will be upgraded:
univention-errata-level,univention-management-console-module-setup,univention-system-setup,univention-web-js,univention-web-style
Starting dist-update at Wed Apr 26 11:50:52 2017…
Starting package upgrade Reading package lists…
Building dependency tree…
Reading state information…
The following packages will be upgraded:
univention-errata-level univention-management-console-module-setup
univention-system-setup univention-web-js univention-web-style
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 15.4 MB of archives.
After this operation, 8,192 B of additional disk space will be used.
Get:1 https://updates.software-univention.de/4.2/maintained/component/ 4.2-0-errata/all/ univention-errata-level 4.2.0-4 [786 B]
Get:2 https://updates.software-univention.de/4.2/maintained/component/ 4.2-0-errata/all/ univention-management-console-module-setup 10.0.10-13A~4.2.0.201704131209 [744 kB]
Get:3 https://updates.software-univention.de/4.2/maintained/component/ 4.2-0-errata/all/ univention-system-setup 10.0.10-13A~4.2.0.201704131209 [133 kB]
Get:4 https://updates.software-univention.de/4.2/maintained/component/ 4.2-0-errata/all/ univention-web-js 1.0.42-10A~4.2.0.201704241500 [9,685 kB]
Get:5 https://updates.software-univention.de/4.2/maintained/component/ 4.2-0-errata/all/ univention-web-style 1.0.42-10A~4.2.0.201704241500 [4,886 kB]
Fetched 15.4 MB in 55s (280 kB/s)
(Reading database …
(Reading database … 5%
(Reading database … 10%
(Reading database … 15%
(Reading database … 20%
(Reading database … 25%
(Reading database … 30%
(Reading database … 35%
(Reading database … 40%
(Reading database … 45%
(Reading database … 50%
(Reading database … 55%
(Reading database … 60%
(Reading database … 65%
(Reading database … 70%
(Reading database … 75%
(Reading database … 80%
(Reading database … 85%
(Reading database … 90%
(Reading database … 95%
(Reading database … 100%
(Reading database … 138407 files and directories currently installed.)
Preparing to unpack …/univention-errata-level_4.2.0-4_all.deb …
Unpacking univention-errata-level (4.2.0-4) over (4.2.0-2) …
Preparing to unpack …/univention-management-console-module-setup_10.0.10-13A~4.2.0.201704131209_all.deb …
Unpacking univention-management-console-module-setup (10.0.10-13A~4.2.0.201704131209) over (10.0.10-12A~4.2.0.201703301431) …
Preparing to unpack …/univention-system-setup_10.0.10-13A~4.2.0.201704131209_all.deb …
Conf univention-system-setup disabled.
To activate the new configuration, you need to run:
service apache2 reload
Unpacking univention-system-setup (10.0.10-13A~4.2.0.201704131209) over (10.0.10-12A~4.2.0.201703301431) …
Preparing to unpack …/univention-web-js_1.0.42-10A~4.2.0.201704241500_all.deb …
Unpacking univention-web-js (1.0.42-10A~4.2.0.201704241500) over (1.0.42-8A~4.2.0.201703311030) …
Preparing to unpack …/univention-web-style_1.0.42-10A~4.2.0.201704241500_all.deb …
Unpacking univention-web-style (1.0.42-10A~4.2.0.201704241500) over (1.0.42-8A~4.2.0.201703311030) …
Processing triggers for python-support (1.0.15.18.201403132013) …
Processing triggers for univention-config (12.0.1-5A~4.2.0.201703151910) …
dpkg-query: no packages found matching ldapacl_66univention-appcenter_app.acl
Setting up univention-s4-connector (11.0.6-17A~4.2.0.201704131417) …
File: /etc/logrotate.d/univention-s4-connector
insserv: warning: script ‘K01univention-system-setup-boot’ missing LSB tags and overrides
insserv: warning: script ‘S99obmscheduler’ missing LSB tags and overrides
insserv: warning: script ‘S99obmaua’ missing LSB tags and overrides
insserv: warning: script ‘obmscheduler’ 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: warning: script ‘obmaua’ missing LSB tags and overrides
insserv: There is a loop at service obmscheduler if started
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Max recursions depth 99 reached
insserv: There is a loop between service plymouth and mountnfs if started
insserv: loop involving service mountnfs at depth 6
insserv: loop involving service nfs-common at depth 5
insserv: There is a loop between service plymouth and networking if started
insserv: loop involving service networking at depth 3
insserv: loop involving service procps at depth 2
insserv: There is a loop between service plymouth and mountnfs if started
insserv: There is a loop between service plymouth and mountall if started
insserv: loop involving service mountall at depth 5
insserv: loop involving service checkroot-bootclean at depth 4
insserv: loop involving service rpcbind at depth 8
insserv: loop involving service urandom at depth 6
insserv: There is a loop between service obmscheduler and mountdevsubfs if started
insserv: loop involving service mountdevsubfs at depth 2
insserv: loop involving service udev at depth 1
insserv: There is a loop between service plymouth and mountnfs-bootclean if started
insserv: loop involving service mountnfs-bootclean at depth 2
insserv: loop involving service mountall-bootclean at depth 1
insserv: loop involving service keymap at depth 3
insserv: loop involving service obmscheduler at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package univention-s4-connector (–configure):
subprocess installed post-installation script returned error exit status 1
Setting up univention-errata-level (4.2.0-4) …
Setting version/erratalevel
File: /etc/lsb-release
File: /etc/apt/apt.conf.d/55user_agent
Setting up univention-system-setup (10.0.10-13A~4.2.0.201704131209) …
File: /usr/share/univention-management-console/modules/setup-certificate.xml
File: /etc/logrotate.d/univention-system-setup
File: /etc/apache2/conf-available/univention-system-setup.conf
Enabling conf univention-system-setup.
To activate the new configuration, you need to run:
service apache2 reload
Setting up univention-management-console-module-setup (10.0.10-13A~4.2.0.201704131209) …
Allowing use of questionable username.
The system user `systemsetup’ already exists. Exiting.
loaded pickle file /var/cache/univention-management-console/acls/systemsetup
warning: rule setup/* already exists
warning: rule lib/server/* already exists
warning: rule sysinfo/* already exists
loaded pickle file /var/cache/univention-management-console/acls/root
warning: rule setup/* already exists
warning: rule lib/server/* already exists
warning: rule sysinfo/* already exists
Not updating umc/web/appliance/fast_setup_mode
Calling joinscript 35univention-management-console-module-setup.inst …
2017-04-26 11:52:07.572863875-06:00 (in joinscript_init)
Joinscript 35univention-management-console-module-setup.inst finished with exitcode 1
Setting up univention-web-js (1.0.42-10A~4.2.0.201704241500) …
File: /usr/share/univention-web/js/umc/hooks.json
File: /var/www/univention/languages.json
File: /etc/apache2/conf-available/univention-web.conf
Conf univention-web already enabled
Module expires already enabled
Not updating ucs/server/languages/en_US
Not updating ucs/server/languages/de_DE
Not updating ucs/server/languages/en_GB
Not updating ucs/server/languages/de_AT
Not updating ucs/server/languages/de_CH
Not updating umc/web/hooks/univention-web-js
Setting up univention-web-style (1.0.42-10A~4.2.0.201704241500) …
Processing triggers for python-support (1.0.15.18.201403132013) …
Errors were encountered while processing:
univention-s4-connector

Reading package lists… 0%

Reading package lists… 0%

Reading package lists… 5%

Reading package lists… Done

Building dependency tree… 0%

Building dependency tree… 0%

Building dependency tree… 50%

Building dependency tree… 50%

Building dependency tree

Reading state information… 0%

Reading state information… 0%

Reading state information… Done
E: Sub-process /usr/bin/dpkg returned an error code (1)
exitcode of apt-get dist-upgrade: 100
ERROR: update failed. Please check /var/log/univention/updater.log


#4

I am thinking to correct this I need to run…

dpkg --configure univention-s4-connector UCS

on both the master and backup, but would like to confirm this before I run it, as these are PRODUCTION systems.


#5

I would run the package correction via # dpkg --configure -a That should run the package configuration (and only for the s4 connector, since it is the only unconfigured system) - afterwards run # univention-run-join-scripts again to make sure the join status is okay.

Since you mentioned it:

but would like to confirm this before I run it, as these are PRODUCTION systems.

Please be advised, that the forum has no guaranteed solutions, since for us the view at the problem is not deep enough at the forums in contrast to a support-ticket where we could do remotesession or phone-calls.


#6

The command fails with the following output…

root@bebucsmdcsvrp1:~# dpkg --configure -a
Setting up univention-s4-connector (11.0.6-17A~4.2.0.201704131417) …
File: /etc/logrotate.d/univention-s4-connector
insserv: warning: script ‘K01univention-system-setup-boot’ missing LSB tags and overrides
insserv: warning: script ‘S99obmscheduler’ missing LSB tags and overrides
insserv: warning: script ‘S99obmaua’ missing LSB tags and overrides
insserv: warning: script ‘obmscheduler’ 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: warning: script ‘obmaua’ missing LSB tags and overrides
insserv: There is a loop at service obmscheduler if started
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all' which can not be true! insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Max recursions depth 99 reached
insserv: There is a loop between service plymouth and mountnfs if started
insserv: loop involving service mountnfs at depth 6
insserv: loop involving service nfs-common at depth 5
insserv: There is a loop between service plymouth and networking if started
insserv: loop involving service networking at depth 3
insserv: loop involving service procps at depth 2
insserv: There is a loop between service plymouth and mountnfs if started
insserv: There is a loop between service plymouth and mountall if started
insserv: loop involving service mountall at depth 5
insserv: loop involving service checkroot-bootclean at depth 4
insserv: loop involving service rpcbind at depth 8
insserv: loop involving service urandom at depth 6
insserv: There is a loop between service obmscheduler and mountdevsubfs if started
insserv: loop involving service mountdevsubfs at depth 2
insserv: loop involving service udev at depth 1
insserv: There is a loop between service plymouth and mountnfs-bootclean if started
insserv: loop involving service mountnfs-bootclean at depth 2
insserv: loop involving service mountall-bootclean at depth 1
insserv: loop involving service keymap at depth 3
insserv: loop involving service obmscheduler at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package univention-s4-connector (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
univention-s4-connector


#7

obmaua is our Cloud Backup agent…wondering if that is the problem?


#8

We can’t afford UCS support, plus we were informed there is no US support.


#9

It really looks that way.

insserv: There is a loop at service obmscheduler if started
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all’ which can not be true!
insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all’ which can not be true!
[…]
insserv: Starting obmscheduler depends on plymouth and therefore on system facility $all’ which can not be true!
insserv: Starting obmaua depends on plymouth and therefore on system facility$all’ which can not be true!
insserv: Max recursions depth 99 reached
insserv: There is a loop between service plymouth and mountnfs if started

Though unfortunatly I do not know “obmscheduler” or “obmaua” and cannot advise how you may fix this. Are you able to deactivate it in some way?


#10

I can try to uninstall, then upgrade and then reinstall, we really need to keep it as it backups up our UCS server with live data to the cloud.

Oddly this issue did not occur with our member servers, which also have OBM backup installed.


#11

Before i go and uninstall OBM I am going to open a case with OBM support.


#12

The reply from OBM support was…

“the response from the engineers is that Obm is not capable of blocking anything on a security level. It’s just a restful service.”

So it appears that our only option at this point is to uninstall OBM, attempt to repair with "dpkg --configure -a ", then run “univention-run-join-scripts” then attempt the update again to be sure nothing was missed, then reboot, and reinstall OBM again and run a backup to ensure all is well again.


#13

Hi Brian,

just wanted to let you know that the editor has a nice little “Upload” button for attachments, e.g. logfiles :slight_smile:

A new window will open that even allows drag & drop.

And the button next to it (the one with </>) helps to format code and console output. That way it’s easier to see what a user wrote and what is text or log from the system.

Regarding the actual problem: If I am not mistaken, insserv detects a loop dependency for the boot process. This is imho the most important message:

insserv: There is a loop at service obmscheduler if started

So, removing OBM or at least its init-scripts is definitely worth a try. Did you boot your system with the default entry in the GRUB boot menu or did you maybe switch to the second one (sysvinit)?
I guess(!) the OBM initscripts might not be LSB compliant which confuses insserv.

Best regards,
Michael Grandjean


#14

yes, that upload only accepts PDF, JPG or PNG not LOG extenstions.


#15

OBM Support came back with this to try BEFORE we attempt to remove OBM…

To resolve the problem, please add the LSB fields into the corresponding init script files to the top of the file. The following is an example of the change that is required for the OBM scheduler init script (e.g. /etc/init.d/obmscheduler):

“### BEGIN INIT INFO”

“### END INIT INFO”


#16

This has appeared to correct the issue…I think we are good, we are updating our internal WIKI on this issue.

Thanks everyone for the help!


#17

Sorry! :sweat: I wasn’t aware that the we still have this restriction. We are going to address this.

I’m glad to hear that :slight_smile:

Regards, Michael


#18

Hello @BrianBonnell,

just FYI: log and txt files are now allowed as upload file formats :slight_smile:

Regards, Michael