[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#69442: Discovered substitute servers not removed when they go offlin
From: |
Ludovic Courtès |
Subject: |
bug#69442: Discovered substitute servers not removed when they go offline |
Date: |
Wed, 28 Feb 2024 00:05:29 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hello,
Substitute servers discovered over Avahi don’t disappear when they go
off-line: they remain in /var/guix/discover/publish “forever” (?) and
‘guix substitute’ keeps trying to connect to them, in vain.
The problem AIUI is that the mDNS records are still valid according to
their TTL and thus cached by avahi-daemon; we can only notice that
things go wrong when trying to resolve:
--8<---------------cut here---------------start------------->8---
$ avahi-browse _guix_publish._tcp -r
+ enp0s31f6 IPv6 guix-publish-xyz _guix_publish._tcp
local
+ enp0s31f6 IPv4 guix-publish-xyz _guix_publish._tcp
local
Failed to resolve service 'guix-publish-xyz' of type '_guix_publish._tcp' in
domain 'local': Timeout reached
Failed to resolve service 'guix-publish-xyz' of type '_guix_publish._tcp' in
domain 'local': Timeout reached
--8<---------------cut here---------------end--------------->8---
(One way to reproduce that is to ‘pkill -9 avahi-daemon’ on the machine
that advertises the service.)
Problem is that ‘avahi-browse-service-thread’ attempts to resolve
services once for all; thus it never notices that services went away, at
least not until some long TTL has expired.
Ludo’.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#69442: Discovered substitute servers not removed when they go offline,
Ludovic Courtès <=