Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[stunnel-users] "connect_blocking"

4,533 views
Skip to first unread message

Maroon Brinks

unread,
Oct 19, 2011, 5:12:11 AM10/19/11
to
Hi Everyone,

I was hoping you could help. I cannot for the life of me get my program to
connect through stunnel to this ip address. It appears to connect to stunnel
just fine, however I constantly recieve: "connect_blocking" and I've found it
very very hard to find information on the internet about this error. Here is
the log output below followed by my configuration file:

####LOG####

2011.10.19 09:49:56 LOG7[28234:139956427736816]: local socket: FD=8 allocated
(non-blocking mode)
2011.10.19 09:49:56 LOG7[28234:139956427736816]: Service bgcssl accepted FD=8
from 127.0.0.1:58178
2011.10.19 09:49:56 LOG7[28234:139956427839760]: Service bgcssl started
2011.10.19 09:49:56 LOG7[28234:139956427839760]: Option TCP_NODELAY set on local
socket
2011.10.19 09:49:56 LOG5[28234:139956427839760]: Service bgcssl accepted
connection from 127.0.0.1:58178
2011.10.19 09:49:56 LOG7[28234:139956427839760]: remote socket: FD=9 allocated
(non-blocking mode)
2011.10.19 09:49:56 LOG6[28234:139956427839760]: connect_blocking: connecting
148.106.128.90:7631
2011.10.19 09:49:56 LOG7[28234:139956427839760]: connect_blocking: s_poll_wait
148.106.128.90:7631: waiting 10 seconds
2011.10.19 09:50:06 LOG3[28234:139956427839760]: connect_blocking: s_poll_wait
148.106.128.90:7631: TIMEOUTconnect exceeded
2011.10.19 09:50:06 LOG5[28234:139956427839760]: Connection reset: 0 bytes sent
to SSL, 0 bytes sent to socket
2011.10.19 09:50:06 LOG7[28234:139956427839760]: Service bgcssl finished (0
left)
2011.10.19 09:50:06 LOG7[28234:139956427839760]: str_stats: 0 block(s), 0 data
byte(s), 0 control byte(s)

####CONFIG FILE####

; stunnel.conf

pid = /home/stunnel/bin/stunnel.pid
;setuid = nobody
;setgid = nobody
foreground = yes

sslVersion = TLSv1
service = stunnel

client = yes
debug = 7
output = stunnel.log

[bgcssl]
client = yes
accept = 127.0.0.1:12347
connect = 148.106.128.90:7631

Any help would be greatly appreciated.

Regards,
Mark

_______________________________________________
stunnel-users mailing list
stunne...@stunnel.org
http://stunnel.mirt.net/mailman/listinfo/stunnel-users

Michal Trojnara

unread,
Oct 21, 2011, 11:44:15 AM10/21/11
to
Maroon Brinks wrote:
> I've found it very very hard to find information
> on the internet about this error.
[cut]
> 2011.10.19 09:49:56 LOG7[28234:139956427839760]: connect_blocking:
> s_poll_wait 148.106.128.90:7631: waiting 10 seconds
> 2011.10.19 09:50:06 LOG3[28234:139956427839760]: connect_blocking:
> s_poll_wait 148.106.128.90:7631: TIMEOUTconnect exceeded

"TIMEOUTconnect exceeded" means that 148.106.128.90:7631 is not
responding to SYN packets.

Most likely either:
- your remote host is down, or
- your network link is broken, or
- packets are dropped by a firewall.

Mike

arnaud...@gmail.com

unread,
Oct 4, 2012, 8:04:18 AM10/4/12
to
What if i'm without firewall, on the same lan, with an uplink, and with two hosts up.

:/usr/local/etc/stunnel # rsync -vazi rsync://ro...@10.32.5.51/Profile .

gives me :
2012.10.04 13:55:54 LOG6[464:4512]: connect_blocking: connecting ::1:873
2012.10.04 13:55:54 LOG7[464:4512]: connect_blocking: s_poll_wait ::1:873: waiting 10 seconds
2012.10.04 13:55:55 LOG3[464:4512]: connect_blocking: connect ::1:873: Connection refused (WSAECONNREFUSED) (10061)
2012.10.04 13:55:55 LOG6[464:4512]: connect_blocking: connecting 127.0.0.1:873
2012.10.04 13:55:55 LOG7[464:4512]: connect_blocking: s_poll_wait 127.0.0.1:873: waiting 10 seconds
2012.10.04 13:55:55 LOG7[464:5508]: Service [backuppc] accepted (FD=7692) from 127.0.0.1:12892
2012.10.04 13:55:55 LOG5[464:4512]: connect_blocking: connected 127.0.0.1:873
2012.10.04 13:55:55 LOG7[464:5508]: Creating a new thread

FYI my stunnel configuration is :
debug = 7
output = stunnel.log
fips = no
cert = stunnel.pem
[backuppc]
client = yes
accept = 0.0.0.0:873
connect = localhost:873

and rsync configuration is :
use chroot = false
max connections = 4
log file = c:/rsyncd/rsyncd.log
pid file = c:/rsyncd/rsyncd.pid
lock file = c:/rsyncd/rsyncd.lock
[docs]
path = c:/users
comment = Profile
strict modes = false
auth users = root
secrets file = c:/rsyncd/rsyncd.secrets

You may notice that the path is a hybrid of linux/windows style, I use rsyncd from the backupPC sourceforge
0 new messages