Re: Error: Dropping conflicting packet due to unfinished request
El mar, 17-05-2005 a las 10:19 -0400, Dustin Doris escribió: Perhaps your ldap server might be running a little slow. Are you using openldap? If so, what version? Also, do you have the attributes you are searching with indexed? Finally, if you are using a BDB backend, what does your DB_CONFIG file show? Yes, I have OpenLDAP, version 2.2.13, and I have all the attributes radius uses indexed. It may be a problem with my ldap server, but it run without any problem last 3 months. Problems appeared a week ago. Trying to solve the problem yesterday I increased the max_request_time, timeout and timelimit options. Since then, there isn't any problem (it's the first time in last week that radius is running more than 12 hours without problems) Another problem I have when the problem appears is that databases are corrupted. When the problem crash radius daemon, I have, not just, to restart it, but also I have to delete the db.ippool and db.ipindex files. If I restart it without deleting these files, radius runs with problem and dies after a little while. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA)/ \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
On Tue, 17 May 2005, Angel L. Mateo wrote: Hello, I run freeradius server (1.0.2) with ldap support in a debian sarge server. Last days I'm having the error message Error: Dropping conflicting packet due to unfinished request a lot of times and the server dies too frequently. I've seen in previous threads (http://lists.freeradius.org/archives/freeradius-users/2005/04/frm00119.html and http://lists.freeradius.org/archives/freeradius-users/2005/05/msg7.html) about this message related whith a bug in external commands, but I don't use any external command, I just use an ldap server as the users' database. Any idea? Perhaps your ldap server might be running a little slow. Are you using openldap? If so, what version? Also, do you have the attributes you are searching with indexed? Finally, if you are using a BDB backend, what does your DB_CONFIG file show? - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Dustin Doris wrote: I run freeradius server (1.0.2) with ldap support in a debian sarge server. Last days I'm having the error message Error: Dropping conflicting packet due to unfinished request a lot of times and the server dies too frequently. [...] Perhaps your ldap server might be running a little slow. Are you using openldap? If so, what version? Also, do you have the attributes you are searching with indexed? Finally, if you are using a BDB backend, what does your DB_CONFIG file show? I suppose that if you're seeing it lots of times, and it dies frequently, may be more related to LDAP and what Dustin tells you But I also add, that besides the external commands bug, I also saw some of those errors too, while NOT using external commands, which disappeared after upgrading to latest 1.0.x version form CVS. Regards, Juan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
[EMAIL PROTECTED] (Paul Hampson) wrote: Which's this fix? Revisions 1.83 through 1.87 of src/main/threads.c. The exec code was cleaned up, which means lots of garbage was deleted. The patches can be back-ported to 1.0.x, for a 1.0.3 release, but I'd really like to release 1.1.0 one of these days. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Juan Nin [EMAIL PROTECTED] wrote: Maybe we should back-port some fixes, and release 1.0.3. 1.1.0 is still a ways off, due to various craziness. that would be great! is this just an idea, or you've decided it? if so, any idea on aprox. realesa date for 1.0.3? :) Some time in the future. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Alan DeKok wrote: if so, any idea on aprox. realesa date for 1.0.3? :) Some time in the future. I really need to execute an external script I have another radius running freeradius-0.9.3 on other server which is executing external scripts, so I guess the bug wasn't present on previous versions would it be to crazy to downgrade? or should I use latest from CVS? is it stable for production? thanks again, Juan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Juan Nin [EMAIL PROTECTED] wrote: I have another radius running freeradius-0.9.3 on other server which is executing external scripts, so I guess the bug wasn't present on previous versions would it be to crazy to downgrade? I would suggest using the fixed code from CVS. You should be able to patch it into 1.0.2. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Juan Nin [EMAIL PROTECTED] wrote: I have another radius running freeradius-0.9.3 on other server which is executing external scripts, so I guess the bug wasn't present on previous versions would it be to crazy to downgrade? I would suggest using the fixed code from CVS. You should be able to patch it into 1.0.2. Alan DeKok. Is the same bug present in external programs when running with rlm_perl? Thanks - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Dustin Doris [EMAIL PROTECTED] wrote: Is the same bug present in external programs when running with rlm_perl? Hmm... I don't think so. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
On Thu, Apr 07, 2005 at 02:05:04PM -0400, Alan DeKok wrote: Juan Nin [EMAIL PROTECTED] wrote: also, another issue that worries me is that if I change my authentication method on /etc/raddb/users so as to be the following: Ah... That's a bug in the run external program code. It's fixed in the latest CVS snapshot. Which's this fix? I hit the same problem, but hadn't had a chance to debug it, but I can't see the change in CVS that either caused or fixed it. (It only started happening to me when I moved from my PPC machine to an i386 machine, so I was blaming NPTL for the problem and just rewrote around all my wait=yes rlm_exec modules) -- Paul TBBle Hampson, on an alternate email client. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
On Apr 4, 2005 10:14 PM, Alan DeKok [EMAIL PROTECTED] wrote: Mon Apr 4 12:15:58 2005 : Error: Dropping conflicting packet from client XXX:1645 - ID: 103 due to unfinished request 221 Your database is too slow, or your NAS is too fast. mmhhh, database seems ok, I'm not having performance issues with it... also, another issue that worries me is that if I change my authentication method on /etc/raddb/users so as to be the following: DEFAULT Auth-Type := Accept Exec-Program-Wait = /usr/local/php4/bin/php /path/to/script.php, Service-Type = Framed-User, Framed-Protocol = PPP, Fall-Through = 0 and script.php is just: ? exit(0); ? I start receiving the following similar errors: Thu Apr 7 19:05:43 2005 : Error: Discarding duplicate request from client XXX:1645 - ID: 139 due to unfinished request 73857 Thu Apr 7 19:05:53 2005 : Error: Discarding duplicate request from client XXX:1645 - ID: 139 due to unfinished request 73857 Thu Apr 7 19:06:36 2005 : Error: WARNING: Unresponsive child (id 1467612080) for request 73857 what may be happening?? It can't take long to execute that!!! should I run the radius in debug mode? is this suitable in production? any ideas?? thanks again, Juan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
On Apr 4, 2005 10:14 PM, Alan DeKok [EMAIL PROTECTED] wrote: Mon Apr 4 12:15:58 2005 : Error: Dropping conflicting packet from client XXX:1645 - ID: 103 due to unfinished request 221 Your database is too slow, or your NAS is too fast. mmhhh, database seems ok, I'm not having performance issues with it... also, another issue that worries me is that if I change my authentication method on /etc/raddb/users so as to be the following: DEFAULT Auth-Type := Accept Exec-Program-Wait = /usr/local/php4/bin/php /path/to/script.php, Service-Type = Framed-User, Framed-Protocol = PPP, Fall-Through = 0 and script.php is just: ? exit(0); ? I start receiving the following similar errors: Thu Apr 7 19:05:43 2005 : Error: Discarding duplicate request from client XXX:1645 - ID: 139 due to unfinished request 73857 Thu Apr 7 19:05:53 2005 : Error: Discarding duplicate request from client XXX:1645 - ID: 139 due to unfinished request 73857 Thu Apr 7 19:06:36 2005 : Error: WARNING: Unresponsive child (id 1467612080) for request 73857 what may be happening?? It can't take long to execute that!!! should I run the radius in debug mode? That may be helpful is this suitable in production? If its suitable to change the authentication method to test a php script, then its definately suitable to run in debug mode. I run in debug mode in production whenever there is an issue. If you're fast in killing the pid and starting in debug mode, then you won't lose any auth's. What does top show you? - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Juan Nin [EMAIL PROTECTED] wrote: also, another issue that worries me is that if I change my authentication method on /etc/raddb/users so as to be the following: Ah... That's a bug in the run external program code. It's fixed in the latest CVS snapshot. should I run the radius in debug mode? For running external programs, -f is good enough. is this suitable in production? Yes. Maybe we should back-port some fixes, and release 1.0.3. 1.1.0 is still a ways off, due to various craziness. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Alan DeKok wrote: also, another issue that worries me is that if I change my authentication method on /etc/raddb/users so as to be the following: Ah... That's a bug in the run external program code. It's fixed in the latest CVS snapshot. oh!!! well, I think it's a bit good news then :P For running external programs, -f is good enough. ok Maybe we should back-port some fixes, and release 1.0.3. 1.1.0 is still a ways off, due to various craziness. that would be great! is this just an idea, or you've decided it? if so, any idea on aprox. realesa date for 1.0.3? :) thanks again! Juan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Dustin Doris wrote: If its suitable to change the authentication method to test a php script, then its definately suitable to run in debug mode. I run in debug mode in production whenever there is an issue. If you're fast in killing the pid and starting in debug mode, then you won't lose any auth's. great What does top show you? load is fine, it's usually around 0.99 or 1.0, sometimes it goes a bit more than that it's a dual Xeon 2.4Ghz with 4GB of RAM, being used about 3.5GB of RAM - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Error: Dropping conflicting packet due to unfinished request
Juan Nin [EMAIL PROTECTED] wrote: I'm running freeradius 1.0.1, for authentication and accounting under Fedora Core 2. You should upgrade to 1.0.2. Mon Apr 4 12:15:58 2005 : Error: Dropping conflicting packet from client XXX:1645 - ID: 103 due to unfinished request 221 Your database is too slow, or your NAS is too fast. They are not many, but about 3 series like these appear every day. Then it's not a serious problem. I tried increasing max_request_time to 60 (it was on 30) and max_requests to 6400 (I've got 25 clients) on radiusd.conf, but that didn't solve it... That wouldn't affect anything. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
