Hi

We've had the following issues during an update which was the same as reported here https://help.univention.com/t/ucs-4-2-0-stunnel-startet-nicht/5530

How to reproduce: 
* Upgrade a system with univention-saml installed from 4.1-4 latest errata to 4.2-0 or later (as of testing it was 4.2-2 errata 184)
* univention-saml runs as process and depends on the stunnel4 package, stunnel4 also ships its own init script that is actually not used but fails.
* Reboot the system and see stunnel4 service errrors

The issue is that at boot stunnel exits with signal 1 and thus systemd shows a failed service when in fact the required sockets are started through the univention-saml init script already.

The current workaround in order to have a clean boot of such a system, was to 'systemctl disable stunnel4'.

This allows a system administration to have less garbage error messages during reboots and doesn't need to spend to time to analyze an actual non-issue in terms a working univention-saml service.

Second I wanted to let you know that stunnel4 is still shipped from the 4.1 repository whether or not that is a major issues it shows that the package was not rebuild/updated for 4.2 specifically.

-- Mathieu Simon