stunnel4 startup script ignores second configuration file

[Dr Grischa Meyer]

On Ubuntu 13.04
stunnel4 version 3:4.53-1

I have to *.conf files in /etc/stunnel/ but only one gets started by the init.d script.

Ie.:
$ sudo service stunnel4 start
Starting SSL tunnels: [Already running: /etc/stunnel/nfs.conf] [Already running: /etc/stunnel/redis.conf] stunnel.

However only one is running.

I can start the second one by running
$ sudo stunnel4 /etc/stunnel/redis.conf
and then it runs fine.

So the issue is somewhere in the init.d script.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Drew Mazurek (mazurek-4)]

I see the same issue with Ubuntu 14.04 LTS:

> ls /etc/stunnel/*.conf
/etc/stunnel/stunnel-1.conf /etc/stunnel/stunnel-2.conf
> sudo service stunnel4 start
Starting SSL tunnels: [Started: /etc/stunnel/stunnel-1.conf] [Already running: /etc/stunnel/stunnel-2.conf] stunnel.

[Jeff Goldschrafe (jgoldschrafe)]

Each stunnel instance needs its own pid= option in the configuration file in order for the init script to be able to differentiate between running processes. The messaging is confusing, but that aside, this is probably working as designed.