Buildbot Frontend not reachable #352
Comments
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/nginx-subdomains-are-all-messed-up/57418/1 |
|
Check |
|
For context, |
|
|
I'll take a look at this later today, now I know where the bug is probably |
|
Have you not configured any workers by chance? |
The Buildbot worker is also failing with reference to twisted. I obfuscated the domain. But because its a free domain provider (for not much longer) I witnessed some instabilities in resolving the name. The worker is configured like this: { config, ... }:
let
masterCfg = config.services.buildbot-nix.master;
masterPort = config.services.buildbot-master.port;
in
{
services.buildbot-nix.worker = {
enable = true;
name = config.networking.hostName;
masterUrl = "${masterCfg.domain}:${(toString masterPort)}";
workerPasswordFile = config.sops.secrets."hetzbox-buildbot-worker-password".path;
};
} |
|
I mean in your |
The buildbot-workers.json is configured as a sops template. Could users and groups be wrong? { inputs, config, ... }:
let
hostName = config.networking.hostName;
cfg = config.sops;
bb-master-user = config.users.users.buildbot;
bb-worker-user = config.users.users.buildbot-worker;
buildbot-group = bb-master-user.group;
bbMasterPort = config.services.buildbot-master.port;
in
{
sops = {
secrets = {
codeberg-token = {
group = buildbot-group;
};
cb-buildbot-secret = {
owner = bb-master-user.name;
};
buildbot-webhook = {
owner = bb-master-user.name;
};
hetzbox-buildbot-worker-password = {
owner = bb-worker-user.name;
group = buildbot-group;
};
};
templates = {
"buildbot-workers.json" = {
content = ''
[
{
"name": "${hostName}",
"password": "${cfg.placeholder.hetzbox-buildbot-worker-password}",
"host": "${hostName}",
"port": ${(toString bbMasterPort)}
}
]
'';
owner = bb-master-user.name;
};
};
};
} |
|
It's called "pass" instead of password and there is no |
|
Use this as a template: buildbot-nix/examples/master.nix Line 15 in 8dc24d5 |
|
#355 made the cause of the problem more clear |
Thanks a lot. My issue is resolved as the frontend is now reachable. I cannot remember where I got the wrong workers.json config from. I am not really sure what cores means in this context. So i took half the number of available threads. |
It's number of concurrent build jobs effectively. If you allocate less, than you will see some errors in your buildbot worker because half the worker instances won't be able to connect. |
My configuration isn't based on the clan infra. But I realized that they are very similar.
But I always see the following instead of the buildbot frontend when trying to.
Could this be related to harmonia#481?
The text was updated successfully, but these errors were encountered: