Stray `{ref, ok}` message can kill the writer process about rabbitmq-server HOT 9 CLOSED

@lukebakken should we simply ignore this message in the writer and try to log some context at debug level? I mean, the writer cannot do much about this message, and this may allow us to log relevant details about the sender.

from rabbitmq-server.

Don't worry about the release notes, we can leave it open

from rabbitmq-server.

This feels like a warning level sort of message, maybe?

from rabbitmq-server.

@lukebakken logging a warning works for me #9994.

Those who have a way to reproduce and are interested in digging in now have a place to add more logging and tracing.

from rabbitmq-server.

rabbit_writer interacts with

• A socket, which in Erlang is a source of messages
• A statistics timer, which uses a reference for identity
• It implements a few bits required by the sys module

I'd start with those three for most likely senders of these stray {ref(), ok} messages.

from rabbitmq-server.

I'm going to re-open this issue to devote some time (at some point) to figure out the root cause.

@michaelklishin will having this issue open affect release notes? I can open a new issue if so.

from rabbitmq-server.

I can't see any usages in Ra of {ref, ok} the closest I have is https://github.com/rabbitmq/ra/blob/ba3293a3ea29e6aa738726ba22e951f1ce8e7af4/src/ra_server_sup_sup.erl#L243
but that should be a proper reference() not the atom ref.

from rabbitmq-server.

@kjnilsson yes, the error in the logs shows an actual reference, not the atom ref

from rabbitmq-server.

I've closed this because as of #9991, we hope that the writer process does not die. If someone wants to investigate where these messages originate from, you are welcome to do it.

It's just that this specific issue, as it is worded right now, should be addressed.

from rabbitmq-server.