Search results

  1. OpenZFS 2.0?

    It looks like zfs 2.0.3 in now in the stable proxmox repo :) Is there anything published about this upgrade ?
  2. ifreload failed

    The network interface file does not seem to have any link with this issue. This part of ifupdown2 scans the available devices, without using the interfaces file. More details with a new node impacted... I just got the same problem on a second server, also using a melanox adapter (same as the...
  3. ifreload failed

    Was 2.0.1-1+pve2, now 2.0.1-1+pve3 Same error message: "error: main exception: Length of MACAddress attribute not supported: 24" It comes from https://github.com/CumulusNetworks/python-nlmanager/blob/master/nlmanager/nlpacket.py#L591 I've replaced the raise.exception with a simple...
  4. ifreload failed

    Same problem for me since a hard reboot of one of my servers which completely lost network :( I used ifupdown2 previously on this server and had no trouble, so it must be linked with some update. On another node, infiniband does not causes trouble with ifupdown2. The IB adapters are different...
  5. [SOLVED] PVE 5.4-11 + Corosync 3.x: major issues

    Non corosync problem in my syslog... the fix seems good so far :)
  6. [SOLVED] PVE 5.4-11 + Corosync 3.x: major issues

    Meanwhile... why not ask systemd to restart corosync when it crashed ? Restart=on-failure To my knowledge, link0 was not down Here is a full syslog during the same period: Aug 22 12:29:00 proxmox72 systemd[1]: Starting Proxmox VE replication runner... Aug 22 12:29:00 proxmox72 systemd[1]...
  7. [SOLVED] PVE 5.4-11 + Corosync 3.x: major issues

    One more corosync crash (with 1.10_pve2)... I hope the upcoming bug fixes will help ! ● corosync.service - Corosync Cluster Engine Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Thu 2019-08-22 12:29:22 UTC; 2h...
  8. [SOLVED] PVE 5.4-11 + Corosync 3.x: major issues

    corosync got killed (again) on one of my 3 nodes cluster root@r510a:~# systemctl status corosync ● corosync.service - Corosync Cluster Engine Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Sun 2019-08-11...
  9. [SOLVED] PVE 5.4-11 + Corosync 3.x: major issues

    I also have instability in my 3 nodes cluster recently upgrade from 5.4 to 6.0. corosync got killed on two nodes during the past days. This morning, one of the node got out of the cluster. The log showed a "TOTEM FAILED RECEIVED". It got back it in by adding a second ring (on my infiniband...
  10. [SOLVED] migrating (very) old (non proxmox) openvz container to proxmox 5

    I'm currently migrating an old server (debian 6 + openvz) to proxmox 5. The old vzdump script generates .tgz files that are not recognized by proxmox 5 pct restore command. Simply rename them to .tar.gz !
  11. migrating non proxmox openvz container to proxmox 4

    After some more investigation, it looks like my old vzdump (1.2.x) does not create a dump file compatible with today's pct restore... How can I do some conversion ?
  12. migrating non proxmox openvz container to proxmox 4

    I have an old openvz based setup which I want to migrate to proxmox 4 (and LXC). I've backuped a test VM using vzdump, but when I restore on my proxmox 4 node, I get the following: root# pct restore 101 vzdump-openvz-101-2016_02_21-15_40_41.tar unable to create image: qemu-img: Image size must...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!