Ubuntu
stunnel4 package

stunnel4 startup script ignores second configuration file

Bug #1237200 reported by Dr Grischa Meyer
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
stunnel4 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in stunnel4 (Ubuntu):
status: New → Confirmed
Revision history for this message
Drew Mazurek (mazurek-4) wrote :

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.

Revision history for this message
Jeff Goldschrafe (jgoldschrafe) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.