On Mon, Jan 02, 2012 at 12:43:45PM +0100, Henning Brauer wrote: > * Donald Reichert <[email protected]> [2012-01-02 08:04]: > > Watching the log file, I see sometimes lines like this: > > > > Jan 2 07:51:19 rt-beta bgpd[4344]: change req for 38.21.12.48/25: not in > > table > > > > I didn't find any clue what happens here; I found the part of source code, > > where 'change req for' can be seen, but I don't really understand what it's > > telling me. > > bgpd saw a route change message on the routing socket for said > destination. which means something changed said kernel route. > bgpd then figures out that it doesn't have such a route in its copy of > the kernel routing table. > now of course the question is why. could be a bug somewhere, could be > rdaomains related if you use them (speculation!), could be a missed > message on the routing socket. or sth else. >
You should try to figure out from where 38.21.12.48/25 is originating. Is it a connected, local (e.g. ospf) or external (bgp) route. I have seen errors like these when being so dumb and staring two bgpd instances at the same time. The two servers are then fighting over the same routing table and you will see quite a few of those or similar messages. -- :wq Claudio
