"Dropping conflicting packet" and "Rejecting request"
I am moving FreeRadius(1.1.0 Sparc Solaris9) by the following compositions. (Target is "* Proxy *") ------------ --------------- | Radius-1 |--> -->| HomeRadius1 |---RDB ------------ | ----------- | --------------- |-->|* Proxy *|-->| ------------ | ----------- | --------------- | Radius-2 |--> -->| HomeRadius2 |---RDB ------------ --------------- The role of this server is only a Proxy server. The occasionally following errors are output by "radius.log" Wed Feb 22 11:53:38 2006 : Error: Dropping conflicting packet from client Radus-1:1039 - ID: 246 due to unfinished request 7101301 and Wed Feb 22 11:53:38 2006 : Error: Rejecting request 7101299 due to lack of any response from home server Radius-1:1039 Why are these messages output? The number of requests that *Proxy* receive is AUTH=10 and ACCT=15 in about one second. It is a setting as follows. --- radiusd.conf --- max_request_time = 12 delete_blocked_requests = no cleanup_delay = 6 max_requests = 20480 hostname_lookups = no reject_delay = 3 proxy_requests = yes --- proxy.conf --- proxy server { synchronous = no retry_delay = 0 retry_count = 0 dead_time = 60 default_fallback = yes post_proxy_authorize = no } When the examination on which I put the load is done, this error is fully output. However, it is output when the load is low. There is always one kind of UDP transmission Port of "Radius-1" and "Radius-2". (It is not unique at each request. ) Because this server is being operated, it is not possible to do in debug mode. Please give something a good idea to me. I'm sorry in strange English. My best regards. ######################################### # # # Takeshi Yoshida # # # ######################################### --------------------------------- TSUKAME EIKOU! KAGAYAKE EGAO! Yahoo! JAPAN JPC OFFICIAL PARTNER INTERNET PORTAL SITE
Takeshi Yoshida <ducati_monster_400@yahoo.co.jp> wrote:
Wed Feb 22 11:53:38 2006 : Error: Dropping conflicting packet from client Radus-1:1039 - ID: 246 due to unfinished request 7101301
This means that the NAS sent a new packet while the server was in the middle of processing an old one. The reason is usually that the database or home server is taking too long to respond to FreeRADIUS.
When the examination on which I put the load is done, this error is fully output. However, it is output when the load is low.
I would look at the home RADIUS servers and/or databases to see why they're taking more than 1/10s to respond to a RADIUS request. It looks like they're taking 30s or more, which is very bad. And the server that logs these messages is *not* responsible for the problem, and there's little you can change on it to fix the problem. Alan DeKok.
participants (2)
-
Alan DeKok -
Takeshi Yoshida