On Tue, Nov 30, 2010 at 08:35:46AM +0100, Xavier Beaudouin wrote:
> Hello,
>
> I have updated a openbgpd router from OpenBSD 4.7 i386 to 4.8 amd64.
>
> Now I have new instability like this :
>
> Nov 29 21:25:22 core-3 bgpd[28895]: fatal in RDE: path_alloc: Cannot allocate
> memory
> Nov 30 02:01:47 core-3 bgpd[5522]: fatal in RDE: up_generate: Cannot allocate
> memory
>
> I have 2Gb on this machine and login.conf like this :
>
> default:\
> :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin:\
> :umask=022:\
> :datasize-max=1512M:\
> :datasize-cur=1024M:\
> :maxproc-max=2048:\
> :maxproc-cur=1024:\
> :openfiles-cur=1024:\
> :stacksize-cur=4M:\
> :localcipher=blowfish,6:\
> :ypcipher=old:\
> :tc=auth-defaults:\
> :tc=auth-ftp-defaults:
>
> This currently make me mad, because this router handle more than 130 peers and
> is still unstable.
>
> What is needed to make openbgpd work as it should and shuttup ?
>
> (I am going to add a monit... because on production day this is not
> acceptable).
>
> Xavier
By default daemons run in the daemon login class. Check that, also
check if you do not have stale /etc/login.conf.db file lying around.
AFAIK I know, bgpd does not increase its limits to the max, so it does
not make sense to have different values for -max and -cur.
If these things don't help, analyzing this requires some specific bgpd
knowledge, which I do not have.
-Otto
