Thanks for the replies! We'll try to kill the process manually, but it is still unclear what is the core reason of the service fall ?
The logs should speak for itself. To fix this one you need to coordinate with network/dba guys. Sometimes its simply because oracle s dead or too busy to respond to anything. Other times in can be firewall issues.
There were no network changes before and during the RADIUS outage (no firewall). Dba guys say that the Oracle is Ok, and no significant issues were placed on record according to oracle logs. Alexander
2010/12/15 Александр Чурсин <achursin86@gmail.com>:
The logs should speak for itself. To fix this one you need to coordinate with network/dba guys. Sometimes its simply because oracle s dead or too busy to respond to anything. Other times in can be firewall issues.
There were no network changes before and during the RADIUS outage (no firewall). Dba guys say that the Oracle is Ok, and no significant issues were placed on record according to oracle logs.
Then do a simple test. When radius says can't reconnect, connect manually from the radius server with sqlplus (or whatever you're familiar with) using the same user/password that you use for radius. -- Fajar
Hi,
There were no network changes before and during the RADIUS outage (no firewall). Dba guys say that the Oracle is Ok, and no significant issues were placed on record according to oracle logs.
Then do a simple test. When radius says can't reconnect, connect manually from the radius server with sqlplus (or whatever you're familiar with) using the same user/password that you use for radius.
..and first rule of networking - never believe what another team says about their server - especially DBA people ;-) alan
Alan, please, clarify some things: 1) >in the accounting {} sectin of your server, instead of just calling SQL,
wrapper it:
if (Acct-Session-Time != 0) { sql
> } > else { > ok >} Where can I put this wrapper, sql.conf or in some source file and after that the server must be recompiled ? 2) > tcmdpump of your DB connection, and in the other, run radiusd -X So I need to run two terminal windows with these command running on it during the problem? Tcpdump... you mean tcpdump traffic with a source of RADIUS and a destionaton of Oracle DB ? 3) >you are sending a packet with same details - constraint violation. What do you mean? Sorry for newbie questions. Thanks in advance! p.s. Yes, you are right RADIUS client is Cisco PDSN.
Hi,
Alan, please, clarify some things:
1) >in the accounting {} sectin of your server, instead of just calling SQL,
wrapper it:
if (Acct-Session-Time != 0) { sql
> } > else { > ok >}
Where can I put this wrapper, sql.conf or in some source file and after that the server must be recompiled ?
read what I wrote again - pay particular attention to the bit straight after the 1) part place it in the accounting {} section where SQL is called in your virtual server
2) > tcmdpump of your DB connection, and in the other, run radiusd -X
So I need to run two terminal windows with these command running on it during the problem? Tcpdump... you mean tcpdump traffic with a source of RADIUS and a destionaton of Oracle DB ?
yes and yes
3) >you are sending a packet with same details - constraint violation. What do you mean?
databases, particularly relational ones, have unique keys in each index entry so that they can be linked/searched/operated on. if you try inserting a new entry with the same key as an existing entry, then its doomed to failure.
p.s. Yes, you are right RADIUS client is Cisco PDSN.
yes, we have cisco kit and it spews out such packets too alan
Ok, thanks for explanation. The RADIUS version is 1.1.0 In the accounting section of the radiusd.conf we have: accounting { #detail #acct_unique ################################################# # Vladikavkaz OSE Acct-Type OSE { acct_unique group { sqlacct { fail = 1 # ok = return } OSE { fail = 1 ok = return } } # sql_log } ################################################# and so on anologous to these constructions with #### as a delimeter ... So, no "sql" mentioned... I'am sorry, but it's unclear for me where to put the wrapper. Alexander
participants (3)
-
Alan Buxey -
Fajar A. Nugraha -
Александр Чурсин