The configuration files are :
pid = /var/stunnel.pid ;chroot = /var/lib/stunnel
setuid = nobody setgid = nobody foreground =yes
; Use it for client mode client = yes
; Service-level configuration
[pop3s] accept = 995 connect = 110
[imaps] accept = 993 connect = 143
[ssmtp] accept = 465 connect = 25
[mysqls] accept = 3307 connect = 192.168.1.6:3307
On 192.168.1.6 ---------------------- pid = /var/stunnel.pid
setuid =nobody setgid = nobody foreground = yes
client = no
; Service-level configuration
[pop3s] accept = 995 connect = 110
[imaps] accept = 993 connect = 143
[ssmtp] accept = 465 connect = 25
[mysqls] accept =3307 connect =3306
connecting like /usr/local/mysql/bin/mysql -h 127.0.0.1 -u root -p -P 3307 Enter password:
On entring password the following lines appear : ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 104
Subrata
----- Original Message ----- From: Brian Hatch [email protected] To: [email protected] Sent: Sun, 7 Oct 2007 10:02:17 +0530 (IST) Subject: Re: [stunnel-users] Stunnel on the same machine
Near 2007-10-05 22:17 +0530, [email protected] insisted:
After starting stunnel and connecting the mysql client/usr/local/mysql/bin/mysql -h 127.0.0.1 -u root -p the flow gets stuck at the Enter password prompt any suggestions how to proceed from there.
What do your stunnel configuration files look like?
Other problem: mysql client may decide to use a local domain socket when connecting to localhost, thwarting your attempts to go via Stunnel. You might want to 'strace mysql ...' and look for the connect() lines.