We have a legacy application using RabbitMQ 3.7.4(A really old version, I know it’s not supported) with Erlang/OTP 19.3 in Windows Server 2016.
Last week after windows updates, RabbitMQ stopped working and we get the following error:
Faulting application name: erl.exe, version: 0.0.0.0, time stamp: 0x58c85c74
Faulting module name: crypto.dll, version: 0.0.0.0, time stamp: 0x58c85f6b
Exception code: 0xc0000005
Fault offset: 0x0000000000017623
Faulting process id: 0x3af8
Faulting application start time: 0x01d9a9c66b055799
Faulting application path: C:\Program Files\Erlang\erts-8.3\bin\erl.exe
Faulting module path: C:\Program Files\Erlang\lib\crypto-3.7.3\priv\lib\crypto.dll
Report Id: 3d5651c3-feaa-41f2-9b29-e9b5e50c8f7c
Faulting package full name:
Faulting package-relative application ID:`
We tried reinstalling RabbtiMQ and even upgrading Erlang/OTPto 20.3 that is also supported by our RabbitMQ version, without success.
At the end, we found a post talking about similar issues and after installing a 32 bit version of Erlang/OTP(20.3), it started working again.
According to the post we found, it may be related to OpenSSL issues.
Someone knows what can be the issue and if it can be resolved without upgrading RabbitMQ and Erlang/OTP?