RE: (RADIATOR) Radiator load problem
Thanx :) God knows how long that's been there, I've only just been assigned this box... Thought you said nothing had changed ;-) /Ingvar Cheers, David Napier === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator load problem
Hello David - On Thursday 18 October 2001 11:57, David Napier wrote: Thanx for the reply High, can't fault this service :) We try to please. Actually, we try to be *much* better than any other product and any other support you have ever seen. The first question of course is what has changed?. According to logs, nothing. We use /etc/password for userlists on this box and only the usual additions and deletions have occured. We do have a few users explicitly mentioned in /etc/raddb/user, and one new user added there, however the syntax is fine (ie, exactly like the 300 before it) as its all script generated. I've grilled other admins and no-one knows anything :/ H. The second question is how do you start radiusd?. We start via the command `/usr/bin/radiusd -config_file /etc/raddb/radiator.cfg`. I am uncertain whether this was bundled with radiator or someone else scripted it. This doesn't answer my question. What I want to know is how do multiple copies of Radiator get started?. If you should only have one copy running and all of a sudden there are many copies running, then something is clearly amiss. And the third question is can you please send me a copy of the configuration file (no secrets) together with a trace 4 debug showing what is going on?. Attached below, with all scarey info 'd. I haven't attached a trace 4 as I haven't got a sample with radius chomping cpu yet. Hopefully we won't have to wait long (or hopefully we will :) Thanks, but unfortunately most of the interesting bits are in the Include files, so I can't really see much. regards Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator load problem
Hello David - The first question of course is what has changed?. The second question is how do you start radiusd?. And the third question is can you please send me a copy of the configuration file (no secrets) together with a trace 4 debug showing what is going on?. BTW - the correct spelling to fix the problem shown below is: Van-Jacobson-TCP-IP regards Hugh On Thursday 18 October 2001 10:42, mail - dilbert wrote: Hi folks :) We've been using Radiator successfully for years now, and its worked perfectly (Version 2.16.3). The last weeks have seen a problem however. Randomly (well, we can't find any pattern causing the problem) 4 or 5 radiusd processes chew up 100% CPU, requiring a restart of radiator. A couple of hours to days later though, the same problem pops up again. There's been no changes to the systems, and there is no common user, or error that occurs prior, during or after the load problem. I can supply a trace 4 log soon, but here's a snapshot of our normal logging around the times of the problems, and as can be seen nothing weird happened. Any ideas? David Napier Wed Oct 17 19:48:54 2001: INFO: Server started: Radiator 2.16.3 on ns1.dot.net.au Wed Oct 17 19:49:47 2001: INFO: Access rejected for ...: No such user Wed Oct 17 20:12:35 2001: ERR: There is no value named Van-Jacobsen-TCP-IP for attribute Framed-Compression. Using 0. Wed Oct 17 20:13:47 2001: ERR: There is no value named Van-Jacobsen-TCP-IP for attribute Framed-Compression. Using 0. Wed Oct 17 20:14:39 2001: INFO: Access rejected for stevos: No such user Wed Oct 17 20:24:48 2001: INFO: Access rejected for julid: Bad Encrypted password Wed Oct 17 20:30:08 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 20:31:00 2001: ERR: There is no value named Van-Jacobsen-TCP-IP for attribute Framed-Compression. Using 0. Wed Oct 17 20:36:25 2001: INFO: Access rejected for ronhill: Bad Encrypted password Wed Oct 17 20:39:16 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 20:39:57 2001: INFO: Access rejected for ronhill: Bad Encrypted password Wed Oct 17 20:41:01 2001: INFO: Access rejected for ronhill: Bad Encrypted password Wed Oct 17 20:41:27 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 20:42:00 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 20:42:03 2001: INFO: Access rejected for sfal: Bad Encrypted password Wed Oct 17 20:42:25 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 20:43:36 2001: NOTICE: SIGTERM received: stopping Wed Oct 17 20:44:30 2001: INFO: Server started: Radiator 2.16.3 on ns1.dot.net.au Wed Oct 17 20:44:34 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 20:46:31 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 20:48:17 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 20:58:25 2001: INFO: Access rejected for djardine: Bad Encrypted password Wed Oct 17 20:59:49 2001: INFO: Access rejected for djardine: Bad Encrypted password Wed Oct 17 21:01:59 2001: INFO: Access rejected for ronhill: Bad Encrypted password Wed Oct 17 21:02:52 2001: INFO: Access rejected for ronhill: Bad Encrypted password Wed Oct 17 21:03:53 2001: INFO: Access rejected for ron hill: No such user Wed Oct 17 21:04:49 2001: INFO: Access rejected for ronhill: Bad Encrypted password Wed Oct 17 21:06:47 2001: INFO: Access rejected for ronhill: Bad Encrypted password Wed Oct 17 21:55:32 2001: ERR: There is no value named Van-Jacobsen-TCP-IP for attribute Framed-Compression. Using 0. Wed Oct 17 22:13:49 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 22:13:49 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 22:13:49 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 22:13:50 2001: INFO: Access rejected for [EMAIL PROTECTED]: Ipass failed Wed Oct 17 22:17:04 2001: INFO: Server started: Radiator 2.16.3 on ns1.dot.net.au Wed Oct 17 22:44:08 2001: INFO: Access rejected for fraser: Bad Encrypted password Wed Oct 17 22:57:38 2001: INFO: Access rejected for ` L: No such user Wed Oct 17 22:57:40 2001: INFO: Access rejected for ` L: No such user Wed Oct 17 22:57:42 2001: INFO: Access rejected for ` L: No such user Wed Oct 17 23:15:16 2001: INFO: Server started: Radiator 2.16.3 on ns1.dot.net.au Wed Oct 17 23:24:24 2001: INFO: Access rejected for ...: No such user Wed Oct 17 23:27:14 2001: INFO: Access rejected for ...: No such user Wed Oct 17 23:31:41 2001: INFO: Access rejected for ...: No such user === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server
Re: (RADIATOR) Radiator load problem
Thanx for the reply High, can't fault this service :) The first question of course is what has changed?. According to logs, nothing. We use /etc/password for userlists on this box and only the usual additions and deletions have occured. We do have a few users explicitly mentioned in /etc/raddb/user, and one new user added there, however the syntax is fine (ie, exactly like the 300 before it) as its all script generated. I've grilled other admins and no-one knows anything :/ The second question is how do you start radiusd?. We start via the command `/usr/bin/radiusd -config_file /etc/raddb/radiator.cfg`. I am uncertain whether this was bundled with radiator or someone else scripted it. And the third question is can you please send me a copy of the configuration file (no secrets) together with a trace 4 debug showing what is going on?. Attached below, with all scarey info 'd. I haven't attached a trace 4 as I haven't got a sample with radius chomping cpu yet. Hopefully we won't have to wait long (or hopefully we will :) BTW - the correct spelling to fix the problem shown below is: Van-Jacobson-TCP-IP Thanx :) God knows how long that's been there, I've only just been assigned this box... Cheers, David Napier -- radiator.cfg ~ # Set the Database Directory: %D DbDir /etc/raddb # Set the Log Directory: %L LogDir /var/log/radacct # Load up all the local stuff include %D/local.cfg #Trace 3 #Log SYSLOG # Facilityuser # Lets see all info above messages Trace 4 #/Log # Load up the NAS cliet list include %D/clients.cfg # Load up the list of realms include %D/realms.cfg # This clause defines an authorisation method that will be used # by any users in the database with Auth-Type=System. It will # match the Identifier System AuthBy UNIX Identifier System Filename /etc/shadow /AuthBy users ~ Password= Service-Type = Framed-User, Framed-Protocol = PPP, Framed-IP-Address = 255.255.255.254, NAS-IP-Address = z.z.z.z, Framed-Compression = Van-Jacobson-TCP-IP, Framed-MTU = 1500 # DEFAULT Auth-Type = System Service-Type = Framed-User, Framed-Protocol = PPP, Framed-IP-Address = 255.255.255.254, # Framed-Compression = Van-Jacobson-TCP-IP, # Idle-Timeout = 5400, Idle-Timeout = 3600, # Idle-Timeout = 18000, Session-Timeout = 36000, Framed-MTU = 1500 === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
