[rabbitmq-discuss] Feature Req / Bug list

Simon MacMullen simon at rabbitmq.com
Fri Nov 29 11:46:40 GMT 2013

On 26/11/2013 22:23, Graeme N wrote:
> Looking at the logs for instances which drop their network connections
> shows some pretty big erlang stack dumps, so I've compressed and
> uploaded a sample log file here for you:
> https://mega.co.nz/#!31JCGSxa!LdxuhXeX_HN_px8lnQcp63RkFcRY_dW9Z_x9C7qv2aE <https://mega.co.nz/#%2131JCGSxa%21LdxuhXeX_HN_px8lnQcp63RkFcRY_dW9Z_x9C7qv2aE>

The fundamental problem I see in that log is:

=ERROR REPORT==== 26-Nov-2013::22:20:19 ===
failed to start SSL Listener on [::]:5671 - eaddrinuse (address already 
in use)

Now that should just cause the server to stop - in fact it sounds like 
it stays up when synchronisation was occurring at the point it tried to 
open network listeners. So I'll look at that.

The big stacktraces that occur after that point are not ideal, but they 
are essentially noise; they all look like they're caused by 
synchronisation processes that are still running when most of the rest 
of the broker has stopped.

Cheers, Simon

More information about the rabbitmq-discuss mailing list