upgrade

  1. T

    Proxmox 5.1 upgrade problem - lvm-thin disappears

    When I upgraded from 4.4 to 5.1, I ran into a problem where the lvm-thin storage refused to start when the system was booting. I've forgotten the exact error code, but it was something along the lines of lvm2-activation.service error code 5. This of course caused quite a panic, even though I...
  2. B

    CEPH problem after upgrade to 5.1 / slow requests + stuck request

    Hi, I've got problem with my CEPH cluster. Cluster specification: 4x node 4x mon 4x mgr 37x osd I was starting from CEPH hammer so I followed tutorials: https://pve.proxmox.com/wiki/Ceph_Hammer_to_Jewel - without any problems https://pve.proxmox.com/wiki/Ceph_Jewel_to_Luminous - without any...
  3. C

    Upgrading to enterprise repo

    Hello, I wanted to know if we currently have the no-subscription repo and wanted to upgrade to the enterprise repo would that be possible by just changing the source list and apt-get update && apt-get dist-upgrade or we would need to reinstall since some packages are newer on the no-sub repo ...
  4. I

    monitors crash after upgrade Proxmox 4.4 to Proxmox 5.1

    Hello, After successful upgrade Proxmox 4.4 to Proxmox 5.1 we decided to go with BlueStore instead of FileStore. As soon as I deleted one FileStore OSD and created BlueStore instead, ceph became unresponsive. It appeared that 2 of 3 monitors crashed, and failed to start. Here is the snippet of...
  5. Volker Lieder

    Merge Proxmox 4.4 to 5.1

    Hi, we have a running setup with: 4 Server Debian 8.x with Proxmox 4.4, CEPH "hammer" with 30 osds Last weekend and for further growing, we installed 4 server with debian stretch and proxmox 5.1. If we login to the proxmox panel the new servers are marked as "offline". I didnt see any hints...
  6. A

    Ceph Hammer -> Jewel Problem

    Hi, i follow the Upgrade Path at Hammer to Jewel now i'm stuck at: systemctl stop ceph-mon.<MON-ID>.<UNIQUE ID>.service At this Point i can't find the right MON-ID, i tought it's listed at /lib/systemd/system/ i'm i right? How to verify this? At my GUI it's named mon.0 to mon.2, but the TAB...
  7. A

    Planning the upgrade from 4.4 to 5.0

    Hi guys, I'm planning a maintenance for tonight and I'd like your help. I have 10 VMs running on 3 nodes of PVE 4.4, for storage I'm using a external iSCSI NAS. So I'll move all VMs to node1, delete node2 and node3, make a fresh install of PVE 5.0 on node2 (keep or change his hostname to node5...
  8. H

    [SOLVED] Ceph luminous required for PVE 5 if Ceph is external

    We are planning an upgrade of PVE 4.x to 5.x. Is the requirement[1] on Ceph Luminous also in the case of using an external Ceph cluster? [1] https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0#Upgrade_the_basic_system_to_Debian_Stretch_and_PVE_5.0
  9. B

    ZFS is causing ARC_Prune storms.

    How can I upgrade ZFS in my Proxmox install? Does anyone have upgrade instructions somewhere? The wiki seems to not cover this. I need to install ZFS version 0.7 or newer. Proxmox v5 ships with ZFS version 0.6.5.9-1. Someone has logged a defect with the exact problem I have, on the ZFS ON...
  10. A

    After upgrade to 5.0, network does not start correctly every time

    Hi! I have a small cluster of Proxmox machines, and I am in the process of upgrading them to 5.0 from 4.4. The two that I have converted have this problem of every few reboots, the network simply doesn't work. I can log in via the console and run /etc/init.d/networking restart and that makes...
  11. I

    Upgraded to 5.0 headaches

    So I just upgraded to 5.0-23 tonight. When I try to boot the system, I now receive this error: [28.072000] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1] The machine will keep spitting out variations of that error (only thing that changes is the timing. Instead of 23s it...
  12. A

    problem upgrading proxmox 3.4 to 4.4

    Hello, I have a problem upgrading proxmox 3.4 to 4.4 on VPS server. i used this howto https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0. Every thing went well, even the step apt-get dist-upgrade without error. After that they ask for reboot. my server didn't reboot. This happend to me...
  13. M

    I/O-Errors nach Upgrade Proxmox VE 3.4-11 nach 4.4-13

    Hallo, im Zusammenhang mit einem Upgrade von Proxmox VE von Ver. 3.4.11 nach 4.4-13 haben wir zwei Effekte beobachtet, die uns im Hinblick auf die Stabilität bzw. Integrität der Gastsysteme etwas beunruhigt. Hardware: HP Proliant, 2 x Xeon E5-2620, 64 GB RAM, RAID 5 Gastsysteme: Linux-Server...
  14. M

    Updating a 3.3.5 cluster

    Hello. I have a cluster of three 3.3.5 nodes and I'd like to upgrade them to the latest one at a time. How will Rios affect the quorum of the cluster? Is it recommended to leave the containers in place during the upgrade? Is there a procedure published? Thanks.
  15. J

    apt-get upgrade broke my VE-3.2

    running an older (but fully working) version of VE and ran 'apt-get update && apt-get upgrade'. it upgraded lots of packages. apt-get update apt-get upgrade afterwards, the https gui started acting funky. timing out, not showing correct fields, just weird. proxmox1> pveversion -v...
  16. grin

    dist-upgrade / reboot / watchdog

    As we have already talked about reboots, here's one fresh. From 4.4-5 to 4.4-13. Reboot is at the end. Apr 12 14:55:47 srv-01-szd systemd[1]: Stopped Corosync Cluster Engine. Apr 12 14:55:47 srv-01-szd systemd[1]: Starting Corosync Cluster Engine... Apr 12 14:55:47 srv-01-szd corosync[26358]...
  17. F

    [SOLVED] Upgrade hanging

    Hi, today I wanted to dist-upgrade my cluster. After the three "VM"-Server I wanted to upgrade the other 3 ceph-severs. But on the first one the "apt-get dist-upgrade" stucked. [...] Setting up ceph-common (10.2.6-1~bpo80+1) ... Setting system user ceph properties..usermod: no changes ..done...
  18. C

    [SOLVED] Unable to upgrade 4.1 to 4.4

    Could someone please advise as the upgrade process?
  19. U

    Proxmox broken at upgrade to 4.4-5.

    Hi! We have 2 nodes in a cluster. After running upgrade we received message: Setting up pve-manager (4.4-5) ... Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details. dpkg: error processing package pve-manager (--configure): subprocess...
  20. H

    [SOLVED] pve-firewall blocking upgrade

    Hey all, I'm trying to upgrade my Proxmox install, that is running 4.3-9. After the `apt-get upgrade` command, I noticed that two packages weren't installed: `pve-firewall` and `pve-manager`. I tried to upgrade the `pve-manager` first, but it said it was dependent of `pve-firewall`, so I tried...