!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

361 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.112 Servers

Load older messages


SenderMessageTime
19 Jul 2025
@emilazy:matrix.orgemilyand on the first (i.e. not cached at my edge location yet) it's like 500 Mbit/s19:29:15
@dramforever:matrix.orgdramforeverthere a bunch of these kind of mirror sites in china19:29:21
@emilazy:matrix.orgemilydunno if limited by Fastly or S3 there19:29:22
@dramforever:matrix.orgdramforeverbut well, china19:29:23
@c0ba1t:matrix.orgCobaltNo, this is more finding a use for the storage. We can't sell/give it away easily and would like to put it to some good use. We have a 40G uplink iirc, with more for DFN19:29:39
@c0ba1t:matrix.orgCobaltIpv6 uplink is larger but might be difficult to implement 19:31:39
@hexa:lossy.networkhexawe can eventually push hydra results to multiple s3 buckets19:33:05
@hexa:lossy.networkhexa* we can eventually push hydra results to multiple s3 buckets with the new queue-runner19:33:10
@hexa:lossy.networkhexaso we could in theory fan than out19:33:22
@n4ch723hr3r:nope.chatn4ch723hr3r joined the room.19:40:51
@c0ba1t:matrix.orgCobaltThat sounds interesting but likely a lot more complex for upstream. If fastly is enough than this can likely also be postponed. Thanks for the info about Hydra though. Maybe that is something to come back to later19:44:09
20 Jul 2025
@hexa:lossy.networkhexa
loading build 302783248 (nixpkgs:cross-trunk:rpi.mpg123.aarch64-darwin)
queue monitor: error:
       … while loading build 302783248:
       … while parsing derivation '/nix/store/l43yj5i4g570a79vi4k1n2p2lla85ppg-systemd-minimal-armv6l-unknown-linux-gnueabihf-257.6.drv'
       error: attribute 'disallowedReferences' must be a list of strings
12:50:13
@hexa:lossy.networkhexa vcunat: you saw this before, right? 12:50:20
@hexa:lossy.networkhexakilled the relevant build and now we're game again12:53:02
@hexa:lossy.networkhexaannoying12:53:13
@vcunat:matrix.orgVladimír ČunátYes, this one but on a different derivation, apparently.13:43:21
21 Jul 2025
@cathal_mullan:matrix.orgCathal joined the room.19:46:11
22 Jul 2025
@drupol:matrix.orgPol joined the room.12:38:28
@drupol:matrix.orgPol Hey, do you have any idea why cache.nixos.org could be extremely slow at work? I contacted the helpdesk, and they confirmed there are no restrictions on their side... they suggested the issue might be external. The behaviour is strange: downloading just 30 MB takes around 15 minutes. It seems to follow a repeating pattern: the connection works normally for 1–2 seconds, then pauses for about 30 seconds, and this cycle continues indefinitely until the end. Nix is barely usable here :( Any idea how I could further investigate or troubleshoot this? Thanks! 12:39:15
@drupol:matrix.orgPol(feel free to redirect me to the right channel for this)12:46:09
@drupol:matrix.orgPolHere's the traceroute session: https://gist.github.com/drupol/3825ac49a93c1f2d04c91286edf8e19a12:58:33
@drupol:matrix.orgPol And a mtr session 13:00:21
@drupol:matrix.orgPolimage.png
Download image.png
13:00:25
@drupol:matrix.orgPol20% loss somewhere... that's weird.13:00:30
@hexa:lossy.networkhexaintermediate losses at routers is normal13:00:54
@drupol:matrix.orgPol27% now :S13:01:10
@hexa:lossy.networkhexathe traceroute not completing could be a red flag13:01:14
@drupol:matrix.orgPolOk... 13:01:14
@drupol:matrix.orgPolyeah that's so weird :(13:01:35
@drupol:matrix.orgPolI have that thing running for now 30 minutes:13:02:01

Show newer messages


Back to Room ListRoom Version: 6