No subject

=CRASH REPORT==== 14-Dec-2012::09:48:57 ===
  crasher:
    initial call: mochiweb_acceptor:init/3
    pid: <0.9433.1>
    registered_name: []
    exception exit: {error,accept_failed}
      in function  mochiweb_acceptor:init/3
    ancestors: [rabbit_mochiweb_web_mgmt,rabbit_mochiweb_sup,<0.140.0>]
    messages: []
    links: [<0.283.0>]
    dictionary: []
    trap_exit: false
    status: running
    heap_size: 987
    stack_size: 24
    reductions: 728
  neighbours:

When using curl (on the loadbalancer) with the same cipher list
(verified with tcpdump) it succeeds.

This is the TLSv1 communication:
> Client Hello
< Server Hello
> Finished
> Alert (Level: Fatal, Description: Unexpected Message)

This is the rabbitmq.config:

  {rabbitmq_mochiweb, [
      {listeners, [
          {mgmt, [
              {port, 443},
              {ssl, true},
              {ssl_opts, [
                  {cacertfile,"/local/secret/ssl/comodo-chain-2009.pem"},
                  {certfile,"/local/secret/ssl/esb-test.it.su.se.pem"},
                  {keyfile,"/local/secret/ssl/esb-test.it.su.se.key"},
                  {verify,verify_none}
                ]
              }
            ]
          }
        ]
      }
    ]
  },

I've added ssl_opts just to make sure that it was using it, before we
didn't have it since it will automatically inherit those settings from
our rabbit config.

We currently use the LB to Apache-servers so we know it should work.

If you need, you can get pcaps on demand.

The RabbitMQ machine runs on Ubuntu 10.04.4 LTS and uses Erlang R13B03
(ancient, I know).

Thanks and have a great weekend!
- Simon

---

Simon Lundström
IT Services
Stockholm University