[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2011-08-13 Thread Joey Imbasciano
This bug was reported in 2007, confirmed in 2008 and is still not fixed? I can confirm this is still affecting Ubuntu 8.04: ii stunnel4 3:4.21-1Universal SSL tunnel for network daemons Any plans to fix this? -- You received this bug notification because you are a member of Ubuntu

[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2010-10-16 Thread valkyr
On Maverick the same error occurs. It is however to do with the message before the one about the PID, complaining of the missing SSL certificate needed to run stunnel. A guide to certificates, and how to generate one can be found here : http://www.stunnel.org/faq/certs.html I guess a cert.

[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2009-09-29 Thread Peter
I got following error message at the startup of stunnel4 on karmic You should check that you have specified the pid= in you configuration file. I'm using stunnel for nntps (119/563). I checked port 119 and found, that cyrus is using port 119 too: netstat -tupan | grep ':::119' tcp6 0

[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2008-11-13 Thread Adrian Busolini
I too have had this problem for a while. Stunnel4 operates perfectly (apart from infrequent random 100% usages requiring killing) but the /etc/init.d/stunnel4 script reports those erroneous messages. I think, because of that (and hence returning a failure code), apt didn't think stunnel4 had

[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2008-10-19 Thread Daniel T Chen
Reproducible in 8.04.1 and current 8.10. ** Changed in: stunnel4 (Ubuntu) Importance: Undecided = Medium Status: New = Confirmed -- stunnel4 init.d script reports startup failures with pid=error message even when not so https://bugs.launchpad.net/bugs/137472 You received this bug

[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2008-02-11 Thread supernaicol
I've resolved my issue simply setting ENABLED=1 instead of ENABLED=0 in the file /etc/default/stunnel4. Tatiana, I still don't know if your case is affected by the same issue, but my problem now seems quite stupid. To be honest, it seems also quite stupid that file didn't enable the service,

[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2007-12-07 Thread supernaicol
I don't know if my case is related to yours, because I don't have the necessary skills to inspect the init.d script, but I cannot start stunnel4 with sudo /etc/init.d/stunnel4 start, so neither stunnel starts when i boot my workstation. Instead sudo stunnel4 works perfectly. Best regards --

[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2007-09-05 Thread Tatiana
$ dpkg -S /etc/init.d/stunnel4 stunnel4: /etc/init.d/stunnel4 $ dpkg -l|fgrep stunnel4 ii stunnel4 4.150-7 Universal SSL tunnel for network daemons -- stunnel4 init.d script reports startup failures with pid=error message even when not so

[Bug 137472] Re: stunnel4 init.d script reports startup failures with pid=error message even when not so

2007-09-05 Thread Tatiana
startdaemons() { if ! [ -d /var/run/stunnel4 ]; then rm -rf /var/run/stunnel4 install -d -o stunnel4 -g stunnel4 /var/run/stunnel4 fi for file in $FILES; do if test -f $file; then ARGS=$file $OPTIONS if $DAEMON $ARGS; then echo -n [Started: $file] else