Request rejected because licensed maximum request count was reached

Logged when Radiator rejects an incoming protocol request after reaching the effective limit from the active licenses for that protocol.

The request limit applies independently to RADIUS, TACACS+, and configured HTTP servers in the Radiator process. When multiple active licenses include a protocol, the highest allowance applies; an unlimited entitlement makes that protocol unlimited. Management API, Management UI, and RadiatorDB operations do not consume the request allowances.

The protocol field identifies the exhausted server protocol. The processed_requests field shows the number of requests accepted for that protocol while a positive request limit has been active since Radiator started. The licensed_requests field shows its active limit. Restarting Radiator resets the processed request counts.

See Getting a Radiator License to obtain or install a testing or production license.