RabbitMQ message broker unable to open unused port 61613

Posted by mjn on Server Fault See other posts from Server Fault or by mjn
Published on 2013-06-29T10:20:42Z Indexed on 2013/06/29 10:22 UTC
Read the original article Hit count: 291

Filed under:
|
|
|

On a Windows Vista system, RabbitMQ fails to open port 61613 which is not used (as netstat and TCPView show). The server log indicates that it is possible to bind port 5672, but the next lines show the problem with port 61613.

I have cleared all firewall settings and rebooted. Several times in the past this helped to solve the problem. But as the problem frequently reappears, I would like to know if there is somthing I am missing to solve its root cause.

=INFO REPORT==== 29-Jun-2013::12:09:16 ===
started TCP Listener on [::]:5672

=INFO REPORT==== 29-Jun-2013::12:09:16 ===
started TCP Listener on 0.0.0.0:5672

=INFO REPORT==== 29-Jun-2013::12:09:16 ===
rabbit_stomp: default user 'guest' enabled

=INFO REPORT==== 29-Jun-2013::12:09:16 ===
started STOMP TCP Listener on [::]:61613

=ERROR REPORT==== 29-Jun-2013::12:09:16 ===
failed to start STOMP TCP Listener on 0.0.0.0:61613 - eacces (permission denied)

=INFO REPORT==== 29-Jun-2013::12:09:16 ===
stopped STOMP TCP Listener on [::]:61613

© Server Fault or respective owner

Related posts about port

Related posts about tcp