Error upgrade

conrad

Member
Nov 20, 2008
110
0
16
Upgrading slave node went perfect,
upgrading master failed.

Installing new version of config file /etc/apache2/sites-available/pve.conf ...
Installing new version of config file /etc/vz/vznet.conf ...
Restarting PVE daemon: pvedaemon.
Restarting PVE Tunnel Server: pvetunnel.
Restarting PVE Cluster Server: pvemirror.
Restarting web server: apache2Syntax error on line 20 of /etc/apache2/sites-enabled/pve.conf.save.1:
DocumentRoot must be a directory
failed!
invoke-rc.d: initscript apache2, action "restart" failed.
dpkg: error processing pve-manager (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve (--configure):
dependency problems - leaving unconfigured
Setting up xbase-clients (1:7.3+18) ...
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
dist-upgrade failed


this line: DocumentRoot /var/www/pve

the dir pve is missing, how is that possible ?
 
i think i can just delete /etc/apache2/sites-enabled/pve.conf.save.1
and run install script again ?
 
this line: DocumentRoot /var/www/pve

the dir pve is missing, how is that possible ?

Debian lenny has changed FS layout a bit. Putting things into /var/www is depreciciated. So we moved everything to /usr/share/pve-manager/

I guess you had a modified pve.conf? If so, there should be a file called /etc/apache2/sites-available/pve.conf.dpkg-dist which contains the new data - just copy that file and rerun the upgrade script again.
 
i think i can just delete /etc/apache2/sites-enabled/pve.conf.save.1
and run install script again ?

I have nod idea what this file is - I guess you created that file? Our file is called /etc/apache2/sites-enabled/pve.conf
 
strange thing is: no i didn't, i saw that there was a
pve.conf.save and a pve.conf.save.1
and there was a document root in that file which
pointed to /var/www/pve

i have really no idea, but i deleted them and try to update again.
 
just removed additional .save and .save.1 config files and ran
upgrade script again.

Upgrade is now successful.

And about the nfs mounts. (i have a /backup nfsmount)
just umount the nfs mounts before upgrade and even after the
--purge option the nfs mounts are available after reboot.
 

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!