Wisam Najim <[EMAIL PROTECTED]> wrote:
> I am running freeRADIUS version 0.9.0 on Solaris 2.8 and using oracle
> 8.1.7.4 database for accounting and authentication.

  1.0.0-pre3 has a number of fixes to the Oracle module, which correct
memory leaks & bad pointer problems.

> I have two databases for authentication and I am configuring the
> freeRADIUS to implement failover.  When the radius detects that
> primary database is not accessible it crashes in most of the cases
> when using the standard oracle library that comes with installed
> oracle client "libclntsh.so.8.0".

  That's bad.  If you have access to a tool like "purify", that can
help enormously.  If not, you're pretty much stuck with gdb.

> If I use another library that was generated by another machine the
> radius works fine. (I do not know how that library was generated)

  Do you know where that library came from?  That is, why does one
library work, and the other fail?

> I would like to know if there are special requirements for oracle client
> installation in order to work properly with freeRADIUS.

  There shouldn't be.

> I have tried the third pre 1.0.0 version and still have the same problem.

  Hmm... I'd like to be able to say it's a problem with the Oracle
library, but I can't be sure that's true.

  Alan DeKok.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to