[stunnel-users] syslog-ng over stunnel does not work for me

[Christoph Pleger]

Hello,

> I set up a server and a client machine to test the combination of
> stunnel and syslog-ng. I followed the instructions in the example at
> http://www.stunnel.org/examples/syslog-ng.html, but the log messages
> are not sent correcly. 
> 
> The log on the server says:
> 
> ****: syslog started
> ****: syslog connected from ###.###.###.###:51646
> ****: SSL state (accept): before/accept initialization
> ****: SSL_accept: 140B544E: error: 140B544E: SSL
> routines:SSL_GET_NEW_SESSION:ssl session id callback failed
> ****: syslog finished (-1 left)
> 
> The log on the client says:
> 
> ****: syslog started
> ****: syslog connected from 127.0.0.1:3524
> ****: FD 8 in non-blocking mode
> ****: syslog connecting ###.###.###.###:514
> ****: connect_wait: waiting 10 seconds
> ****: connect_wait: connected
> ****: Remote FD=8 initialized
> ****: SSL state (connect): before/accept initialization
> ****: SSL state (connect): SSLv3 write client hello A
> ****: SSL_connect: Peer suddenly disconnected
> ****: syslog finished (0 left)
> 
> Please help.

I found the reason for my problem: stunnel tries to read some random
bytes from /dev/urandom, but that device did not exist because I am
running stunnel in a virtual server (www.linux-vserver.org) and my
virtual server only had a very limited number of device nodes in /dev.

Regards
  Christoph