Standard SysAdmin best practises from my perspective:
- tiny replaceable OS/root partitions
- Data storage to be separate from root/os storage
-- then moving it between faster(nvme zfs) vs redundant (read ceph) vs cheaper (HDD zfs) depending on...
Hm - could not reproduce dig not providing any output in a container that I installed fresh from the ubuntu 26.04 template (guessed the version based on `1:9.20.18-1ubuntu2.1` version for bind9-dnsutils) - here it produces the root-nameservers...
Thanks for digging into this, and the pointers to the OVH documentation!
I was not aware that there is a way to explicitly tell which boot-entry to load - so that seems like a workaround if you want to keep the option to boot into rescue mode...
Hello,
I encountered the same problem after updating to Proxmox 9.2, whereas in Proxmox 9.1 the issue doesn't occur.
Since this happened on two different machines, with two mothercard series, I used IPMI to try to figure out what rEFINd was...
No need to apologize! - I do see that it's a bit harder to read - I think I never noticed/wasn't bothered by it, as it looks fine in the template itself.
I'll see if I can adapt the template to add linkebreaks there (without adding tons of...
Thanks for the report - seems the case of having /var/spool/pmg on a dedicated mount-point/filesystem in a container was missed while testing -
I sent a patch for discussion to the pmg-devel mailing-list. once this or an improved version has been...
the config does work though? - I agree that this can be improved and would become more readable - but want to make sure that I don't miss something here?
There are mails originating from PMG (the bounces generated directly by postfix) that are not signed in PMG - could that be the source of the reported mails?
prinzipiell ist in der default config in einem PMG delay_warning_time auf 4h - sprich der ursprüngliche sender sollte von PMG eine mail bekommen, dass die mail noch nicht zugestellt werden konnte - siehe...
hm - if this also happens in a live-system that does not touch zfs before that's a bit odd (if anything or someone in the debian installation, tried running zpool import for all pools that would explain subsequent commands hanging)
as is -...
if the download manager uses many connections than it will run into rate-limits on all our download mirrors.
Thanks for the feedback - would be great if you could try again with the other 2 hosts (with a short pause in between and a single wget)...
please provide a traceroute to enterprise.proxmox.com , as well as a DNS resolution of that domain (both from/on the affected host). if you don't want to provide them publicly and your subscription level allows you to do so, please open an...
Quickly skimming through the thread here and the upstream issue (so I might have missed something).
I think the core issue here is that the broken zpool storage-01 is still configured as storage in PVE? - in that case pvestatd would try to...
Hi @yrzorg
thanks for posting in the forum!
770 sub find_local_network_for_ip {
771 my ($ip, $noerr) = @_;
772
773 my $testip = Net::IP->new($ip);
774
775 my $isv6 = $testip->version == 6;
776 my $routes =
777...
hm - is this node part of a cluster ? - maybe the cluster sync interferes here?
else - if you share the log - and your acme configuration files we might see something more.
"transient data" - this includes quarantined mails, and the...
hm - at least part of the issue is that an IP that might be yours (based on public IPs in your traceroute ) indeed ran into a rate limit - my guess is that your parallel downloader app opened too many parallel connections.
Sadly we had to install...
Genau das ist der Grund warum so etwas als temporary error (4xx) gewertet wird - und aus eigener Erfahrung gar nicht so unwahrscheinlich, dass ein user innerhalb der 5 tage, die eine mail so in der queue bleibt seine Inbox aufräumt.
Ich würde...
ok - but that is to be expected then - if you want to sign only mails from PMG - just add the fqdn of your pmg to the dkim domains e.g. pmg.your.domain (sorry I thought FQDN in your post did not refer to your internal domain, but to the fqdn of...