(RADIATOR) Radiator Log showing "No such user.

[Hugh Irvine]

Hello Ronan -

As mentioned in my previous mail, I will need to see a copy of the 
configuration file (no secrets) together with a trace 4 debug from Radiator 
showing what is happening.

regards

Hugh


On Tue, 29 Jan 2002 07:00, Ronan Eckelberry wrote:
> I think I see the problem after looking at the trace.  It seems
> that the user is disconnecting/being disconnected and not being removed
> from RADONLINE.  This doesn't happen all the time, but in the Trace it
> shows that they are being denied for the "Simultaneous Use", but I am
> using an <AuthLog FILE> clause to just write the failed logins to a file
> (Which is what I use to write to a webpage for the technicians to look
> at) that just gives the reason that the login failed as "No such user".
> Is there any way to change the AuthLog to display the real reason and
> not just "No such user"?  Below is the AuthLog clause I am using.  I am
> not logging Successful logins right now which is why I have it disabled.
>
> <AuthLog FILE>
>         Identifier AuthLog
>         Filename %L/authlog
>         LogSuccess 0
>         LogFailure 1
>         SuccessFormat %l:%U:%P:OK:%1:%{Calling-Station-Id}
>         FailureFormat %l:%U:%P:FAIL:%1:%{Calling-Station-Id}
> </AuthLog>
>
> 	Any input would be appreciated.  Thanks for all the help guys.
>
> :)
>
> -Ronan
>
>
> -----Original Message-----
> From: Hugh Irvine [mailto:hugh at open.com.au]
> Sent: Thursday, 24 January, 2002 22:51
> To: Ronan Eckelberry; radiator at open.com.au
> Subject: Re: (RADIATOR) Radiator Log showing "No such user.
>
>
>
> Hello Ronan -
>
> As usual, the only to tell is to look at a trace 4 debug from Radiator
> in
> conjunction with the configuration file (no secrets). If you send them
> to me
> I will take a look.
>
> regards
>
> Hugh
>
> On Fri, 25 Jan 2002 13:24, Ronan Eckelberry wrote:
> > For some reason Radiator is denying random customers access at
> > random times.  It is logging the reason as "No such user".  It will
> > usually only do this once, but I have seen it do it a few times.  The
> > user does exist in the database.  I will try to log in with the un/pw
> > and get rejected, only to try again seconds or minutes later and be
>
> let
>
> > in.  The user is not listed in the RADONLINE table, nor are they
>
> listed
>
> > as inactive.  Has anyone else had this happen before?  Does anyone
>
> have
>
> > any suggestions?  It seems kind of weird.
> >
> > 	The only thing that I can see in the logs are "Duplicate
> > Requests" from the NASs sometimes and sometimes Radiator will die, but
> > INETD restarts it as soon as it receives a request.
> >
> > 	Any suggestions would be more than helpful.
> >
> > Thanks all,
> >
> > -Ronan
> >
> > Ronan Eckelberry
> > ronan at gowebco.com
> > Network/Systems Engineer
> > Webco Solutions, Inc
> > (352)746-2500
> > www.webcosolutions.com
> >
> > ===
> > Archive at http://www.open.com.au/archives/radiator/
> > Announcements on radiator-announce at open.com.au
> > To unsubscribe, email 'majordomo at open.com.au' with
> > 'unsubscribe radiator' in the body of the message.

-- 
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 radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.