On Tue, May 29, 2012 at 08:57:54AM +0000, Matt Hamilton wrote:
> Hi all,
>
> More bgpd problems last night :( This happened last night on two of our
> routers. One running an old version of OpenBSD (4.3) and one running
> 5.1. Is there anyone out there actually using bpgd in production? How
> do you deal with it quitting everytime something unexpected happens on
> the network?
Yes, lots of people run it in production.
>
> The first message below seems to indicate unable to allocate
> memory. I'm running these boxes pretty much stock having not tuned any
> parameters at all. Both are just running routing daemons (bgpd, ospf)
> and the 4.3 box is running OpenVPN. There are no applications running
> and both boxes have plenty of RAM (4GB) and not using any swap or
> anything.
>
> Is there something I should look at tuning in terms
> of memory allocation in order to stop this happening?
>
> OpenBSD 4.3/amd64:
>
> May 29 05:53:43 firewall1 bgpd[5090]: imsg_create: buf_open: Cannot
> allocate memory
> May 29 05:53:43 firewall1 bgpd[5090]: fatal in RDE: imsg_compose
> error: Cannot allocate memory
> May 29 05:53:44 firewall1 bgpd[27053]: Lost child: route decision
> engine exited
> May 29 05:53:44 firewall1 bgpd[15204]: fatal in SE: pipe write error:
> Broken pipe
Only solution: upgrading. You are runing unsupported software, a
foolish thing to do.
>
> OpenBSD 5.1/amd64:
>
> May 29 05:55:09 fw1 bgpd[21316]: Lost child: route decision engine
> terminated; signal 11
> May 29 05:55:09 fw1 bgpd[21459]: fatal in SE: pipe write error: Broken
> pipe
This is a real issue. I'll leave this one to people more experienced
running bgpd.
-Otto
