Bug#744851: stunnel4: Error message on starting

[Nigel Horne]

On 15/04/2014 10:40, Peter Pentchev wrote:

On Tue, Apr 15, 2014 at 10:19:23AM -0400, Nigel Horne wrote:

OK, so now can you do the following for me?

1. Still, let's see the output of netstat -atpn | fgrep -e :2525

tcp        0      0 0.0.0.0:2525            0.0.0.0:* LISTEN
3123/stunnel4

2. Don't kill the running stunnel process yet, I'd like to check what's
    going on.

3. Show me the output of:
    ls /var/run/*.pid

[snip no stunnel.pid or stunnel4.pid in /var/run/]

    ls /var/run/stunnel/*.pid

ls: cannot access /var/run/stunnel/*.pid: No such file or directory

    ls /var/run/stunnel4/*.pid
    (it's okay if the second command gives back an error, I expect that;
    it's also kind of okay if the third one gives an error, but I'd still
    like to see that :))

ls: cannot access /var/run/stunnel4/*.pid: No such file or directory

OK, now this is a bit weird.  I'll have to check again with an older
version of stunnel, see how it manages its pid files.

What you should do now is stop the running stunnel process by killing it
directly:

   kill 3123

Then "service stunnel4 start" should properly start the new stunnel
process.

It did.

Thanks.

Regards,

-Nigel

I think I really will reintroduce the "pid file by default" and issue a
warning if the configuration files do not specify a pid file, so that it
can be removed again in a couple of versions.

G'luck,
Peter

smime.p7s
Description: S/MIME Cryptographic Signature