hello Arnout,
Arnout Boelens wrote:
Instead of the default debian configuration file in /etc/stunnel4/, I made
another one with different name. However, this is causing installing stunnel4 to
fail during an upgrade. Temporaly moving the file out (resulting in an empty
/etc/stunnel4/ directory), makes it possible to complete the installation.
The error message I got was:
Setting up stunnel4 (4.150-6) ...
Stopping SSL tunnels: stunnel.
Starting SSL tunnels: invoke-rc.d: initscript stunnel4, action "start" failed.
dpkg: error processing stunnel4 (--configure):
subprocess post-installation script returned error exit status 1
In fact, I understood what's happened :
1) You had a running instance of stunnel4
2) You had made an upgrade
3) Upgrade calls /etc/init.d/stunnel4 stop -> but no configuration file
are found here. It does not stop your instance.
4) Upgrade calls invoke-rc.d stunnel4 start -> there is already an
instance loaded, so it failed
But, why "/etc/init.d/stunnel4 stop" did not found the configuration
file to stop instance. I see no reason, is your
/etc/default/stunnel4 file erased by the upgrade ?
Best Regards
Julien Lemoine
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
