[PVE-User] Unable to configure PVE manager (2.0) ?

Dietmar Maurer dietmar at proxmox.com
Thu Feb 16 10:56:36 CET 2012


Well, maybe they updated the debian packages and use strict syntax checks now.

I have corrected the syntax in new package (pve-manager_2.0-27), but you need
to wait a few day until we release that.

- Dietmar

> -----Original Message-----
> From: pve-user-bounces at pve.proxmox.com [mailto:pve-user-
> bounces at pve.proxmox.com] On Behalf Of Koichi MATSUMOTO
> Sent: Donnerstag, 16. Februar 2012 09:48
> To: proxmoxve (pve-user at pve.proxmox.com)
> Subject: Re: [PVE-User] Unable to configure PVE manager (2.0) ?
> 
> Mm.... related with packaging?
> 
> --
> @_@[root at ps /etc][0]# aptitude install insserv The following partially installed
> packages will be configured:
>   proxmox-ve-2.6.32 pve-manager
> No packages will be installed, upgraded, or removed.
> 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B of archives. After unpacking 0 B will be used.
> Setting up pve-manager (2.0-18) ...
> update-rc.d: error: start|stop arguments not terminated by "."
> usage: update-rc.d [-n] [-f] <basename> remove
>        update-rc.d [-n] <basename> defaults [NN | SS KK]
>        update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
>        update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
> 		-n: not really
> 		-f: force
> 
> The disable|enable API is not stable and might change in the future.
> dpkg: error processing pve-manager (--configure):
>  subprocess installed post-installation script returned error exit status 1
> configured to not write apport reports
>                                       configured to not write apport reports
>                                                                             dpkg: dependency problems prevent
> configuration of proxmox-ve-2.6.32:
>  proxmox-ve-2.6.32 depends on pve-manager; however:
>   Package pve-manager is not configured yet.
> dpkg: error processing proxmox-ve-2.6.32 (--configure):
>  dependency problems - leaving unconfigured Errors were encountered while
> processing:
>  pve-manager
>  proxmox-ve-2.6.32
> E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to
> install.  Trying to recover:
> Setting up pve-manager (2.0-18) ...
> update-rc.d: error: start|stop arguments not terminated by "."
> usage: update-rc.d [-n] [-f] <basename> remove
>        update-rc.d [-n] <basename> defaults [NN | SS KK]
>        update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
>        update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
> 		-n: not really
> 		-f: force
> 
> The disable|enable API is not stable and might change in the future.
> dpkg: error processing pve-manager (--configure):
>  subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
>  proxmox-ve-2.6.32 depends on pve-manager; however:
>   Package pve-manager is not configured yet.
> dpkg: error processing proxmox-ve-2.6.32 (--configure):
>  dependency problems - leaving unconfigured Errors were encountered while
> processing:
>  pve-manager
>  proxmox-ve-2.6.32
> --
> 
> On 2012/02/16, at 17:33, Dietmar Maurer wrote:
> 
> > try
> >
> > # aptitude install insserv
> >
> > does that help
> (snip)
> 
> 
> --
>  Koichi MATSUMOTO - http://maccoterie.com/
>     contact me? please see http://mch.tel/
> --




More information about the pve-user mailing list