Colmena | 298 Members | |
| A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena | 102 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Jan 2022 | ||
| After yet another nixops failure, I've tried colmena, but I'm stuck due to nix being killed?
how do I debug what's going on here | 09:29:33 | |
| I'm trying to build for aarch64-linux, on macOS. I do have a aarch64-linux builder in my machines file. | 09:32:30 | |
| 10:27:46 | ||
In reply to @angerman:matrix.orgInteresting, 11 is a segfault. What Nix version are you running? | 12:39:34 | |
| I’ll check in a bit. | 12:46:36 | |
| There is no way to see the raw nix commands Coleman is calling? | 12:47:02 | |
In reply to @angerman:matrix.org Not at the moment and I really should add a bunch of debug prints. You can manually evaluate from the repo with
| 12:53:51 | |
Zhaofeng Li: what I did try was -v2 but there seem to be no verbosity levels. | 13:34:24 | |
| If I run
I get
| 13:34:54 | |
| If I run it with the same pin I set in the meta.nixpkgs attribute I get the segfault. The pin is from 20.09 or so, so somewhat older. | 13:35:43 | |
| I'm not sure how that service.getty is getting in there though. | 13:36:07 | |
Your Nixpkgs is mixed (20.09 didn't have services.getty - it was mingetty or something) | 13:37:59 | |
| Let's first try invoking Nix manually and see if we can directly reproduce the segfault | 13:38:31 | |
| so the host nixpkgs & the target nixpgks need to align? | 13:38:41 | |
| There should just be one nixpkgs version. How are you pinning nixpkgs in your config? | 13:39:31 | |
meta.nixpkgs = import (fetchTarball { ... }); | 13:40:00 | |
with nixops, I used to just set NIX_PATH=nixpgks=<pin> | 13:40:19 | |
| NIX_PATH=nixpkgs=https://github.com/NixOs/nixpkgs/archive/65c9cc79f1d179713c227bf447fb0dac384cdcda.tar.gz:colmena=https://github.com/zhaofengli/colmena/archive/main.tar.gz nix-instantiate -E 'let eval = import <colmena/src/nix/hive/eval.nix>; hive = eval { rawHive = import ./hive.nix; }; in hive.nodes.helios64.config.system.build.toplevel' | 13:40:26 | |
* NIX_PATH=nixpkgs=https://github.com/NixOs/nixpkgs/archive/65c9cc79f1d179713c227bf447fb0dac384cdcda.tar.gz:colmena=https://github.com/zhaofengli/colmena/archive/main.tar.gz nix-instantiate -E 'let eval = import <colmena/src/nix/hive/eval.nix>; hive = eval { rawHive = import ./hive.nix; }; in hive.nodes.helios64.config.system.build.toplevel' keeps segfaulting | 13:40:35 | |
* NIX_PATH=nixpkgs=https://github.com/NixOs/nixpkgs/archive/65c9cc79f1d179713c227bf447fb0dac384cdcda.tar.gz:colmena=https://github.com/zhaofengli/colmena/archive/main.tar.gz nix-instantiate -E 'let eval = import <colmena/src/nix/hive/eval.nix>; hive = eval { rawHive = import ./hive.nix; }; in hive.nodes.helios64.config.system.build.toplevel' keeps segfaulting | 13:40:41 | |
last thing it prints prior to segfaulting is evaluating file '/nix/store/0gqvlf61cyjavvalfql96jxykrf0q0nb-source/pkgs/build-support/kernel/modules-closure.nix'. | 13:41:03 | |
| GC_DONT_GC... | 13:41:51 | |
| god i hate this nix binary. | 13:41:55 | |
In reply to @angerman:matrix.orgWith this there <nixpkgs> in NIX_PATH shouldn't have matterered, but apparently something in the config is trying to use <nixpkgs>. But I think that's a red herring | 13:41:57 | |
| 13:42:16 | |
In reply to @angerman:matrix.orgIf you can get a backtrace, that may be valuable in submitting an issue upstream to Nix | 13:42:17 | |
nix (Nix) 2.5pre20211007_844dd90 | 13:42:41 | |
| I guess I could break out my debugger now, and figure out why the GC keeps failing... or I'll just use GC_DONT_GC for now, and ignore the failure. | 13:43:12 | |
In reply to @angerman:matrix.orgAh, I didn't know about https://github.com/NixOS/nix/issues/4893 | 13:44:03 | |
| Yeah, that is indeed pretty annoying 🙁 | 13:44:28 | |