[erlang-bugs] TLS "unexpected message"
Kim Hansen
kimhrac@REDACTED
Wed Dec 14 10:20:45 CET 2016
We're running RabbitMQ 3.6.6 on top of Erlang 19.1.5 and we are seeing
these errors in the log:
=ERROR REPORT==== 13-Dec-2016::11:48:04 ===
SSL: {connection,{alert,2,20,{"tls_record.erl",229},undefined}}:
ssl_connection.erl:842:Fatal error: unexpected message
=WARNING REPORT==== 13-Dec-2016::11:48:04 ===
STOMP connection 10.20.30.40:57788 -> 172.17.0.2:15679 terminated with
reason {inet_error,
{tls_alert,
"unexpected message"}}, closing it
=ERROR REPORT==== 13-Dec-2016::11:48:04 ===
** Generic server <0.21658.12> terminating
** Last message in was {inet_async,
{sslsocket,
{gen_tcp,#Port<0.69369>,tls_connection,
<0.701.0>},
<0.21655.12>},
#Ref<0.0.15466499.144103>,
{error,{tls_alert,"unexpected message"}}}
** When Server state == {reader_state,
{sslsocket,
{gen_tcp,#Port<0.69369>,tls_connection,<0.701.0>},
<0.21655.12>},
"10.20.30.40:57788 -> 172.17.0.2:15679",
{resume,#Fun<rabbit_stomp_frame.0.111251938>},
{proc_state,"session-GSnfw7PxboMQVsaeobF8ug",
<0.22191.12>,<0.22169.12>,
{dict,2,16,16,8,80,48,
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]},
{{[[<<"T_0">>|
{subscription,
"/exchange/h2s.rsp/eur1.USERNAME",client,
false,"id='0'"}]],
[],[],[],[],[],[],[],[],[],[],[],[],
[[<<"T_1">>|
{subscription,
"/exchange/s2h.req/eur1.USERNAME.json.*.*",
client,false,"id='1'"}]],
[],[]}}},
"1.2",undefined,
{0,nil},
{stomp_configuration,<<"guest">>,<<"guest">>,false,
false,false},
{set,0,16,16,8,80,48,
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]},
{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],
[]}}},
{dict,0,16,16,8,80,48,
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]},
{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],
[]}}},
#Fun<rabbit_stomp_processor.5.66813395>,
{amqp_adapter_info,
{0,0,0,0,0,65535,44049,2},
15679,
{0,0,0,0,0,65535,22167,24922},
57788,<<"10.20.30.40:57788 -> 172.17.0.2:15679
">>,
{'STOMP',0},
[{channels,1},
{channel_max,1},
{frame_max,0},
{client_properties,
[{<<"product">>,longstr,<<"STOMP client">>}]},
{ssl,true},
{ssl_protocol,'tlsv1.2'},
{ssl_key_exchange,rsa},
{ssl_cipher,aes_128_cbc},
{ssl_hash,sha256}]},
#Fun<rabbit_stomp_reader.2.90015809>,none,
{0,0,0,0,0,65535,44049,2},
false},
running,false,true,
{state,fine,5000,#Ref<0.0.15466499.142857>},
undefined,<0.22169.12>,<0.21657.12>,
{<0.22196.12>,<0.22197.12>}}
** Reason for termination ==
** {inet_error,{tls_alert,"unexpected message"}}
and it looks like it might cause a memory leak because we also get a lot of
these:
=WARNING REPORT==== 13-Dec-2016::11:48:05 ===
STOMP detected missed client heartbeat(s) on connection 10.20.30.40:51836
-> 172.17.0.2:15679, closing it
We've asked Pivotal about the root cause of this and they tell us that it
is a TLS alert (from Erlang) that ceases all TCP traffic.
I'd like to know if we can provide you with more information about this?
tcpdump traces or the like? If yes, can you provide us with a tcpdump
command that include a pseudo source IP address or something and we are
more than happy to dig into this and provide some logs.
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20161214/bdae5365/attachment.htm>
More information about the erlang-bugs
mailing list