Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vtysh failed to allocate 8589934528 bytes for Thread Poll Info object #15315

Closed
javier-godoy opened this issue Feb 6, 2024 · 1 comment · Fixed by #15320
Closed

vtysh failed to allocate 8589934528 bytes for Thread Poll Info object #15315

javier-godoy opened this issue Feb 6, 2024 · 1 comment · Fixed by #15320
Assignees
Labels
triage Needs further investigation

Comments

@javier-godoy
Copy link

Starting vtysh in a system with ulimit unlimited, results in a memory allocation error.
This case is different from #15280 because vtysh does not recognize --limit-fds

Hello, this is FRRouting (version 9.1).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

2024/02/06 20:42:47 out of memory: failed to allocate 8589934528 bytes for Thread Poll Info object
2024/02/06 20:42:47 No backtrace available on this platform.
log: showing active allocations in memory group vtysh
log: showing active allocations in memory group libfrr
log: memstats:  Buffer                        :      2 *         24
log: memstats:  Host config                   :      5 * (variably sized)
log: memstats:  Command Tokens                :   6250 *         72
log: memstats:  Command Token Text            :   4126 * (variably sized)
log: memstats:  Command Token Help            :   4126 * (variably sized)
log: memstats:  Command Argument Name         :   1262 * (variably sized)
log: memstats:  Graph                         :     26 *          8
log: memstats:  Graph Node                    :   7173 *         32
log: memstats:  Hash                          :     54 * (variably sized)
log: memstats:  Hash Bucket                   :   1650 *         32
log: memstats:  Hash Index                    :     27 * (variably sized)
log: memstats:  Link List                     :      4 *         40
log: memstats:  Link Node                     :     29 *         24
log: memstats:  Temporary memory              :      1 * (variably sized)
log: memstats:  Thread master                 :      2 * (variably sized)
log: memstats:  Vector                        :  14400 *         24
log: memstats:  Vector index                  :  14400 * (variably sized)
log: memstats:  VTY                           :      2 * (variably sized)
log: showing active allocations in memory group logging subsystem
Aborted (core dumped)

Versions
OS Version: Alpine Linux v3.19.1 dockerized on Rocky Linux 9.3 (Blue Onyx) / Docker version 24.0.7, build afdd53b
Kernel: 5.14.0-362.13.1.el9_3.x86_64
FRR Version: 9.1 configured with:

--enable-static' '--enable-static-bin' '--enable-shared' '--enable-numeric-version' '--disable-capabilities' '--disable-doc' '--disable-bgpd' '--disable-ripd' '--disable-ripngd' '--disable-ospf6d' '--disable-ldpd' '--disable-nhrpd' '--disable-babeld' '--disable-isisd' '--disable-pimd' '--disable-pbrd' '--disable-fabricd' '--disable-pathd' '--disable-bgp-announce' '--disable-bgp-vnc' '--disable-bgp-bmp' '--disable-rtadv' '--disable-irdp' '--bindir=/bin' '--sbindir=/lib/frr' '--sysconfdir=/etc/frr' '--libexecdir=/lib/frr' '--localstatedir=/var/run/frr' '--libdir=/lib/frr' '--with-moduledir=/lib/frr/modules' '--disable-dependency-tracking' '--enable-systemd=no' '--enable-vty-group=frrvty' 'SPHINXBUILD=/usr/bin/sphinx-build' 'PKG_CONFIG_PATH=/usr/lib64/pkgconfig'

@javier-godoy javier-godoy added the triage Needs further investigation label Feb 6, 2024
@mjstapp mjstapp self-assigned this Feb 7, 2024
@mjstapp
Copy link
Contributor

mjstapp commented Feb 7, 2024

I'll take a look

donaldsharp added a commit to donaldsharp/frr that referenced this issue Feb 7, 2024
There exists cases where just honoring the FD_LIMIT size
as given to us by the operating system makes no sense.
Let's just make a switch to allow for this for things
like vtysh and ospfclient which will never have 1k files
open at any given time.

Fixes: FRRouting#15315
Signed-off-by: Donald Sharp <[email protected]>
donaldsharp added a commit to donaldsharp/frr that referenced this issue Feb 7, 2024
There exists cases where just honoring the FD_LIMIT size
as given to us by the operating system makes no sense.
Let's just make a switch to allow for this for things
like vtysh and ospfclient which will never have 1k files
open at any given time.

Fixes: FRRouting#15315
Signed-off-by: Donald Sharp <[email protected]>
donaldsharp added a commit to donaldsharp/frr that referenced this issue Feb 7, 2024
There exists cases where just honoring the FD_LIMIT size
as given to us by the operating system makes no sense.
Let's just make a switch to allow for this for things
like vtysh and ospfclient which will never have 1k files
open at any given time.

Fixes: FRRouting#15315
Signed-off-by: Donald Sharp <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs further investigation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants