Hello Charles -
On Fri, 13 Oct 2000, Charles Sprickman wrote:
> On Thu, 12 Oct 2000, Hugh Irvine wrote:
>
> > > At trace 3, I see no oddities associated with this
> > > username. Any ideas how to track this down??
> >
> > Yes - use trace 4 and watch what happens.
>
> I knew you'd say that :)
>
> Found my problem:
>
Good - well done.
> -MySQL session db definition
> <SessionDatabase SQL>
> Identifier SDB_mysql
>
> DBSource dbi:mysql:radius:localhost
> DBUsername xxxx
> DBAuth xxxx
> [snip]
> Timeout 30
> Identifier sessiondb
> FailureBackoffTime 200
> </SessionDatabase>
>
> That extra "Identifier" line threw something off, and all requests were
> going to the other session database I have configured. Odd behaviour, but
> easy to find once I had the trace at 4. I saw ALL handlers were using my
> other session db, even though only one was configured to do so.
>
What would have happened is this - the second Identifier would have overwritten
the first, and then if any other Handler tried to access SDB_mysql, it would
not have been found. Then, if the other session database was the last one in
the configuration file, it would have been used by default, which is what you
observed.
Isn't trace 4 wonderful? I couldn't live without it...
:-)
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
