| 3 Dec 2023 |
 @sivertism:matrix.org | ah, you're right! I thought I had done that, but I hadn't.
Got a spicier error message this time though
[nixos@desktop:~/nixos-home]$ colmena apply --on surface
warning: Git tree '/home/nixos/nixos-home' is dirty
[INFO ] Using flake: git+file:///home/nixos/nixos-home
[INFO ] Enumerating nodes...
[INFO ] Selected 1 out of 3 hosts.
❌ 25s Failed: Child process exited with error code: 4
surface ✅ 11s Evaluated surface
surface ✅ 0s Built "/nix/store/nzpx3si3lnw205sdd4vcvkh74b8blvx4-nixos-system-surface-24.05pre-git"
surface ✅ 3s Pushed system closure
surface ❌ 11s Activation failed: Child process exited with error code: 4
[ERROR] Failed to deploy to surface - Last 20 lines of logs:
[ERROR] stderr) restarting the following units: dev-hugepages.mount, nix-daemon.service, polkit.service, sshd.service, systemd-journald.service
[ERROR] stderr) starting the following units: ModemManager.service, NetworkManager-wait-online.service, NetworkManager.service, accounts-daemon.service, alsa-store.service, audit.service, avahi-daemon.socket, bluetooth.service, colord.service, cpufreq.service, cups-browsed.service, cups.socket, kmod-static-nodes.service, logrotate-checkconf.service, mount-pstore.service, network-local-commands.service, network-setup.service, nscd.service, power-profiles-daemon.service, resolvconf.service, rtkit-daemon.service, systemd-machined.service, systemd-modules-load.service, systemd-oomd.socket, systemd-sysctl.service, systemd-timesyncd.service, systemd-tmpfiles-setup-dev.service, systemd-udevd-control.socket, systemd-udevd-kernel.socket, udisks2.service, upower.service, wpa_supplicant.service
[ERROR] stderr) the following new units were started: NetworkManager-dispatcher.service, fstrim.timer, systemd-hostnamed.service, systemd-tmpfiles-setup-dev-early.service, systemd-vconsole-setup.service
[ERROR] stderr) warning: the following units failed: iptsd.service
[ERROR] stderr)
[ERROR] stderr) × iptsd.service - IPTSD
[ERROR] stderr) Loaded: loaded (/etc/systemd/system/iptsd.service; enabled; preset: enabled)
[ERROR] stderr) Active: failed (Result: exit-code) since Sun 2023-12-03 17:17:38 CET; 3s ago
[ERROR] stderr) Duration: 295ms
[ERROR] stderr) Process: 3490 ExecStart=/nix/store/a2vzhri5pmfs83fpwcngm4inwk2ww7yj-unit-script-iptsd-start/bin/iptsd-start (code=exited, status=106)
[ERROR] stderr) Main PID: 3490 (code=exited, status=106)
[ERROR] stderr) IP: 0B in, 0B out
[ERROR] stderr) CPU: 99ms
[ERROR] stderr)
[ERROR] stderr) Dec 03 17:17:37 surface systemd[1]: Started IPTSD.
[ERROR] stderr) Dec 03 17:17:38 surface iptsd-start[3619]: DEVICE is required
[ERROR] stderr) Dec 03 17:17:38 surface iptsd-start[3619]: Run with --help for more information.
[ERROR] stderr) Dec 03 17:17:38 surface systemd[1]: iptsd.service: Main process exited, code=exited, status=106/n/a
[ERROR] stderr) Dec 03 17:17:38 surface systemd[1]: iptsd.service: Failed with result 'exit-code'.
[ERROR] failure) Child process exited with error code: 4
[ERROR] Failed to complete requested operation - Last 1 lines of logs:
[ERROR] failure) Child process exited with error code: 4
[ERROR] -----
[ERROR] Operation failed with error: Child process exited with error code: 4
Hint: Backtrace available - Use `RUST_BACKTRACE=1` environment variable to display a backtrace
| 16:19:17 |
| @sivertism:matrix.org | In reply to @sivertism:matrix.org
ah, you're right! I thought I had done that, but I hadn't.
Got a spicier error message this time though
[nixos@desktop:~/nixos-home]$ colmena apply --on surface
warning: Git tree '/home/nixos/nixos-home' is dirty
[INFO ] Using flake: git+file:///home/nixos/nixos-home
[INFO ] Enumerating nodes...
[INFO ] Selected 1 out of 3 hosts.
❌ 25s Failed: Child process exited with error code: 4
surface ✅ 11s Evaluated surface
surface ✅ 0s Built "/nix/store/nzpx3si3lnw205sdd4vcvkh74b8blvx4-nixos-system-surface-24.05pre-git"
surface ✅ 3s Pushed system closure
surface ❌ 11s Activation failed: Child process exited with error code: 4
[ERROR] Failed to deploy to surface - Last 20 lines of logs:
[ERROR] stderr) restarting the following units: dev-hugepages.mount, nix-daemon.service, polkit.service, sshd.service, systemd-journald.service
[ERROR] stderr) starting the following units: ModemManager.service, NetworkManager-wait-online.service, NetworkManager.service, accounts-daemon.service, alsa-store.service, audit.service, avahi-daemon.socket, bluetooth.service, colord.service, cpufreq.service, cups-browsed.service, cups.socket, kmod-static-nodes.service, logrotate-checkconf.service, mount-pstore.service, network-local-commands.service, network-setup.service, nscd.service, power-profiles-daemon.service, resolvconf.service, rtkit-daemon.service, systemd-machined.service, systemd-modules-load.service, systemd-oomd.socket, systemd-sysctl.service, systemd-timesyncd.service, systemd-tmpfiles-setup-dev.service, systemd-udevd-control.socket, systemd-udevd-kernel.socket, udisks2.service, upower.service, wpa_supplicant.service
[ERROR] stderr) the following new units were started: NetworkManager-dispatcher.service, fstrim.timer, systemd-hostnamed.service, systemd-tmpfiles-setup-dev-early.service, systemd-vconsole-setup.service
[ERROR] stderr) warning: the following units failed: iptsd.service
[ERROR] stderr)
[ERROR] stderr) × iptsd.service - IPTSD
[ERROR] stderr) Loaded: loaded (/etc/systemd/system/iptsd.service; enabled; preset: enabled)
[ERROR] stderr) Active: failed (Result: exit-code) since Sun 2023-12-03 17:17:38 CET; 3s ago
[ERROR] stderr) Duration: 295ms
[ERROR] stderr) Process: 3490 ExecStart=/nix/store/a2vzhri5pmfs83fpwcngm4inwk2ww7yj-unit-script-iptsd-start/bin/iptsd-start (code=exited, status=106)
[ERROR] stderr) Main PID: 3490 (code=exited, status=106)
[ERROR] stderr) IP: 0B in, 0B out
[ERROR] stderr) CPU: 99ms
[ERROR] stderr)
[ERROR] stderr) Dec 03 17:17:37 surface systemd[1]: Started IPTSD.
[ERROR] stderr) Dec 03 17:17:38 surface iptsd-start[3619]: DEVICE is required
[ERROR] stderr) Dec 03 17:17:38 surface iptsd-start[3619]: Run with --help for more information.
[ERROR] stderr) Dec 03 17:17:38 surface systemd[1]: iptsd.service: Main process exited, code=exited, status=106/n/a
[ERROR] stderr) Dec 03 17:17:38 surface systemd[1]: iptsd.service: Failed with result 'exit-code'.
[ERROR] failure) Child process exited with error code: 4
[ERROR] Failed to complete requested operation - Last 1 lines of logs:
[ERROR] failure) Child process exited with error code: 4
[ERROR] -----
[ERROR] Operation failed with error: Child process exited with error code: 4
Hint: Backtrace available - Use `RUST_BACKTRACE=1` environment variable to display a backtrace
Just needed a reboot. Works like a charm now. Touch and everything 🥳
Thanks a lot for the help ibizaman !
| 16:24:47 |
 ibizaman | The error is weird indeed. Glad we made it work!
