Hello, How should settle in "radiusd.conf" max_request_time, cleanup_delay and max_requests? Currently I max_request_time = 30 cleanup_delay = 2 and max_requests = 50432 Is it set? If it is misconfigured what can happen? best regards
Hello, When I read the explanations of "max-request" must change this number to the number of clients. But what that "clients": the number of public IP that connect different or the number of NAS in the database? I have a Wifi Hotspot system with terminals for customers. There are about 274 clients (routers connected to the ADSL Box customers). Should I surrender the default values or should I increase? best regards
Date: Thu, 17 Jul 2014 19:17:19 +0000 From: A.L.M.Buxey@lboro.ac.uk To: freeradius-users@lists.freeradius.org Subject: Re: radiusd.conf max request ?
Hi,
Currently I max_request_time = 30 cleanup_delay = 2 and max_requests = 50432
well, the first of those is default...the others have been changed...so why were they changed (reasons) - and was the text thats in radiusd.conf read to understand the effects? :-)
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 17 Jul 2014, at 15:39, Arnaud . <arn0@live.fr> wrote:
Hello,
When I read the explanations of "max-request" must change this number to the number of clients. But what that"clients": the number of public IP that connect different or the number of NAS in the database?
Doing it by clients is only a very rough way of determining the correct queue size.
I have a Wifi Hotspot system with terminals for customers. There are about 274 clients (routers connected to theADSL Box customers).
It controls number of requests the server holds state for. You should determine the normal number of requests received per second, then multiple it by cleanup_delay, and double it to give you a bit of a buffer. It's mainly useful for keeping the server from melting down completely in overload situations. If you keep reaching the limit of the buffer and the server starts discarding requests, one of your backend databases or processes is too slow, or the server is processing a very high number of packets per second and you've left the queue value at default. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Arnaud . wrote:
Hello,
How should settle in "radiusd.conf" max_request_time, cleanup_delay and max_requests?
The configuration files document what they're for, and what they do.
Currently I max_request_time = 30 cleanup_delay = 2 and max_requests = 50432
Is it set? If it is misconfigured what can happen?
Don't change max_request_time or cleanup_delay. Set max_requests to some large value. If you get it wrong, error messages will appear in the log. The messages will tell you to increase max_request_time. Alan DeKok.
Hello So if I have 274 routers connected to Hotspot Radius server, I need to put in max-request: 70144 (256 queries * number of clients) Is this correct? best Regards
Date: Thu, 17 Jul 2014 16:43:45 -0400 From: aland@deployingradius.com To: freeradius-users@lists.freeradius.org Subject: Re: radiusd.conf max request ?
Arnaud . wrote:
Hello,
How should settle in "radiusd.conf" max_request_time, cleanup_delay and max_requests?
The configuration files document what they're for, and what they do.
Currently I max_request_time = 30 cleanup_delay = 2 and max_requests = 50432
Is it set? If it is misconfigured what can happen?
Don't change max_request_time or cleanup_delay. Set max_requests to some large value.
If you get it wrong, error messages will appear in the log. The messages will tell you to increase max_request_time.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
A client is not limited to 256 ongoing requests. One client can (and will, if need be) use multiple source ports (for each source port, 256 requests can be ongoing), hence sending as many requests as it needs at a given time. This is not exact science. You need to do is evaluate the maximum total requests/s rate your server will have to serve. Multiply that by your max request time, and you have the max requests FreeRADIUS will be handling at a given time. BTW, the following comment in radiusd.conf is misleading, it should probably be updated : # max_requests: 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. De : freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org [mailto:freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org] De la part de Arnaud . Envoyé : vendredi 18 juillet 2014 09:36 À : FreeRadius users mailing list Objet : RE: radiusd.conf max request ? Hello So if I have 274 routers connected to Hotspot Radius server, I need to put in max-request: 70144 (256 queries * number of clients) Is this correct? best Regards
Date: Thu, 17 Jul 2014 16:43:45 -0400 From: aland@deployingradius.com<mailto:aland@deployingradius.com> To: freeradius-users@lists.freeradius.org<mailto:freeradius-users@lists.freeradius.org> Subject: Re: radiusd.conf max request ?
Arnaud . wrote:
Hello,
How should settle in "radiusd.conf" max_request_time, cleanup_delay and max_requests?
The configuration files document what they're for, and what they do.
Currently I max_request_time = 30 cleanup_delay = 2 and max_requests = 50432
Is it set? If it is misconfigured what can happen?
Don't change max_request_time or cleanup_delay. Set max_requests to some large value.
If you get it wrong, error messages will appear in the log. The messages will tell you to increase max_request_time.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Thank you and where can we see the maximum total requests/s rate? Because it is difficult to see the maximum queries to a given order to determine the correct value now? best Regards From: nicolas.chaigneau@capgemini.com To: freeradius-users@lists.freeradius.org Subject: RE: radiusd.conf max request ? Date: Fri, 18 Jul 2014 08:29:51 +0000 A client is not limited to 256 ongoing requests. One client can (and will, if need be) use multiple source ports (for each source port, 256 requests can be ongoing), hence sending as many requests as it needs at a given time. This is not exact science. You need to do is evaluate the maximum total requests/s rate your server will have to serve. Multiply that by your max request time, and you have the max requests FreeRADIUS will be handling at a given time. BTW, the following comment in radiusd.conf is misleading, it should probably be updated : # max_requests: 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. De : freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org [mailto:freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org] De la part de Arnaud . Envoyé : vendredi 18 juillet 2014 09:36 À : FreeRadius users mailing list Objet : RE: radiusd.conf max request ? Hello So if I have 274 routers connected to Hotspot Radius server, I need to put in max-request: 70144 (256 queries * number of clients) Is this correct? best Regards
Date: Thu, 17 Jul 2014 16:43:45 -0400
From: aland@deployingradius.com
To: freeradius-users@lists.freeradius.org
Subject: Re: radiusd.conf max request ?
Arnaud . wrote:
Hello,
How should settle in "radiusd.conf" max_request_time, cleanup_delay and
max_requests?
The configuration files document what they're for, and what they do.
Currently I max_request_time = 30 cleanup_delay = 2 and max_requests =
50432
Is it set? If it is misconfigured what can happen?
Don't change max_request_time or cleanup_delay. Set max_requests to
some large value.
If you get it wrong, error messages will appear in the log. The
messages will tell you to increase max_request_time.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
The traffic your server has to serve depends on your clients, only you can estimate that. As Alan said, you can set max_requests to an arbitrary large value, e.g. 200000. FreeRADIUS doesn't consume much memory anyway, it probably won't make any difference if it's larger than necessary. De : freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org [mailto:freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org] De la part de Arnaud . Envoyé : vendredi 18 juillet 2014 10:56 À : FreeRadius users mailing list Objet : RE: radiusd.conf max request ? Thank you and where can we see the maximum total requests/s rate? Because it is difficult to see the maximum queries to a given order to determine the correct value now? best Regards ________________________________ From: nicolas.chaigneau@capgemini.com<mailto:nicolas.chaigneau@capgemini.com> To: freeradius-users@lists.freeradius.org<mailto:freeradius-users@lists.freeradius.org> Subject: RE: radiusd.conf max request ? Date: Fri, 18 Jul 2014 08:29:51 +0000 A client is not limited to 256 ongoing requests. One client can (and will, if need be) use multiple source ports (for each source port, 256 requests can be ongoing), hence sending as many requests as it needs at a given time. This is not exact science. You need to do is evaluate the maximum total requests/s rate your server will have to serve. Multiply that by your max request time, and you have the max requests FreeRADIUS will be handling at a given time. BTW, the following comment in radiusd.conf is misleading, it should probably be updated : # max_requests: 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. De : freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org<mailto:freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org> [mailto:freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org] De la part de Arnaud . Envoyé : vendredi 18 juillet 2014 09:36 À : FreeRadius users mailing list Objet : RE: radiusd.conf max request ? Hello So if I have 274 routers connected to Hotspot Radius server, I need to put in max-request: 70144 (256 queries * number of clients) Is this correct? best Regards > Date: Thu, 17 Jul 2014 16:43:45 -0400 > From: aland@deployingradius.com<mailto:aland@deployingradius.com> > To: freeradius-users@lists.freeradius.org<mailto:freeradius-users@lists.freeradius.org> > Subject: Re: radiusd.conf max request ? > > Arnaud . wrote: > > Hello, > > > > How should settle in "radiusd.conf" max_request_time, cleanup_delay and > > max_requests? > > The configuration files document what they're for, and what they do. > > > Currently I max_request_time = 30 cleanup_delay = 2 and max_requests = > > 50432 > > > > Is it set? If it is misconfigured what can happen? > > Don't change max_request_time or cleanup_delay. Set max_requests to > some large value. > > If you get it wrong, error messages will appear in the log. The > messages will tell you to increase max_request_time. > > Alan DeKok. > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
OK I think I'll define a large value to be quiet! But 200000 is very large? They are the consequences of a too large value? In the logs I spotted a few lines: Tue Jul 15 20:46:41 2014 : Error: Discarding duplicate request from client localhost:2054 - ID: 0 due to unfinished request 442908 Tue Jul 15 21:06:54 2014 : Error: Discarding duplicate request from client localhost:2056 - ID: 0 due to unfinished request 443583 Tue Jul 15 21:06:55 2014 : Error: Discarding duplicate request from client localhost:32768 - ID: 156 due to unfinished request 443584 There is a relation with max_rquest or is something else? From: nicolas.chaigneau@capgemini.com To: freeradius-users@lists.freeradius.org Subject: RE: radiusd.conf max request ? Date: Fri, 18 Jul 2014 09:18:37 +0000 The traffic your server has to serve depends on your clients, only you can estimate that. As Alan said, you can set max_requests to an arbitrary large value, e.g. 200000. FreeRADIUS doesn’t consume much memory anyway, it probably won’t make any difference if it’s larger than necessary. De : freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org [mailto:freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org] De la part de Arnaud . Envoyé : vendredi 18 juillet 2014 10:56 À : FreeRadius users mailing list Objet : RE: radiusd.conf max request ? Thank you and where can we see the maximum total requests/s rate? Because it is difficult to see the maximum queries to a given order to determine the correct value now? best Regards From: nicolas.chaigneau@capgemini.com To: freeradius-users@lists.freeradius.org Subject: RE: radiusd.conf max request ? Date: Fri, 18 Jul 2014 08:29:51 +0000 A client is not limited to 256 ongoing requests. One client can (and will, if need be) use multiple source ports (for each source port, 256 requests can be ongoing), hence sending as many requests as it needs at a given time. This is not exact science. You need to do is evaluate the maximum total requests/s rate your server will have to serve. Multiply that by your max request time, and you have the max requests FreeRADIUS will be handling at a given time. BTW, the following comment in radiusd.conf is misleading, it should probably be updated : # max_requests: 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. De : freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org [mailto:freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org] De la part de Arnaud . Envoyé : vendredi 18 juillet 2014 09:36 À : FreeRadius users mailing list Objet : RE: radiusd.conf max request ? Hello So if I have 274 routers connected to Hotspot Radius server, I need to put in max-request: 70144 (256 queries * number of clients) Is this correct? best Regards
Date: Thu, 17 Jul 2014 16:43:45 -0400
From: aland@deployingradius.com
To: freeradius-users@lists.freeradius.org
Subject: Re: radiusd.conf max request ?
Arnaud . wrote:
Hello,
How should settle in "radiusd.conf" max_request_time, cleanup_delay and
max_requests?
The configuration files document what they're for, and what they do.
Currently I max_request_time = 30 cleanup_delay = 2 and max_requests =
50432
Is it set? If it is misconfigured what can happen?
Don't change max_request_time or cleanup_delay. Set max_requests to
some large value.
If you get it wrong, error messages will appear in the log. The
messages will tell you to increase max_request_time.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
No. It means you're backend isn't fast enough to deal with the queries. Wg DB too slow. Alan has already mentioned this in this very thread. alan -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
participants (6)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan Buxey
-
Alan DeKok -
Arnaud . -
Arran Cudbard-Bell -
Chaigneau, Nicolas