daemon dumps core on unexpected disconnection #571
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#571
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
My nix-deamon crashed while building my system.
Steps To Reproduce
I don't remember what I was doing exactly when the coredump occurred, I saw it when randomly reading my systemd-journal.
nix --version
outputnix (Lix, like Nix) 2.91.1
coredump message
Command Line: nix-daemon 71942
Executable: /nix/store/n99cjrvzmw28v6vy6nbkcp0niwvlhwnb-lix-2.91.1/bin/nix
Control Group: /system.slice/nix-daemon.service
Unit: nix-daemon.service
Slice: system.slice
Boot ID: aa4f83a64d494119aa2e2247befbbebf
Machine ID: 9498cd0c1ff74b9eac48ce3bc55bcd99
Hostname: kat-probook
Storage: /var/lib/systemd/coredump/core.nix-daemon.0.aa4f83a64d494119aa2e2247befbbebf.71944.1730456422000000.zst (present) // you can download it here
Size on Disk: 1.3M
Message: Process 71944 (nix-daemon) of user 0 dumped core.
nix-deamon coredumpedto daemon dumps core on unexpected disconnectionI'm pretty sure we should have other instances of this bug but it's basically that the daemon handles surprise disconnections poorly and winds up dumping core due to throwing while an exception is being handled.
It is a bug that it's dumping core but it is relatively harmless.
aha yes okay there was a reason i was familiar with this: #123 (comment)
let's keep this report open because we should fix the double throw in the future.
I suspect this might have been fixed by https://gerrit.lix.systems/c/lix/+/2086 or similar exception handling work I did in 2.92-dev?
The reproducer is to take a broken client that aborts the connection (2.90 works) and then run the example from #123 against a newer daemon. The 2.91 daemon crashes, the 2.92-dev daemon no longer crashes.