| 17:20:18 |
| ibizaman | * The error is weird indeed. Glad we made it work! | 17:20:39 |
 Zhaofeng Li | In reply to @sivertism:matrix.org
ah, you're right! I thought I had done that, but I hadn't.
Got a spicier error message this time though
[nixos@desktop:~/nixos-home]$ colmena apply --on surface
warning: Git tree '/home/nixos/nixos-home' is dirty
[INFO ] Using flake: git+file:///home/nixos/nixos-home
[INFO ] Enumerating nodes...
[INFO ] Selected 1 out of 3 hosts.
❌ 25s Failed: Child process exited with error code: 4
surface ✅ 11s Evaluated surface
surface ✅ 0s Built "/nix/store/nzpx3si3lnw205sdd4vcvkh74b8blvx4-nixos-system-surface-24.05pre-git"
surface ✅ 3s Pushed system closure
surface ❌ 11s Activation failed: Child process exited with error code: 4
[ERROR] Failed to deploy to surface - Last 20 lines of logs:
[ERROR] stderr) restarting the following units: dev-hugepages.mount, nix-daemon.service, polkit.service, sshd.service, systemd-journald.service
[ERROR] stderr) starting the following units: ModemManager.service, NetworkManager-wait-online.service, NetworkManager.service, accounts-daemon.service, alsa-store.service, audit.service, avahi-daemon.socket, bluetooth.service, colord.service, cpufreq.service, cups-browsed.service, cups.socket, kmod-static-nodes.service, logrotate-checkconf.service, mount-pstore.service, network-local-commands.service, network-setup.service, nscd.service, power-profiles-daemon.service, resolvconf.service, rtkit-daemon.service, systemd-machined.service, systemd-modules-load.service, systemd-oomd.socket, systemd-sysctl.service, systemd-timesyncd.service, systemd-tmpfiles-setup-dev.service, systemd-udevd-control.socket, systemd-udevd-kernel.socket, udisks2.service, upower.service, wpa_supplicant.service
[ERROR] stderr) the following new units were started: NetworkManager-dispatcher.service, fstrim.timer, systemd-hostnamed.service, systemd-tmpfiles-setup-dev-early.service, systemd-vconsole-setup.service
[ERROR] stderr) warning: the following units failed: iptsd.service
[ERROR] stderr)
[ERROR] stderr) × iptsd.service - IPTSD
[ERROR] stderr) Loaded: loaded (/etc/systemd/system/iptsd.service; enabled; preset: enabled)
[ERROR] stderr) Active: failed (Result: exit-code) since Sun 2023-12-03 17:17:38 CET; 3s ago
[ERROR] stderr) Duration: 295ms
[ERROR] stderr) Process: 3490 ExecStart=/nix/store/a2vzhri5pmfs83fpwcngm4inwk2ww7yj-unit-script-iptsd-start/bin/iptsd-start (code=exited, status=106)
[ERROR] stderr) Main PID: 3490 (code=exited, status=106)
[ERROR] stderr) IP: 0B in, 0B out
[ERROR] stderr) CPU: 99ms
[ERROR] stderr)
[ERROR] stderr) Dec 03 17:17:37 surface systemd[1]: Started IPTSD.
[ERROR] stderr) Dec 03 17:17:38 surface iptsd-start[3619]: DEVICE is required
[ERROR] stderr) Dec 03 17:17:38 surface iptsd-start[3619]: Run with --help for more information.
[ERROR] stderr) Dec 03 17:17:38 surface systemd[1]: iptsd.service: Main process exited, code=exited, status=106/n/a
[ERROR] stderr) Dec 03 17:17:38 surface systemd[1]: iptsd.service: Failed with result 'exit-code'.
[ERROR] failure) Child process exited with error code: 4
[ERROR] Failed to complete requested operation - Last 1 lines of logs:
[ERROR] failure) Child process exited with error code: 4
[ERROR] -----
[ERROR] Operation failed with error: Child process exited with error code: 4
Hint: Backtrace available - Use `RUST_BACKTRACE=1` environment variable to display a backtrace
Looks like the iptsd setup in nixos-hardware does script = "iptsd $(iptsd-find-hidraw)";
https://github.com/NixOS/nixos-hardware/blob/a89745edd5f657e2e5be5ed1bea86725ca78d92e/microsoft/surface/common/ipts/default.nix#L42
| 17:31:50 |
| Zhaofeng Li | If you don't have the driver, then iptsd-find-hidraw presumably returns nothing | 17:32:15 |
| Zhaofeng Li | hence "DEVICE is required" | 17:32:34 |
| @sivertism:matrix.org | Ah, that makes sense. Thanks! | 18:00:45 |
| 4 Dec 2023 |
| ibizaman | Sivert: I felt compelled to make a blog post out of it, I hope you don't mind https://blog.tiserbox.com/posts/2023-12-03-2-deploy-to-nix-os-without-root-user.html | 04:15:19 |
| @sivertism:matrix.org | Not at all, I think it's a good idea to have all the steps in one place 👍️ | 05:23:42 |
| 5 Dec 2023 |
|  @federicodschonborn:matrix.org changed their profile picture. | 00:38:02 |
| 7 Dec 2023 |
|  @mutantmell:helveticastandard.com left the room. | 03:55:45 |
| 11 Dec 2023 |
 ari ❄ | colmena, when used in a flake, requires that one sets colmena.meta.nixpkgs, and that definition typically takes the system argument. I have a flake with configs for aarch64-linux and x86_64-linux, generating the nixosConfigurations entries using nixpkgs.lib.nixosSystem that also takes the system argument. now, if I don't additionally explicitly set nixpkgs.system for all the hosts, building the configs using nixos-rebuild or nix build or whatever works correctly, but colmena appears to set the system for all the hosts to whatever is passed as system argument to colmena.meta.nixpkgs (colmena eval -E '{ nodes, ... }: nodes.scylla.config.nixpkgs.system' returns wrong value).
Is there a workaround for that, that wouldn't involve setting nixpkgs.system explicitly, or adding nodeNixpkgs = builtins.mapAttrs (name: value: value.pkgs) conf; (this duplicates contents of nixpkgs.overlays which can cause other issues)?
| 14:34:17 |
|  Jasom joined the room. | 23:20:53 |
| Jasom | Colmena is stateless; nixops carries a small amount of state (e.g. system.stateVersion, ssh keys). I happen to like having that state managed for me, and it shouldn't be too hard to make an external tool to do this. Has someone written a tool to do so with Colmena, or should I write one? | 23:50:17 |
| 12 Dec 2023 |
 Wanja Hentze | not to my knowledge | 01:51:27 |
| Wanja Hentze | sounds lime a good thing to have available though! | 01:51:36 |
| Wanja Hentze | * sounds like a good thing to have available though! | 01:51:56 |
| ibizaman | Jasom can you elaborate on what this state management or I guess the lack of thereof means in practice? I don’t remember ever having to deal with that. | 01:58:42 |
