On Sun, Feb 22, 2009 at 10:52, Vianney Lejeune <via....@free.fr> wrote: >>> >> Hi, >> >> Thanks for the report and sorry for the delay in replying. Do you >> always experience any similar slowdown as the OP described near the same >> time this message is printed ? Are you both handling the same multiple >> requests at the same time ? Is it easy to reproduce, and if so is there >> any anomalous mapping (present or absent) afterwards ? >> >> Thanks >> >> Nick > >> > > Hi, > > The problem is I use upnpd on a gateway (250 computers). Various > softwares use upnp, so I don't know if there are multiple requests as the > same time, neither slowdowns. It happens sometimes according to the joined > logfile. > I can conduct some tests if you want to, provided I can get the tools. > > Regards, > Mr Lejeune
My setup is rather similar. A gateway for 100 home and business computers running all kinds of different software. When I reported the bug, my gateway would run fine for maybe a week, before becoming very unresponsive. A reboot would then help. I gave up on running upnpd, and the problem disappeared. I am still not quite certain what actually happened. My guess is that upnpd caused 100% cpu use, starving the other running processes. My machine is an otherwise lightly loaded 500 MHz box. But even if my guess is correct, I cannot say whether the slowdown is related to this error message. I just seized on the error message as something more tangible than the slowdown. As you can probably guess, this is not easy to reproduce for me. I cannot leave the gateway running in a likely-to-break configuration for weeks at a time. Rune -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org