Problem: Services do not start after an Update 4.1 --> 4.2

ucs-4-1
ucs-4-2
systemd
update
services
problem

#1

Problem

After an update from UCS 4.1 to UCS 4.2 some services do not start automatically as expected in the configured runlevels.

Solution

Use systemctl to enable the SERVICE permanently and start it now:

systemctl enable SERVICE
systemctl start SERVICE

Root Cause

With UCS 4.1 to UCS 4.2 the Debian base changed from Debian 7 (“Wheezy”) to Debian 8 (“Jessie”) where systemd was introduced as replacement for SysVinit.

systemd does not use the concepts of runlevels any more. Instead it uses targets. During the update some services did not get fully migrated so they were in status disabled.


#2