Search results

  1. H

    Adaptec Raid - broken requests after upgrade to current PVE 8 - revert to 7.4?

    Thanks a lot for your feedback. I'll keep the cluster in it's current mixed state (seems to be running smoothly) and wait for the patched kernel through the repositories. Hauke
  2. H

    Adaptec Raid - broken requests after upgrade to current PVE 8 - revert to 7.4?

    Hi there, after using the patched kernel on both affected nodes, they both behave perfectly fine, again :) Thanks a lot! One question remains: What do I do with my funny cluster now? Upgrade the remaining two nodes (still on 7.4) and use the patched kernel Upgrade the remaining two nodes...
  3. H

    Adaptec Raid - broken requests after upgrade to current PVE 8 - revert to 7.4?

    Just a quick reply while still testing: With your kernel, I can not reproduce the error using fio on a single node :) Next steps: I will install the same kernel on the second node that is affected and will bulk-migrate vms between those two nodes (which always triggered the unwanted aborted...
  4. H

    Adaptec Raid - broken requests after upgrade to current PVE 8 - revert to 7.4?

    Wow, thanks a lot for that hint! I will immediately check and let you know!
  5. H

    Adaptec Raid - broken requests after upgrade to current PVE 8 - revert to 7.4?

    Hi there, I am in the middle of performing an upgrade of my 4 node cluster from latest 7.4 to current 8.1. While the update procedure itself worked like a charm, I am running into RAID trouble with the current kernel (same as here https://bugzilla.kernel.org/show_bug.cgi?id=217599#c30, really...
  6. H

    [SOLVED] Setup Reverse Proxy (nginx) for backup client

    Got it! frontend pbs mode tcp bind :8007 ssl crt /etc/haproxy/my.crt alpn h2 http-request redirect scheme https unless { ssl_fc } default_backend servers backend servers mode tcp server s1 y.y.y.y:8007 ssl alpn h2 Just had to switch to tcp mode. Now it works! Thanks for...
  7. H

    [SOLVED] Setup Reverse Proxy (nginx) for backup client

    Hi Cookiefamily, I would expect a very simple config like: frontend pbs mode http bind :8007 ssl crt /etc/haproxy/my.crt alpn h2,http/1.1 default_backend servers backend servers mode http server s1 y.y.y.y:8007 ssl alpn h2,http/1.1 ,correct? When I do so, the pbsclient's...
  8. H

    [SOLVED] Setup Reverse Proxy (nginx) for backup client

    Hi ph0x, For me ... simply isolation. I do not want my vms to have a route into the network, where the backup server resides. So I decided to run a reverse proxy on each of my cluster nodes and provide an isolated ovs-bridge for my vms to access it. |vm| <-> |storage transfer-network| <->...
  9. H

    [SOLVED] Setup Reverse Proxy (nginx) for backup client

    Hi Sinos, Thanks for your reply and your help. That alone was not yet the solution, I still get broken pipes. But further reading seems to show that nginx still does not support http2-reverse-proxying. I also gave it a try with the grpc-module, but with more or less the same results. Since...
  10. H

    [SOLVED] Setup Reverse Proxy (nginx) for backup client

    Noone? Or did I miss an obvious documentation :eek:?
  11. H

    [SOLVED] Setup Reverse Proxy (nginx) for backup client

    Hi there, we are just integrating PBS 1.1 as our primary backup solution (love it!). We would like to make it avaliable to backup-clients via an nginx reverse proxy. The proxy works perfectly fine with the Web-UI, but the backup clients fail with broken pipes: Starting backup...
  12. H

    Upgrade PVE5.4 to PVE6 - suddenly, gre conntrack module is needed

    Hi, no, I tcpdump-ed myself through it and then searched online. I found an old thread here, which guided me into the right direction. Kind regards, Hauke
  13. H

    Upgrade PVE5.4 to PVE6 - suddenly, gre conntrack module is needed

    Hello there, this post is more for information puropses, should someone else stumble over the same problem. We just upgraded our 5.4 environment to 6.0. To provide internal connectivity for some of our VMs, we have another ovs (vmbrX, with no physical device connected) on each node, all of...
  14. H

    PVE 5.4 - Nodes suddenly reboot - no entries in logs

    Short update: Did Upgrade to PVE6 (hoping for a newer version of ixgbe driver) and limited the vzdump bandwidth. The latter seems to be a temporary fix, but of course, we will only see over the next week, if it acutally works. Kind regards, Hauke
  15. H

    PVE 5.4 - Nodes suddenly reboot - no entries in logs

    Hi Manu, thanks for your answer. No, we do not use a dedicated corosync network. But all backup/snapshotting traffic goes through a dedicated storage network, so there is no high load on the network, the corosync uses. I can see that in our Grafana-instance, we use to monitor the cluster...
  16. H

    PVE 5.4 - Nodes suddenly reboot - no entries in logs

    Hi, thanks for the hint. The CPU temperature does not seem to be the problem, it remains at a stable <45° Celsius all the time. The overheat protection would trigger at 89 degrees. As for the airflow/temperature of the NIC, I will have to check with our hardware provider, the machines are in...
  17. H

    PVE 5.4 - Nodes suddenly reboot - no entries in logs

    Hi Chris, good point. We updated the BIOS a few weeks ago exactly because of this issue. We do not observe much CPU load (the machines are a little oversized regarding CPU). During the time of the last failure, the CPU load was <10%. We did/do have, however, heavy traffic situations during...
  18. H

    PVE 5.4 - Nodes suddenly reboot - no entries in logs

    Hi Chris, I am confident that it is not primarily a hardware problem. All nodes are affected, randomly. Of course, it can still be hardware-related, because all nodes have the same hardware (except HDDs/SDDs on node 4). Kind regards, Hauke
  19. H

    PVE 5.4 - Nodes suddenly reboot - no entries in logs

    Hi forum, we have a 4 node setup based on Supermicro Superservers with the latest PVE5.4 and Ceph. For about 2 months now, we observe sudden reboots of single nodes about once per week without any hints in the logs (messages, syslog, kern.log). It seems like the node is running without any...
  20. H

    cluster firewall - change main ip address

    Oh dear, oh dear, oh dear. I refuse to accept that I have been this stupid :eek: I really thought, the host FW does not need to be activated. Shame on me, problem solved. It was a layer-8 problem. Kind regards, Hauke

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!