Re: [RADIATOR] 100% load 1 cpu core
Hi On Tue, 2 Feb 2016, SinTeZ Wh1te wrote: > Hello List! > > After installing Radiator on the test server, I got a problem with the 100% > load 1 CPU core but the others are unused. > > Screenshot > http://i.imgur.com/eQjK5k8.png > there are various ways to distribute load over multile cores on radiator by fanning processes out to multiple radiator instances. But before getting into that we need to understand a lot more of your setup. You seem to have a quite simple proxy radius configuration. I have had setups with high load where a single frontend radiator process has distributed eap radius requests to multiple backends for cpu intensive eap processing with the Farming feature. In those cases the frontend has had no trouble at all to keep up with the load. I do see though that your radiator process seems to have high memory consumption over 100MB in your screenshot. That makes me wonder how responsive the backend is that you are proxying to. Radiator needs to keep track of all the requests it has proxies to the other host so if that host cannot keep up with the load a queue will build up on the frontend and it will start resending which will cause even more load on the backend. So generally if the backend cannot keep up things might go down the hill quite fast. Not sure if this is your issue. That would need further investigation. Please tell us more about: 1. the type of requests you are handling 2. the type of the backend you are proxying to Greetings Christian -- Christian Kratzer CK Software GmbH Email: c...@cksoft.de Wildberger Weg 24/2 Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart Mobile: +49 171 1947 843 Geschaeftsfuehrer: Christian Kratzer Web: http://www.cksoft.de/ ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
[RADIATOR] 100% load 1 cpu core
Hello List! After installing Radiator on the test server, I got a problem with the 100% load 1 CPU core but the others are unused. Screenshot http://i.imgur.com/eQjK5k8.png radius.cfg # Listen for addresses using default ports BindAddress ::,0.0.0.0 #BindV6Only AuthPort1645,1820 AcctPort1646,1821 # Uncomment these for foreground debugging #Foreground #LogStdout Userradiator Group radiator DbDir /etc/radiator DictionaryFile /etc/radiator/dictionary LogDir /var/log/radiator LogFile %L/radiator-log-%Y-%m PidFile /var/run/radiator/radiusd.pid # Dont turn this up too high, since all log messages are logged # to the RADMESSAGES table in the database. 3 will give you everything # except debugging messages Trace 2 # You will probably want to change this to suit your site. # You should list all the clients you have, and their secrets # If you are using the Radmin Clients table, you wil probably # want to disable this. Identifier Client-DEFAULT Secret 12345 DupInterval 0 RejectHasReason Host 192.168.144.3 Secret 12345 AuthPort 1820 AcctPort 1821 RejectHasReason -- With regards, Alexander Yakunin ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] 100% load 1 cpu core
Hello - What are you using to test? And you should note that a single instance of Radiator is single-threaded and will only use 1 CPU core. At the very least you should run separate instances for authentication and accounting. regards Hugh > On 2 Feb 2016, at 20:00, SinTeZ Wh1tewrote: > > Hello List! > > After installing Radiator on the test server, I got a problem with the 100% > load 1 CPU core but the others are unused. > > Screenshot > http://i.imgur.com/eQjK5k8.png > > radius.cfg > > > # Listen for addresses using default ports > BindAddress ::,0.0.0.0 > #BindV6Only > > AuthPort1645,1820 > AcctPort1646,1821 > > # Uncomment these for foreground debugging > #Foreground > #LogStdout > > Userradiator > Group radiator > > DbDir /etc/radiator > DictionaryFile /etc/radiator/dictionary > LogDir /var/log/radiator > LogFile %L/radiator-log-%Y-%m > PidFile /var/run/radiator/radiusd.pid > > # Dont turn this up too high, since all log messages are logged > # to the RADMESSAGES table in the database. 3 will give you everything > # except debugging messages > Trace 2 > > # You will probably want to change this to suit your site. > # You should list all the clients you have, and their secrets > # If you are using the Radmin Clients table, you wil probably > # want to disable this. > > Identifier Client-DEFAULT > Secret 12345 > DupInterval 0 > > > > > RejectHasReason > > Host 192.168.144.3 > Secret 12345 > AuthPort 1820 > AcctPort 1821 > RejectHasReason > > > > > > -- > With regards, > Alexander Yakunin > ___ > radiator mailing list > radiator@open.com.au > http://www.open.com.au/mailman/listinfo/radiator -- Hugh Irvine h...@open.com.au Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER, SIM, etc. Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc. ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator