| 28 Jul 2023 |
 Mindavi | In reply to @andreas.schraegle:helsinki-systems.de
which one? the nixpkgs one or the one from the hydra repo?
I seem to remember them having some differences, but idk if that would be one of them. If you know about any consider making an issue on the nixpkgs tracker | 15:28:48 |
| Mindavi | I am running the nixpkgs one | 15:29:16 |
 ajs124 | In reply to @rick:matrix.ciphernetics.nl
If you know about any consider making an issue on the nixpkgs tracker it's probably just outdated information. there used to be a time where certain perl deps also were only part of the hydra flake instead of being in nixpkgs, but I think it's been some years since these issues. | 15:30:33 |
 chayleaf | the symptoms:
- I can see the queue (it says 0/4, but the builds are actually running)
- "running builds" is empty
- "machine status" is idle
- "latest builds" populates after build finish (that's probably fine)
- "latest steps" works perfectly fine too
- build page (like /build/4) returns 500 with the issue above
| 15:31:27 |
| chayleaf | * the symptoms:
- I can see the queue (it says 0/4, but the builds are actually running)
- "running builds" is empty
- "machine status" is idle
- "latest builds" populates after build finish (that's probably fine)
- "latest steps" works perfectly fine too
- build page (like /build/4) returns 500 with the error above
| 15:31:59 |
| ajs124 | does your nix-daemon log anything? | 15:32:32 |
| chayleaf | oh, error: error processing connection: user 'hydra-www' is not allowed to connect to the Nix daemon | 15:33:58 |
| chayleaf | also a bunch of connections are from hydra user | 15:34:31 |
| chayleaf | yeah it works after adding hydra-www to allowed-users | 15:39:42 |
