stunnel4 should be run from rc?.d after wifi-radar, not before

[Daniel Bonniot de Ruisselet]

Binary package hint: stunnel4

Currently both stunnel4 and wifi-radar are run with priority S20, and bcause of alphabetic ordering, stunnel4 is run first. So when wifi-radar is neded to set up the network, stunnel simply doesn't work after boot and has to be restarted manually. I guess starting stunnel4 at S21 would do the trick.

The dependency in /etc/init.d/stunnel4 should also be updated to require wifi-radar (or rather networking in general, if that is possible).

[Daniel Bonniot de Ruisselet (bonniot-users)]

Actually, a higher number is probably needed for stunnel. The network setting happens partially in the background and is not ready when stunnel is running. I'll experiment.

Is there anything in the boot process that might rely on stunnel?

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10?

[Daniel Bonniot de Ruisselet (bonniot-users)]

Yes, it still happens in 8.10. Basically, if I connect to the wiki network setup in /etc/network/interfaces, then stunnel works. Otherwise (i.e. if wifi-radar or since 8.10 NetworkManager automatically finds another configured network), stunnel has to be restarted manually.

I realized currently stunnel is started in rc2.d (but too early, and that cannot be fixed because of background processes) and /etc/ppp/ip-up.d (but that only applies to ppp). Wouldn't it solve everything to restart stunnel in the same way, but in /etc/network/if-up.d ?

[BradB (bbeyenhof)]

I've been having this problem in 8.10 as well (I have stunnel set to run as a client so that an SSL-incapable email notifier can access an SSL IMAP server). However, even if I change stunnel's startup scripts to S95, it still doesn't work without a manual service restart.

I'm unsure how the stuff in /etc/network/ works... care to expound how I might be able to use that instead?

[Erwan Hamon (erwan-hamon)]

I reported a similar (same?) problem on Jaunty: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/368545

And an ugly workaround:
#cat /etc/crontab | grep stunnel
@reboot root /etc/init.d/stunnel4 restart

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for stunnel4 (Ubuntu) because there has been no activity for 60 days.]