Recent content by ChristianW

Last week we changed from udp to tcp in status.cfg. For the last round we had no crash. Further observing and maybe we'll give udp with the new mtu feature for status.cfg a try.

Hm, we do have somehow a similar setup: VM running OPNSense with wireguard tunnel to grafana/graphite. Proxmox pushes metric data through this tunnel. In our case we have a debian base with proxmox installed. Our trouble startet with the last dist-upgrade, we made 9.10.2020.

Hi, is there any Update on this? We are facing the same issue, except the cycle of occurance is about seven days. It began probably with an dist-upgrade 14 days ago.

Hi, switching to tcp is working for us. It's quite a while ago, but our last guess was, that possibly corosyncs paket size checks could be responsible for the issue. Our paket sizes for metrics were repetitively starting somewhere at high level and than shrinking until one would reach our...

By the way: On VMs we use collectd to send metrics and they are all fine. So we have: - Host metrics by Proxmox = ok - Metrics out of VMs = ok - VM metrics by Proxmox = faulty Besides, how are metrics collected in Proxmox?

Standard Ethernet: 1500

https://forum.proxmox.com/threads/update-to-proxmox-6-1-broke-metrics.65402/

Hi, we just upgraded Proxmox to 6.1. Everything seems fine so far, but most of our monitoring data will be dropped, maybe because of an mtu issue: 08:55:30.176550 IP 172.16.200.250.47503 > 172.16.200.6.2003: UDP, bad length 10348 > 1472 08:55:30.242207 IP 172.16.200.250.47871 >...

Sounds good. Right now we are missing monitor data: Here before upgrade: After upgrade: Any idea how to work around it? Thank you for your this quick reply!

Hi, we just upgraded to 6.1 last night and have only sporadic monitoring data as well now. Probably same issue here: 08:55:30.176550 IP 172.16.200.250.47503 > 172.16.200.6.2003: UDP, bad length 10348 > 1472 08:55:30.242207 IP 172.16.200.250.47871 > 172.16.200.6.2003: UDP, bad length 50789 >...