Hi Juha,
the warning is due a race condition in timer processing. A transaction
was detached from the timer list (expire, cleanup, reply received); in
the same time, another process was computing the transaction (maybe a
reply was received) and it's trying to place it back into timer....and
this is the race.
Probably by delaying the sending of final reply (due failing RADIUS),
the race was more probably to happen than in normal processing.
regards,
bogdan
Juha Heinanen wrote:
one user told me that he is getting detached timer warnings like this:
Jun 9 12:16:34 localhost /usr/sbin/openser[4906]: WARNING: set_timer
for 3 list called on a "detached" timer -- ignoring: 0x407a6dd8
following this warning syslog output reveals that he also had problem
with radius server:
Jun 9 12:16:36 localhost /usr/sbin/openser[4883]: rc_send_server: no reply
from RADIUS server localhost.localdomain:1813
Jun 9 12:16:36 localhost /usr/sbin/openser[4883]: ERROR: acc_rad_request:
radius-ing failed
so perhaps the detached timer error was due to his radius server not
responding for radius accounting request.
should openser be able to cope with radius problem without trying to use
a detached timer?
-- juha
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
