Uploaded image for project: 'Container Tools'
  1. Container Tools
  2. RUN-2720

[containers/netavark] Thread leak in netavark-dhcp-proxy

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • netavark
    • 8
    • False
    • Hide

      None

      Show
      None
    • False
    • rhel-container-tools
    • RUN 271

      [1901222282] Upstream Reporter: Joerg Sonnenberger
      Upstream issue status: Closed
      Upstream description:

      Using SuSE MicroOS with a bunch of macvlan-using containers, I see netvark-dhcp-proxy hanging every few days. From journalctl:

      netavark[14606]: thread 'tokio-runtime-worker' panicked at 'failed to spawn thread: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', /home/abuild/rpmbuild/BUILD/rustc-1.71.1-src/library/std/src/thread/mod.rs:686:29

      Even with RUST_BACKTRACE=1 set, it doesn't give a backtrace. Last time this happened, ps reported over 4000 threads for the PID.


      Upstream URL: https://github.com/containers/netavark/issues/811

              Unassigned Unassigned
              upstream-sync Upstream Sync
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: