I have already posted my problems to the list but I got no answers.
I'm getting this error on the Postgres logs: pq_recvbuf: unexpected EOF on client connection
That happens only with freeradius connections. Other clients of PostgreSQL (and I have a lot) never produce this messages.
I think that the fr sql code should be improved to make it more robust, specially in the reconnects. When it fails to do an insert (happens sometimes with fields too wide, timeouts due to the network, etc) it never does the insert right the second time. And then it does never try again. I know that in the case of malformed fields, like the username, it's going to fail again because postgres wont accept the >32 chars data, but in other cases it should.
But, what I can't explain is that running radiusd -X, I get some SQL_DOWN in places where shouldn't be. Im 100% sure that my SQL backend it's working properly. In all that cases, I lose a record.
I would send you any other information that you consider necesary in order to debug this
Thanks again
Guillermo
Peter Nixon wrote:
On Mon, 27 Jan 2003 07:30 pm, Guillermo Schimmel wrote:
Hi, I would like to exchange some experiences with somebody usingI also am using FreeRadius CVS + PostgreSQL 7.3 in a large installation and can possibly help you. Why don't you post your problem to the mailing list though. that way we can all have a stab at helping you.
freeradius with PostgreSQL.
That's because I'm having problems (I lose some records) and don't know
what to do. So I want to compare my setup which someone else's.
What sort of records are you losing? When? Are you seeing errors in radius.log? Do you see the same loss of records when running freeradius under debugging with SQL tracing turned on? If so have you tried to execute the failed SQL statements manually and checked the error that PG is returnng??
Answer all these questions, and you will probably find your problem.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
