From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] nix-channel --update crashes on musl
Date: Thu, 20 Jul 2023 00:06:08 +0200 [thread overview]
Message-ID: <20230719220608.arYcNLMJr65tp6pZOEBaGKiojNZKK7VG0eSyICciNts@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37382@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
Closed issue by loreb on void-packages repository
https://github.com/void-linux/void-packages/issues/37382
Description:
<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
### System
* xuname:
Void 5.10.117_1 x86_64-musl GenuineIntel uptodate rFFF
* package:
nix-2.8.1_1
### Expected behavior
It works as usual
### Actual behavior
```
$ nix-channel --update
unpacking channels...
RT34
$ echo $?
162
$ strace nix-channel --update
(...)
vfork()
+++ killed by SIGRT_2 +++
RT34
```
### Steps to reproduce the behavior
Run the above on a musl machine.
To make it more interesting, if you stop the nix-daemon service,
log in as root, and run /etc/sv/nix-daemon/run by hand the behavior changes:
nix-daemon starts to spew many, many, *many* messages saying that it accepted a connection from $pid until it runs out of memory while keeping tens of thousands of nix-daemon processes alive (or zombies?); I have no idea if adding substantially more memory would help, but I know at least that this used to work before.
The bug happens the exact same way with the newly released 2.9.0 (I believe - I had to fiddle with the `--with-sandbox-shell` option to get it to compile for some reason).
`grep -R SIGRT` in the nix sources doesn't return any result, so I guess it's in some dependency (boost?)
Any help is greatly appreciated.
edit:
it makes no difference on my machine (or a vm), but in case you've never used nix before,
you're supposed to first enable the nix-daemon service and then,
as an unprivileged user, subscribe to a nix channel (`nix-channel --add https://nixos.org/channels/nixpkgs-unstable`) before trying to update.
AND maybe do it from a fresh login to pick up on /etc/profile.d/nix*.sh
prev parent reply other threads:[~2023-07-19 22:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 12:19 [ISSUE] " loreb
2022-06-10 21:49 ` paper42
2022-06-11 12:37 ` loreb
2022-10-31 10:57 ` xiarenfan
2022-11-02 12:59 ` loreb
2022-11-03 0:27 ` xiarenfan
2022-11-03 12:30 ` loreb
2023-06-03 20:35 ` vincele
2023-06-03 20:43 ` vincele
2023-06-03 21:17 ` vincele
2023-06-03 21:18 ` vincele
2023-06-03 21:19 ` vincele
2023-06-03 21:19 ` vincele
2023-06-03 21:27 ` vincele
2023-06-04 7:10 ` vincele
2023-06-05 14:31 ` loreb
2023-06-05 15:07 ` vincele
2023-06-05 15:12 ` vincele
2023-06-05 15:17 ` vincele
2023-06-05 15:18 ` vincele
2023-06-05 15:25 ` vincele
2023-06-05 16:23 ` loreb
2023-06-23 15:18 ` loreb
2023-07-17 13:56 ` loreb
2023-07-17 14:08 ` classabbyamp
2023-07-17 14:08 ` classabbyamp
2023-07-17 14:42 ` loreb
2023-07-17 15:50 ` loreb
2023-07-19 22:06 ` classabbyamp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230719220608.arYcNLMJr65tp6pZOEBaGKiojNZKK7VG0eSyICciNts@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).