From: Mathieu Othacehe <othacehe@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 45302@debbugs.gnu.org
Subject: bug#45302: Avahi substitute discovery keeps trying to ping unaccessible servers
Date: Mon, 11 Jan 2021 14:24:10 +0100 [thread overview]
Message-ID: <87mtxf61z9.fsf@gnu.org> (raw)
In-Reply-To: <87lfdw72lq.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 17 Dec 2020 18:40:33 +0100")
Hello Pierre,
> I've set up my desktop and laptop to use the new substitute discovery
> feature, it's awesome!
Glad you like it, and sorry for the late answer.
> substitute: guix substitute: warning: 10.0.0.5: connection failed: No route to host
Once your laptop goes to sleep, Avahi should detect that the publish
service is gone and remove it from the cache at
/var/guix/discovery/publish.
I'm having troubles reproducing it at home. Could you please run
"avahi-browse -a" on your desktop, put your laptop to sleep, and check
if the publish server disappears this way:
--8<---------------cut here---------------start------------->8---
- enp7s0f0 IPv6 guix-publish-cervin _guix_publish._tcp local
- enp7s0f0 IPv4 guix-publish-cervin _guix_publish._tcp local
--8<---------------cut here---------------end--------------->8---
Regarding the reboot issue, that's because the cache wasn't cleaned-up,
it should by fixed with: ee94cd265e03d12eeeccf58cbaf74b90008fcd14.
Thanks,
Mathieu
next prev parent reply other threads:[~2021-01-11 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 17:40 bug#45302: Avahi substitute discovery keeps trying to ping unaccessible servers Pierre Neidhardt
[not found] ` <handler.45302.B.16082268462565.ack@debbugs.gnu.org>
2020-12-17 18:33 ` bug#45302: Acknowledgement (Avahi substitute discovery keeps trying to ping unaccessible servers) Pierre Neidhardt
2020-12-22 3:25 ` bug#45302: Avahi substitute discovery keeps trying to ping unaccessible servers Maxim Cournoyer
2020-12-22 9:45 ` Pierre Neidhardt
2021-01-11 13:24 ` Mathieu Othacehe [this message]
2021-01-18 11:14 ` Pierre Neidhardt
2021-01-26 10:53 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtxf61z9.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=45302@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).