> At first glance, this appears to be barfing because it's trying to contact the absent server with OCIErrorGet to find > out why it can't contact the server....
> As a test, try putting 'return msgbuf;' on line 48, right after the memset call. You'll get no error text in your > logs, but if that fixes it then we've possibly hit a segfaulting bug in liboracleclient... I did that test, but I've got the error right after trying to execute the alt_start_query, which is updating the radacct table for start packet. > It'd be worth checking the values of the parameters to OCIErrorGet to confirm they're what we'd expect... > I think the command in GDB is 'print oracle_sock->errHandle' and the like... > Mind you, I don't know the meaning of the parameters to OCIErrorCode anyway... It may just need some parameter > checking before OCIErrorCode is called. > Anyway, the reason it doesn't failover is because this segfault comes on the line before the module returns > RLM_MODULE_FAIL, which I expect would trigger the failover. So with the 'return' inserted as described above, it > should failover fine. Regards ------------------------------------------------------------------------ ------------------- Yasser Ahmed Hosny - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
