Rejected Diameter request because the connection is draining

Logged when a peer sends an application request on a connection whose Diameter server is reloading or stopping, or when such a request was still waiting for policy processing when the drain started. Radiator answers the request at once with diameter_result_code: 3004 (DIAMETER_TOO_BUSY) when its Destination-Host names this local node and 3002 (DIAMETER_UNABLE_TO_DELIVER) otherwise, so the peer can send it to another peer. Requests already in policy processing still complete before the connection is disconnected.

No action; the event follows a configuration reload or server stop. If the peer reports failures for these requests, check that it retries 3002 and 3004 answers at another peer or after it reconnects.