Hi Hugh,
I'm an Antonio Coloma's colleague.
We are working together in a high avaibility radius system with Radiator
radius server.
In our test we have discovered that when we use a SQL session database
with the SQL engine located in a host that can not be reached by the
radiusd daemon (due to a firewall, or another cause)(there is no error
in the connection, the problem is that there is no answer to the
connection request (TCP connect timeout)), the file descriptor used in
the socket created by radiusd to make this connection is not closed.
We have seen this using the truss command avaible under Solaris. This is
part of the output generated by this command:
...
12493: so_socket(2, 2, 0, "", 1) = 6
12493: setsockopt(6, 65535, 8, 0xEFFFF304, 4) = 0
12493: connect(6, 0xEFFFF378, 16) (sleeping...)
12493: Received signal #14, SIGALRM, in connect() [caught]
12493: connect(6, 0xEFFFF378, 16) Err#91 ERESTART
...
There is no close system call for close the file descriptor 6.
The radiusd process retries to make the connection again later, and
opens a new socket and again the same system calls sequence with no
close of the recently created file descriptor:
...
12493: so_socket(2, 2, 0, "", 1) = 7
12493: setsockopt(7, 65535, 8, 0xEFFFF304, 4) = 0
12493: connect(7, 0xEFFFF378, 16) (sleeping...)
12493: Received signal #14, SIGALRM, in connect() [caught]
12493: connect(7, 0xEFFFF378, 16) Err#91 ERESTART
...
At the end the radisd service fails due to a there is no file
descriptors avaible, and in the logfile appears messages like:
"Wed Aug 16 22:42:23 2000: WARNING: Could not open user database file
'./db/users' in Radius::AuthDBFILE: Too many open files"
Do you known something about this issue ?
Is a bug ?
Is there any solution to it ?
Greetings.
---
Carles Xavier Munyoz Baldó / [EMAIL PROTECTED]
Wanadoo España
Dpto. Sistemas / System Department
Tel: +34 96 5040000 Ext. 40046 - Fax: +34 96 5040047
http://www.wanadoo.es/
---
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
