Bug 42730 - Configured value of max_requests is too low
Configured value of max_requests is too low
Product: UCS
Classification: Unclassified
Component: Radius
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.2-0-errata
Assigned To: Janek Walkenhorst
Daniel Tröder
Depends on:
  Show dependency treegraph
Reported: 2016-10-21 12:34 CEST by Sönke Schwardt-Krummrich
Modified: 2017-06-15 17:58 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.091
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016101221000391
Bug group (optional):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2016-10-21 12:34:40 CEST
The configured value of max_requests in radiusd.conf is too low and caused authentication problem in some customer environments. Currently the value is hardcoded to 1024.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2016-10-21 14:13:05 CEST
Please note that for each auth request a separate authhelper process is spawned. So if the current limit of 1024 is reached, 1024 helper processes were running.
Comment 2 Janek Walkenhorst univentionstaff 2017-05-12 18:58:21 CEST
Advisory: univention-radius.yaml

 The maximum number of requests which the server keeps track of. This should be 256 multiplied by the number of clients, e.g. With 4 clients, this number should be 1024. (Default: 1024)
Comment 3 Daniel Tröder univentionstaff 2017-05-21 11:41:28 CEST
OK: code
OK: manual test
OK: advisory (wording r79460)
Comment 4 Janek Walkenhorst univentionstaff 2017-06-15 17:58:00 CEST