* Claudio Jeker ([EMAIL PROTECTED]) wrote: > On Mon, Mar 12, 2007 at 11:14:29AM +0100, Claudio Jeker wrote: > > On Sun, Mar 11, 2007 at 11:43:03PM +0000, Jon Morby wrote: > > > I've noticed since updating to current from 4.0-current in January to > > > -current "now" that certain commands through bgpctl seem to just > > > hang .. (we've tried this with various snapshots every 2 weeks or so > > > since January) as well as trying a full build. > > > > > > If I do a bgpctl reload (100+ peers per production router) and then > > > within a minute or so do a "bgpctl show" then bgpctl's output just > > > hangs (I've left it for nearly an hour and nothing has appeared > > > beyond the headers) > > > > > > > Hmm. That's strange. Does it work after waiting a longer time? > > bgpctl show can block for some extended time (if the RDE is busy) but you > > should get a result back. > > > > > Also regardless of a reload, attempting to show rib nei a.b.c.d out > > > also just seems to hang > > > > > > bgpctl show rib nei 80.252.124.1 out > > > flags: * = Valid, > = Selected, I = via IBGP, A = Announced > > > origin: i = IGP, e = EGP, ? = Incomplete > > > > > > flags destination gateway lpref med aspath origin > > > > > > and no more output > > > > > > > You're right we have a polling issue here. I'm looking into it. > > In short, the RDE blocks and does not continue to process the show command > > until an update or some other message was received because the current > > batch of work did not queue any outgoing imsgs. The poll(2) timeout needs > > to be changed to 0 in this case. > > > > ... and here is the patch to fix the issue. > > -- > :wq Claudio >
<snip> That patch did not fix the issue for me(running 4.1 with -current bgpd). There is almost no load on the box. # time bgpctl sh rib out <snip> Takes forever, 10+ minutes. However, if I open another terminal and type: # bgpctl sh rib in The sh rib out will finnish almost instantly and the rib in will finnish in less then a second. The output of sh rib out is not what I'd expect though. The networks I've defined in my config will be show twice(that is true even if I'm not speeding things up with the sh rib in). If any patch gets sent to the list I will probably not have time to test it before the end of the weekend. Regards Andreas Lundin
