upgrade

  1. E

    Vorgehensweise: Umstellung von Wheezy Openvz auf Proxmox 5.x

    Hallo zusammen, vorhanden: Debian Wheezy Openvz Rootserver 4 VMs online direkt mit eigener IP erreichbar 1 VM über VPN und interner IP erreichbar (VMs sind schon auf Proxmox VM konvertiert (Testserver) Um ein Update des Systems auf Stretch mit Proxmox durchzuführen, fallen mir ein paar Wege...
  2. T

    Live migration to another cluster (even from 3 to 5)

    All old proxmox users know how frustrating it can be to migrate your enviroment from 3 to 4 or even to 5. Ad there is many many other reasons why you some times want migrate your vm's from cluster to another. There is dirty hack for that. - copy from your local machine authorized keys your...
  3. G

    Different upgrade state on two PVE systems?

    I have two PVE systems which are not connected, both have a valid subscription and the same apt sources settings, but I get different results on running package update while both claiming that no updates are available: proxmox-ve: 5.1-40 (running kernel: 4.13.13-4-pve) pve-manager: 5.1-46...
  4. gurubert

    Migration from PVE 3 to 5 with GFS2 on shared storage

    Hi, I need to migrate a two node cluster from PVE 3.2 to 5.1. The cluster uses a shared storage device connected via SAS to the nodes running GFS2 on top of the shared block devices. GFS2 uses lock_dlm as locking manager, managed by the cluster manager of PVE. Is it possible to install PVE 5.1...
  5. magicfab

    Thank you! Flawless hardware upgrade in progress.

    This morning I had a scheduled PVE hardware upgrade planned. The plan was to move PVE OS disk + local data disk from an aging system (A) to a temporary system (B), in preparation for new faster disks + RAID being installed on (A). I just plugged the (A) disks in (B), booted and... it works...
  6. D

    Unable to upgrade node in cluster

    root@node02-sxb-pve01:~# apt-get update Err:1 https://packages.cisofy.com/community/lynis/deb stretch InRelease Failed to connect to packages.cisofy.com port 443: No route to host Err:2 https://enterprise.proxmox.com/debian/pve stretch InRelease Failed to connect to enterprise.proxmox.com...
  7. G

    PVE won't boot after upgrade 4.2 to 4.4

    Hi! just did a dist-upgrade to upgrade my PVE node from 4.2 to 4.4. upgrade process was good, but after the system reboot it won't start on default mode. the output of journalctl -xe is attached. I need some help to identify the error, thanks in advance.
  8. 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...
  9. 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...
  10. 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 ...
  11. 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...
  12. 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...
  13. 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...
  14. 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...
  15. 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
  16. 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...
  17. 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...
  18. 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...
  19. 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...
  20. 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...

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!