From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] api: metrics/server: test connection on add/update
Date: Thu, 3 Dec 2020 17:55:06 +0100 [thread overview]
Message-ID: <59b49c6b-18e2-2d9e-afd6-3890a0896312@proxmox.com> (raw)
In-Reply-To: <20201125125640.5711-1-d.csapak@proxmox.com>
On 25.11.20 13:56, Dominik Csapak wrote:
> just a basic check, but better than not checking at all
>
so, just had an issue with the network (some test IPv6 LAN here) and had a metric
server configured on that net, thus pvestatd spammed the log with "network
unreachable" messages, and all my resources got the good ol' question mark in the
gui, so far so good.
But, I then tried to disable that ext. metrics entry, but we then *also* do a
connection check which obv. fails ^^
next prev parent reply other threads:[~2020-12-03 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 12:56 Dominik Csapak
2020-11-25 13:56 ` [pve-devel] applied: " Thomas Lamprecht
2020-12-03 16:55 ` Thomas Lamprecht [this message]
2020-12-07 14:30 ` [pve-devel] " Thomas Lamprecht
2020-12-07 14:32 ` Dominik Csapak
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59b49c6b-18e2-2d9e-afd6-3890a0896312@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox