Radiator Server Documentation — v10.34.2

Building a Diameter error answer failed

A Diameter request rejected by its connection was dropped because its error answer could not be built.

Emission

Log level: DEBUG

Per-request tracing: No

Promotion: WARN

Logged when Radiator rejects a request on an Open connection before routing, for example with 3002 (DIAMETER_UNABLE_TO_DELIVER) or 3004 (DIAMETER_TOO_BUSY) while the adjacency is busy or draining, with a malformed-request answer, or with a duplicate-identity rejection, but cannot build the answer with diameter_result_code. Typical causes are an AVP the answer must copy from the request, such as Session-Id, Proxy-Info, or the Failed-AVP evidence, that cannot be encoded again or makes the answer exceed the maximum message size, or the connection being withdrawn while the answer was built. The request is dropped without an answer and the connection stays open.

Check the attached error and compare the logged identifiers with the peer's request. Also check the event that logged the rejection itself.