Open jjzazuet opened 2 months ago
It is likely the same cause as #811 but given your error is different we cannot be for sure. When #811 is fixed you should definitely retest.
One more crash occurrence today with latest netavark
build in case it helps:
ul 15 22:16:10 build-00 user.notice dhcp-proxy: thread 'thread 'tokio-runtime-worker<unnamed>' panicked at ' panicked at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/thread/mod.rslibrary/std/src/sys/pal/unix/stack_overflow.rs::683168::2913:
Jul 15 22:16:10 build-00 user.notice dhcp-proxy: :
Jul 15 22:16:10 build-00 user.notice dhcp-proxy: failed to spawn thread: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }failed to set up alternative stack guard page: Out of memory (os error 12)
Jul 15 22:16:10 build-00 user.notice dhcp-proxy: stack backtrace:
Jul 15 22:16:10 build-00 user.notice dhcp-proxy: memory allocation of 3072 bytes failed
Jul 15 22:16:11 build-00 daemon.err /etc/init.d/netavark-dhcp-proxy[17725]: start-stop-daemon: failed to start `/opt/netavark'
Jul 15 22:16:11 build-00 user.notice dhcp-proxy: * start-stop-daemon: failed to start `/opt/netavark'
Thanks!
Hi, I have a few standalone containers running under podman, using a
macvlan
network to make them available to an internal LAN network. I'm observing the following:1: Every time the external router assigns a DHCP host configuration to a container,
netavark
logs this message:2: Every week or so I will get a hard crash on
netavark
with the following logs, and the container will no longer be reachable at the static IP lease addresses:I just tried building and upgrading to the latest upstream version of
netavark
, but I'm seeing the same log messages. I'll wait to see if I get a crash with this version.Let me know if more info is needed. Thanks!