* randy <[EMAIL PROTECTED]> [2003-07-09 20:22]: > since after starting radiusd the connections to my oracle cluster > get established ok and work for 2:30 minutes, is there a way to > "force" freeradius to close those connections and open them again > after, say, 2 minutes? this way at least i wouldn't have to kill > radiusd every 2 minutes...
it looks like i have tracked down the problem: i have set up a completely identical redhat 7.3 box with freeradius-snapshot-20030702 with rlm_sql_oracle, which is connecting to the same oracle rac cluster but from a different network segment. so the only difference is that the connections between radius and oracle are going over a different firewall. this new radius hasn't had any difficulties since i started it up about 24 hours ago. so this has got to be a network/firewall problem. still i think that freeradius should be able to figure out when the connections to oracle have died. to me it looks like it doesn't even notice that the connections are gone, and keeps waiting for a response from oracle. is there a way i can tell freeradius to completely shut down the oracle connections and re-establish them after n seconds of no response? none of the settings i can configure in oraclesql.conf changed anything. all i can do is kill radiusd, and once it comes back up, the connections are re-established fine. shouln't this be possible without totally killing radiusd? many thanks, randy ps: i have also tried the latest snapshot (20030710) but there's no difference in the behaviour. i went back to 20030702 because that's the exact same version i'm running on the machine that's having problems, to be able to rule out any other differences in the setup. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
