[stunnel-users] Stunnel blocks booting process when no network connectivity

[Muschi Stevenson]

My stunnel implementation works fine when the network is plugged in
but it does not start at all, which stops the whole boot process, when
there is no network connected on the machine (as a client).

As extra information:

- I'm using "delay=yes"
- I'm using an fqdn (e.g: stunnel.mydomain.com) for the connections
- Using stunnel 4.53
- Using ubuntu 12.04 but this also happened with centos5 previously
however after some time it did boot on centos which doesn't happen in
ubuntu

How can this be avoided or a timeout specified?

Doing an strace as suggested by symcbean shows the following
(including the last part where it hangs):

[...]
--- SIGCHLD (Child exited) @ 0 (0) ---
rt_sigreturn(0x11)                      = 0
close(3)                                = 0
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 6039
clone(child_stack=0,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7ff9ce0c79d0) = 6046
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 6046
--- SIGCHLD (Child exited) @ 0 (0) ---
rt_sigreturn(0x11)                      = 6046
write(1, "[Started: /etc/stunnel/stunnel.c"..., 37) = 37
write(1, "stunnel.\n", 9)               = 9
exit_group(0)                           = ?
[...]

stunnel hangs in this line: wait4(-1,

and when i plug in the network cable it continues to show
[{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 6046

Any help would be appreciated as this is critically blocking our deployment

http://serverfault.com/questions/429072/stunnel-delaying-boot