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

[pan@REDACTED]

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 you 
specify debugtype console? Does anything show up in the debug log or in 
the event viewer when the node crashes? Does the node really crash or is 
it only the connection that fails?

Cheers,
/Patrik

On Tue, 29 Mar 2011, Emile Joubert wrote:

> Hi,
>
> I'm unable to start the crypto module in an Erlang VM installed as a Windows 
> service, if that service has any stopaction or a debugtype specified.
>
> Here are the steps to reproduce:
>
>> erlsrv add test -st halt() -sn test@REDACTED
>> erlsrv start test
>> werl.exe -remsh test@REDACTED -sname tmp
>  (in the werl window)
> 1> crypto:start().
>
> When left long enough this leads to
>
> ** Node 'test@REDACTED' not responding **
> ** Removing (timedout) connection **
>
> Specifying a debugtype of new or reuse also leads to a timeout:
>
>> erlsrv add test -de new -sn test@REDACTED
>> erlsrv start test
>> werl.exe -remsh test@REDACTED -sname tmp
>  (in the werl window)
> 1> crypto:start().
>
> When the service is installed without a stopaction and without a debugtype 
> specified then the crypto module works fine:
>
>> erlsrv add test -sn test
>> erlsrv start test
>> werl.exe -remsh test@REDACTED -sname tmp
>  (in the werl window)
> 1> crypto:rand_bytes(1).
> <<"ë">>
>
> I've observed this behaviour on version R14B01 and R14B02 on Windows XP 
> 32bit. Is this a known issue and is there a better workaround than not 
> specifying stopaction or a debugtype ?
>
>
> Regards
>
> Emile
>
>
> _______________________________________________
> erlang-bugs mailing list
> erlang-bugs@REDACTED
> http://erlang.org/mailman/listinfo/erlang-bugs
>