stunnel4 init script seems to incorrect check for "pid" in /etc/stunnel/*.conf

Bug #620157 reported by joe williams
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
stunnel4 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: stunnel4

stunnel wont start even though the config file includes the pid.

root@host:~# grep "^pid" /etc/stunnel/haproxy.conf|sed "s;.*= *;;"
/stunnel4.pid
root@host:~# /etc/init.d/stunnel4 start
Starting SSL tunnels: [Failed: /etc/stunnel/haproxy.conf]
You should check that you have specified the pid= in you configuration file

haproxy.conf:

; Certificate/key is needed in server mode and optional in client mode
cert = /etc/stunnel/file.crt
key = /etc/stunnel/file.key

; Protocol version (all, SSLv2, SSLv3, TLSv1)
sslVersion = all
options = NO_SSLv2

; Some security enhancements for UNIX systems - comment them out on Win32
chroot = /var/lib/stunnel4/
setuid = stunnel4
setgid = stunnel4
pid = /stunnel4.pid

; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1

; Service-level configuration

[https]
accept = 443
connect = localhost:80
TIMEOUTclose = 0

Revision history for this message
joe williams (joetify) wrote :

root@host:~# cat /etc/issue
Ubuntu 10.04 LTS \n \l

root@host:~# uname -a
Linux host 2.6.32-305-ec2 #9-Ubuntu SMP Thu Apr 15 08:05:38 UTC 2010 x86_64 GNU/Linux

Revision history for this message
joe williams (joetify) wrote :

This *seems* to only effect 64bit installations, I set things up on a 32bit machine exactly the same way without issue.

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

Other bug subscribers

Remote bug watches

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