Problem with proxmox version 5.4-3

[javiteam]

I have a cluster with 3 nodes, the first one is in proxmox 5.4-15 and the other two in 5.4-3 , the problem is that i need to install 5.4-15 in all of them because of a bug. But i can’t do it ,all of them have the same repository but i do apt update and dist-upgrade and i can’t find any upgradeable packets, so i have no way to installing the 5.4-15 in the 5.4-3 nodes

 

[Dunuin]

PVE 5 is End-of-Life since july 2020 and is based on Debian 9 which is also End-of-Life since july 2020. Debian 9 LTS is EoL since june 2022. Its so outdated that Debian even dropped the repos meanwhile. Try to add the archive repos: https://www.debian.org/distrib/archive.en.html and then upgrade PVE to a supported version (so PVE 7 or better PVE 8 as PVE7 will be EoL in 6 months too):
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

 

[javiteam]

PVE 5 is End-of-Life since july 2020 and is based on Debian 9 which is also End-of-Life since july 2020. Debian 9 LTS is EoL since june 2022. Its so outdated that Debian even dropped the repos meanwhile. Try to add the archive repos: https://www.debian.org/distrib/archive.en.html and then upgrade PVE to a supported version (so PVE 7 or better PVE 8 as PVE7 will be EoL soon too):
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

I cant upgrade to proxmox 6 because my servers are old . And they can't run proxmox 6

 

[Dunuin]

Then its probably time to upgrade to some newer hardware that was released in the last decade to be able to keep up with security/reliability.

 

[javiteam]

Then its probably time to upgrade to some newer hardware that was released in the last decade to be able to keep up with security/reliability.

It is a class project, i don't own the servers. But i can't understand why one of the servers had the 5.4-15 and the other two have 5.4-3 if all of them were installed with the same iso ,and have the same repositorys

 

[leesteken]

It is a class project, i don't own the servers. But i can't understand why one of the servers had the 5.4-15 and the other two have 5.4-3 if all of them were installed with the same iso ,and have the same repositorys

Someone pressed the Refresh button and the Upgrade button (or the command-line equivalents) on one server but not the others (while it was still supported).
Maybe you can copy the apt cache/repository from one server to the other two and upgrade that way?

 

[javiteam]

Someone pressed the Refresh button and the Upgrade button (or the command-line equivalents) on one server but not the others (while it was still supported).
Maybe you can copy the apt cache/repository from one server to the other two and upgrade that way?

how can i do that ? I'm still a noob with proxmox ,thanks for the help

 

[leesteken]

how can i do that ? I'm still a noob with proxmox ,thanks for the help

I don't know but it sounds to me that something like that might work. I don't want to spend the time to recreate your situation and experiment to figure it out, but you might have the motivation to pursue this direction, search and learn and ask concrete questions.

 

[javiteam]

I don't know but it sounds to me that something like that might work. I don't want to spend the time to recreate your situation and experiment to figure it out, but you might have the motivation to pursue this direction, search and learn and ask concrete questions.

i'll try it tomorrow and tell you,thanks for the help

 

[RolandK]

>I cant upgrade to proxmox 6 because my servers are old . And they can't run proxmox 6

can you explain why they can't run proxmox 6 ? you can even run proxmox 8.1 without problems on hardware more then 10 years old.

 

[javiteam]

>I cant upgrade to proxmox 6 because my servers are old . And they can't run proxmox 6

can you explain why they can't run proxmox 6 ? you can even run proxmox 8.1 without problems on hardware more then 10 years old.

i think they are hp proilant dl100 and they dont even have the minium amount of ram for proxmox 6, i'll check it tomorrow when i go to class . Thanks everyone, this community really helps

 

[RolandK]

Prolian DL100 G2 ? ( https://en.wikipedia.org/wiki/ProLiant )

that should have maximum 4gb ram and that should be ok for proxmox ( Minimum 2 GB for the OS and Proxmox VE services, plus designated memory for guests should be valid for for proxmox 6/7 and 8)

i bet you get that for free from somewhere , if you don't have 4gb inside

 

[javiteam]

I was able to install proxmox 6.4 but now i’m having another problem while installing openvswitch , two nodes of the cluster managed to install it without errors but the other one with same repositorys and the same version is giving me an error

 

[javiteam]

I was able to install proxmox 6.4 but now i’m having another problem while installing openvswitch , two nodes of the cluster managed to install it without errors but the other one with same repositorys and the same version is giving me an error

The error is
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law.


root@cremaet：~# apt instal1 openvswitch-common=2.12.3-1


Reading package lists... Done Building dependency tree


Reading state information... Done


Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.


The following information may help to resolve the situation:


The following packages have unmet dependencies:


openswitch-common: Depends: libatonicl (>= 4.8) but it is not installable


Depends: libunbound8 (>= 1.8.0) but it is not installable


E: Unable to correct problens, you have held broken packages. root@cremaet:~*

 

[sherminator]

If I were in this situation I wouldn't waste time trying to upgrade such an outdated installation. I would try to backup the VMs, make a new installation of the whole environment and then restore the VMs.