oxidecomputer / oxidecomputer/propolis

Propolis panic during zone uninstall

Open
#827 9 comments 0 reactions 1 assignee View on GitHub

@iximeow is already working on this.

Since Jan 19, 2026.

Dominant language
Rust
Stars
270
Forks
42
Avg merge
4d 5h
Merged PRs (30d)
6

Description

I found two sets of propolis core files on a certain sled after running the "parking" script that halted and uninstalled all zones on the sled.

Here are the core files of two specific propolis zones - there are 5 occurrences for each of them:

root@oxz_switch0:~# pilot host exec -c 'ls -lh /pool/*/*/crypt/debug/core\.* || true' 0-31
 7  BRM27230045        ok: 
 8  BRM44220011        ok: 
 9  BRM44220005        ok: -rw-r--r--   1 root     root        309M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_0807fc69-c1ad-4768-9cb6-9c54746b36d5.propolis-server.14698.1734168037
-rw-r--r--   1 root     root       69.4M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_0807fc69-c1ad-4768-9cb6-9c54746b36d5.propolis-server.18482.1734168039
-rw-r--r--   1 root     root       69.4M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_0807fc69-c1ad-4768-9cb6-9c54746b36d5.propolis-server.18516.1734168040
-rw-r--r--   1 root     root       69.4M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_0807fc69-c1ad-4768-9cb6-9c54746b36d5.propolis-server.18551.1734168040
-rw-r--r--   1 root     root       69.4M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_0807fc69-c1ad-4768-9cb6-9c54746b36d5.propolis-server.18571.1734168041
-rw-r--r--   1 root     root        186M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_75e401d6-7502-4231-b30c-b2bfa32a1a6f.propolis-server.18383.1734168037
-rw-r--r--   1 root     root       69.4M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_75e401d6-7502-4231-b30c-b2bfa32a1a6f.propolis-server.18453.1734168038
-rw-r--r--   1 root     root       69.4M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_75e401d6-7502-4231-b30c-b2bfa32a1a6f.propolis-server.18487.1734168039
-rw-r--r--   1 root     root       69.4M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_75e401d6-7502-4231-b30c-b2bfa32a1a6f.propolis-server.18521.1734168040
-rw-r--r--   1 root     root       69.4M Dec 14  2024 /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_75e401d6-7502-4231-b30c-b2bfa32a1a6f.propolis-server.18554.1734168040
10  BRM42220009        ok: 
...

The stacks appear identical and here is one of them:

BRM44220005 # mdb /pool/ext/f8b11629-ced6-412a-9c3f-d169b99ee996/crypt/debug/core.oxz_propolis-server_75e401d6-7502-4231-b30c-b2bfa32a1a6f.propolis-server.18554.1734168040
Loading modules: [ libumem.so.1 libnvpair.so.1 libc.so.1 ld.so.1 ]
> $C ! demangle
fffff5ffeddffa20 libc.so.1`_lwp_kill+0xa()
fffff5ffeddffa50 libc.so.1`raise+0x22(6)
fffff5ffeddffaa0 libc.so.1`abort+0x58()
fffff5ffeddffab0 0x28c9ab9()
fffff5ffeddffac0 0x28c9aa9()
fffff5ffeddffb20 rust_panic+0xd()
fffff5ffeddffbe0 std::panicking::rust_panic_with_hook::h503ea5292ea6f2f4+0x231()
fffff5ffeddffc20 std::panicking::begin_panic_handler::{{closure}}::h2eb8efd06bcdc46a+0x98()
fffff5ffeddffc30 0x28b0699()
fffff5ffeddffc60 0x28b2d3c()
fffff5ffeddffc90 0x28f7f6f()
fffff5ffeddffd70 0xf881f7()
fffff5ffeddffee0 std::sys::backtrace::__rust_begin_short_backtrace::h68463c8dc06c772b+0xd6()
fffff5ffeddfff60 core::ops::function::FnOnce::call_once{{vtable.shim}}::hc5463a0161650b1d+0xa3()
fffff5ffeddfffb0 std::sys::pal::unix::thread::Thread::new::thread_start::he13a45effb26dfc6+0x2b()
fffff5ffeddfffe0 libc.so.1`_thrp_setup+0x77(fffff5ffeef30240)
fffff5ffeddffff0 libc.so.1`_lwp_start()

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.