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

Emile Joubert <>
Wed Mar 30 13:35:12 CEST 2011

On 30/03/11 11:00, Patrik Nyblom wrote:
> Hi!
> You're absolutely right in that you should not use debugtype console for
> production, I was just trying to narrow down the problem. The fact that
> console works points to that something get's messed up for
> crypto/openssl when the stdout/stdin file descriptors get assigned to
> pipes/files...
> A few quest(ion)s:
> Do you get an erl_crash.dump somewhere when it crashes? Do you get nothing
> at all in the event viewer, or...?

There is no erl_crash.dump in sight. The event viewer contains nothing 
at the time of the crash. Subsequent attempts to stop the service lead 
to entries some time after the crash:

test: Using TerminateProcess to kill erlang.

> The actual debug log, does that contain anything?

The debuglog contains nothing beyond the opening banner:

Eshell V5.8.3  (abort with ^G)

> I've not used that particular OpenSSL version, could you try upgrading
> to the latest OpenSSL (and also install the redistributables needed)?
> Please also uninstall any other OpenSSL versions. WinXP and different
> DLL versions when running as a service is known to cause problems

I've been able to reproduce the bug using the "Win32 OpenSSL v1.0.0d 
Light" OpenSSL libraries instead of "Win32 OpenSSL v0.9.8r Light" on 2 
separate XP SP3 32bit machines. The problem manifests in an identical 
manner. One of the machines has Visual Studio installed, for which no 
redistributable is necessary and the other had the redistributable 

> unfortunately :( Also please instal the OpenSSL DLL's in the Windows
> directory when asked by the installer.

This was done in all cases.


I'd be interested to know what OS, Erlang and OpenSSL version you are 
using so that I can try that. I've not been able to reproduce the 
problem under Windows7. So far it appears to be XP-specific.



More information about the erlang-bugs mailing list