Just created an article in the wiki for - Installing Proxmox VE v1.9 post Lenny retirement. Debian Lenny was retired on Feb 6th, 2012 after a 2 month notice. All fresh installs will need the change to the /etc/apt/sources.list file before updates can be obtained and Debian Appliance Builder installed.
Installing Proxmox VE v1.9 post Lenny retirement
- Thread starter apmuthu
- Start date
Nobody should be doing new installs of Proxmox 1.9, it is end of life. Any new/old servers are just sitting around waiting for some security bug/flaw/hack to appear in postfix/apache2/etc.
In my case, I want to test the upgrade from 1.9 to 2.0. I already installed a test cluster with PVE 2.0 beta, then RC, to see how it works. Then I want to reinstall with 1.9, and test the upgrade path (with the script), to 2.0, before doing this on my production cluster. This is why I need to do a post Lenny retirement 1.9 Proxmox install. I think it is well justified, and the wiki article is very welcomed.
Alain
Alain
You are welcome. In fact, it was my plan from the beginning to have a test cluster to test 2.0, then to reinstall it with 1.9 and test the procedure to upgrade to 2.0, but the Lenny retirement complicated things a little. It helped me to have your wiki article to help fix the repositories paths, and be able to upgrade 1.9 to the last versions, and to install a few things (mc...).
I have succesfully reinstalled my test cluster with 1.9, and reinstalled VM (via backup), now it remains to test the upgrade.
Thanks
I have succesfully reinstalled my test cluster with 1.9, and reinstalled VM (via backup), now it remains to test the upgrade.
Thanks
Hi apmuthu,
I tested to day the upgrade script from 1.9 and 2.0 with my test cluster, and saw one caveat with this post lenny retirement configuration. The script does not handle correctly the changes with 'archives' in sources.list, and ends with an incorrect file.
So, I saw these errors when running the script ./pve-upgrade-1.9-to-2.0 :
It is due to the fact that the script replace 'archive' by 'debian' in the path, and 'lenny' by 'squeeze' (correct.
First I have :
(and similar for security updates). Then the script is doing some search and replace with sed :
and this ends with :
And this is incorrect, because, in my case, I am in France, you need to add .fr in the path :
and the same for security updates :
I don't know if I add something on the wiki to warn of this caveat, or if the upgrade script can be changed to care of this case ?
In any case, after fixing these paths manually, the upgrade script completed correctly. I had then to setup again the cluster, reimport old parameters (VMs), and at the end (with a few other caveats), it worked.
Alain
I tested to day the upgrade script from 1.9 and 2.0 with my test cluster, and saw one caveat with this post lenny retirement configuration. The script does not handle correctly the changes with 'archives' in sources.list, and ends with an incorrect file.
So, I saw these errors when running the script ./pve-upgrade-1.9-to-2.0 :
Code:
Err [URL]http://ftp.debian.org[/URL] squeeze/updates/main Packages
404 Not Found [IP: 130.89.148.12 80]
Err [URL]http://ftp.debian.org[/URL] squeeze/updates/contrib Packages
404 Not Found [IP: 130.89.148.12 80]
W: Failed to fetch [URL]http://ftp.debian.org/debian-security/dists/squeeze/updates/main/binary-amd64/Packages[/URL] 404 Not Found [IP: 130.89.148.12 80]
W: Failed to fetch [URL]http://ftp.debian.org/debian-security/dists/squeeze/updates/contrib/binary-amd64/Packages[/URL] 404 Not Found [IP: 130.89.148.12 80]It is due to the fact that the script replace 'archive' by 'debian' in the path, and 'lenny' by 'squeeze' (correct.
First I have :
Code:
deb [URL]http://archive.debian.org/debian[/URL] lenny main contrib(and similar for security updates). Then the script is doing some search and replace with sed :
Code:
sed -i -e "s/archive\.debian\.org/ftp\.debian\.org/" -e "s/lenny/squeeze/" /etc/apt/sources.listand this ends with :
Code:
deb [URL]http://ftp.debian.org/debian[/URL] squeeze main contribAnd this is incorrect, because, in my case, I am in France, you need to add .fr in the path :
Code:
deb [URL]http://ftp.fr.debian.org/debian[/URL] squeeze main contriband the same for security updates :
Code:
# security updates
deb [URL]http://ftp.fr.debian.org/debian-security/[/URL] squeeze/updates main contribI don't know if I add something on the wiki to warn of this caveat, or if the upgrade script can be changed to care of this case ?
In any case, after fixing these paths manually, the upgrade script completed correctly. I had then to setup again the cluster, reimport old parameters (VMs), and at the end (with a few other caveats), it worked.
Alain
Last edited:
No, that is difficult to handle in the upgrade script - please add that to the wiki instead.
you write "The script replaces 'archive' by 'ftp'" - I think this is not really true! Instead it simply replaces lenny with squeeze.
Isn't it the meaning of the first part of the log citation I quoted previously ?
Code:
sed -i -e "s/archive\.debian\.org/ftp\.debian\.org/Ah, I see it now - that was a recent addition ;-) If fact it does both things:
# sed -i -e "s/archive\.debian\.org/ftp\.debian\.org/" -e "s/lenny/squeeze/" /etc/apt/sources.list