!UKDpaKNNsBpOPfLWfX:zhaofeng.li

Colmena

316 Members
A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena107 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
1 Dec 2022
@linus:schreibt.jetzt@linus:schreibt.jetzt right, then try plain colmena apply-local 19:01:17
@zhaofeng:zhaofeng.liZhaofeng Li
In reply to @linus:schreibt.jetzt
has the eval-node-limit heuristic improved? Without an explicit limit it at least used to completely blow my laptop up
There hasn't been any change to the heuristic which assumes a constant memory size for each node. We can probably make the number bigger if people keep running into things like this. It's bit difficult to estimate the memory usage to evaluate a "typical" condig
19:01:31
@zhaofeng:zhaofeng.liZhaofeng Li
In reply to @ask-yourself:matrix.org
deployment.privilegeEscalationCommand = ["doas"]; is also set.
colmena apply-local --sudo should work
19:01:40
@ask-yourself:matrix.org@ask-yourself:matrix.org

The output of colmena apply-local is:

.dotfiles on  main [!+] ⊥ colmena apply-local
[WARN ] Colmena was not started by root. This is probably not going to work.
[WARN ] Hint: Add the --sudo flag.
warning: Git tree '/home/isaac/.dotfiles' is dirty
[INFO ] Using flake: git+file:///home/isaac/.dotfiles
warning: Git tree '/home/isaac/.dotfiles' is dirty
warning: Git tree '/home/isaac/.dotfiles' is dirty
        🕖 7s 2 succeeded
desktop ✅ 6s Evaluated desktop
        ❌ 7s Failed: Child process exited with error code: 1
desktop ✅ 6s Evaluated desktop
desktop ✅ 0s Built "/nix/store/cagxgr77kc1ip1f31fx9y1f5xq23mk68-nixos-system-desktop-23.05pre-git"
desktop ✅ 0s Pushed system closure
desktop ❌ 0s Activation failed: Child process exited with error code: 1
[ERROR] Failed to deploy to desktop - Last 3 lines of logs:
[ERROR]  created)
[ERROR]    state) Running
[ERROR]  failure) Child process exited with error code: 1
[ERROR] Failed to complete requested operation - Last 1 lines of logs:
[ERROR]  failure) Child process exited with error code: 1
[ERROR] -----
[ERROR] Operation failed with error: Child process exited with error code: 1
19:01:54
@linus:schreibt.jetzt@linus:schreibt.jetztoops, never mind what I said then19:01:56
@ask-yourself:matrix.org@ask-yourself:matrix.org
In reply to @zhaofeng:zhaofeng.li
colmena apply-local --sudo should work
This should work even after I turn of sudo for this machine?
19:02:29
@ask-yourself:matrix.org@ask-yourself:matrix.org(And yes it does work, thank you.)19:02:50
@zhaofeng:zhaofeng.liZhaofeng LiIt uses the privilegeEscalationCommand configured in the config19:02:52
@zhaofeng:zhaofeng.liZhaofeng Li`apply-local` doesn't run the escalation command by default. It seems a bit rude to do so, given that sudo cache exists and Colmena may end up doing dangerous things without prompt. Better make it explicit I guess.19:03:36
@linus:schreibt.jetzt@linus:schreibt.jetzt gosh frick, I wanted to test if the problem still exists and yes it very much does lol 19:04:00
@zhaofeng:zhaofeng.liZhaofeng Li* There hasn't been any change to the heuristic which assumes a constant memory size for each node. We can probably make the number bigger if people keep running into things like this. It's bit difficult to estimate the memory usage to evaluate a "typical" config19:05:19
@ask-yourself:matrix.org@ask-yourself:matrix.org Zhaofeng Li: colmena apply-local --sudo doesn't work once sudo is turned off though, and I want to turn sudo off. 19:05:42
@linus:schreibt.jetzt@linus:schreibt.jetztHm, would it be appropriate to set the OOM score adjustment for the nix-eval-jobs process to avoid this kind of thing?19:06:28
@zhaofeng:zhaofeng.liZhaofeng LiHmm, it should be using the `deployment.privilegeEscalationCommand`. Let me check19:06:41
@ask-yourself:matrix.org@ask-yourself:matrix.orgWait. I had that commented out.19:06:59
@ask-yourself:matrix.org@ask-yourself:matrix.orgDon't waste your time checking yet, probably my error.19:07:09
@linus:schreibt.jetzt@linus:schreibt.jetztalso, the heuristic results in 52 workers for me which... I think is deep into inappropriate territory for 32G of RAM :D19:09:04

Show newer messages


Back to Room ListRoom Version: 6