[erlang-bugs] Re: crypto from windows service?

Emile Joubert emile@REDACTED
Tue Mar 29 19:05:53 CEST 2011


Hi Patrik,

On 29/03/11 15:08, pan@REDACTED wrote:
> Hi!
>
> I am unable to reproduce the problem, but a wild guess would be that the
> openssl libraries (dll's) get messed up in some way by the small
> differences in process creation when you connect the stdout/stdin to a
> pipe. Have you tried updating openssl on the machine? What happens if

I've been able to reproduce the same problem on a separate new 32bit 
Windows XP SP3 install with R14B02 and Win32 OpenSSL v0.9.8r Light.

> you specify debugtype console? Does anything show up in the debug log or

Setting -debugtype to console pops up a console when the service starts 
(which is inconvenient for a service under normal circumstances). 
Starting the crypto app from the popped up console or from a remotely 
attached node does work however. The problem in my report only occurs if 
debugtype is set to new or reuse, or if any stopaction is specified.

> in the event viewer when the node crashes? Does the node really crash or
> is it only the connection that fails?

Nothing useful appears in the OS event viewer after a crash. The node 
really crashes, not just the connection. It is impossible to establish 
new connections.



Regards

Emile



More information about the erlang-bugs mailing list