Persistent Diameter adjacency is ineligible until configuration or peer state changes

Logged when an outbound adjacency fails for a reason that another connection attempt would repeat: the peer's capability exchange reports another identity or realm, rejects the connection, shares no application, requires in-band security on an unprotected TCP connection, or does not correlate, or the adjacency configuration is invalid. Radiator Server stops dialling the adjacency, and requests waiting for it fail with the logged reason, until the Diameter server configuration is reloaded or Radiator Server is restarted.

Correct the reported peer or adjacency configuration, or have the peer's operator correct the peer, then reload the Diameter server configuration.