Problem: stunnel doesn't run:
ldq@ldq:~$ stunnel4 /etc/stunnel.cnf ldq@ldq:~$ ps aux | grep stunnel ldq 15683 0.0 0.0 2332 1392 pts/0 S+ 11:08 0:00 man stunnel ldq 25289 0.0 0.0 1776 608 pts/1 S+ 11:59 0:00 grep stunnel
stunnel.cnf: ldq@ldq:~$ cat /etc/stunnel.cnf client = yes debug = debug
[nntps] accept = 127.0.0.1:1109 connect = news.giganews.com:443
Version: stunnel 4.140-5ubuntu1 libc6
ldq@ldq:~$ uname -a Linux ldq 2.6.18.5 SMP Thu May 8 01:31:23 UTC 2008 x86_64 GNU/Linux
On Fri, Jul 18, 2008 at 12:00:17PM -0400, Luis L?pez de Quintana wrote:
Problem: stunnel doesn't run:
ldq@ldq:~$ stunnel4 /etc/stunnel.cnf ldq@ldq:~$ ps aux | grep stunnel ldq 15683 0.0 0.0 2332 1392 pts/0 S+ 11:08 0:00 man stunnel ldq 25289 0.0 0.0 1776 608 pts/1 S+ 11:59 0:00 grep stunnel
Okay, so it's not running; but has it logged any error messages using the system's syslog? Is there anything stunnel-related in, say, /var/log/messages, /var/log/syslog, /var/log/daemon.log or anything similar?
stunnel.cnf: ldq@ldq:~$ cat /etc/stunnel.cnf client = yes debug = debug
To keep stunnel's messages into a separate file, you might also add output = /var/log/stunnel.log and then you'll know for sure if it logs anything. Of course, it will need permission to write to that file - it seems to me that you might be trying to run stunnel as a non-root user, nothing wrong with that, but then it might not be able to read its certificates and stuff.
For debugging purposes, try something like:
debug = debug foreground = yes
For normal use, try this instead:
debug = debug output = /home/your-username/stunnel.log
[nntps] accept = 127.0.0.1:1109 connect = news.giganews.com:443
This section looks fine. Now the most probable cause - IF you are running stunnel as a non-root user - would be that it is looking for its certificates in, say, /etc/stunnel.conf or something, and you do not have permission to read that file.
No matter if you are running it as root or not, try running it with foreground = yes so it does not daemonize and it sends all its output to the standard error stream where you can see it.
Version: stunnel 4.140-5ubuntu1 libc6
ldq@ldq:~$ uname -a Linux ldq 2.6.18.5 SMP Thu May 8 01:31:23 UTC 2008 x86_64 GNU/Linux
G'luck, Peter
On Mon, Jul 21, 2008 at 11:33:43AM +0300, Peter Pentchev wrote:
On Fri, Jul 18, 2008 at 12:00:17PM -0400, Luis L?pez de Quintana wrote:
Problem: stunnel doesn't run:
ldq@ldq:~$ stunnel4 /etc/stunnel.cnf ldq@ldq:~$ ps aux | grep stunnel ldq 15683 0.0 0.0 2332 1392 pts/0 S+ 11:08 0:00 man stunnel ldq 25289 0.0 0.0 1776 608 pts/1 S+ 11:59 0:00 grep stunnel
Okay, so it's not running; but has it logged any error messages using the system's syslog? Is there anything stunnel-related in, say, /var/log/messages, /var/log/syslog, /var/log/daemon.log or anything similar?
[snip more of my explanations and guesses]
No matter if you are running it as root or not, try running it with foreground = yes so it does not daemonize and it sends all its output to the standard error stream where you can see it.
Oops, sorry for the "PHISH" tag in the subject of my previous message; it seems our MailScanner thought that 127.0.0.1:443 was a malicious link :)
G'luck, Peter