Problems upgrading from 4.2 to 4.3 without cluster

D

dg_

Active Member
Sep 28, 2016
29
0
41
45
Hello,

I tried upgrade from VE 4.2 to 4.3 but i have some errors:

root@pve1:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-cluster (4.0-46) ...
Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
Package pve-cluster is not configured yet.

dpkg: error processing package libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-firewall:
pve-firewall depends on pve-cluster; however:
Package pve-cluster is not configured yet.
pve-firewall depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.

dpkg: error processing package pve-firewall (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.
qemu-server depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on pve-cluster (>= 4.0-8); however:
Package pve-cluster is not configured yet.
pve-container depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.
pve-manager depends on libpve-access-control (>= 3.0-2); however:
Package libpve-access-control is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.
pve-manager depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.
pve-manager depends on pve-container; however:
Package pve-container is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
libpve-access-control
pve-firewall
pve-ha-manager
qemu-server
pve-container
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve1:~# pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.4.6-1-pve)
pve-manager: not correctly installed (running version: 4.3-1/e7cdc165)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: not correctly installed
qemu-server: not correctly installed
pve-firmware: 1.1-9
libpve-common-perl: 4.0-73
libpve-access-control: not correctly installed
libpve-storage-perl: 4.0-61
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6.1-6
pve-container: not correctly installed
pve-firewall: not correctly installed
pve-ha-manager: not correctly installed
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.4-1
lxcfs: 2.0.3-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
zfsutils: 0.6.5.7-pve10~bpo80
root@pve1:~#



root@pve1:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: failed (Result: exit-code) since Wed 2016-09-28 15:14:35 CEST; 48min ago
Process: 113730 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
Main PID: 1692 (code=killed, signal=KILL)

Sep 28 15:14:35 pve1.xxx.net pmxcfs[113730]: [main] crit: Unable to get local IP address
Sep 28 15:14:35 pve1.xxx.net systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Sep 28 15:14:35 pve1.xxx.net systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 28 15:14:35 pve1.xxx.net systemd[1]: Unit pve-cluster.service entered failed state.
root@pve1:~# journalctl -xn
-- Logs begin at Fri 2016-09-23 13:30:50 CEST, end at Wed 2016-09-28 16:03:35 CEST. --
Sep 28 16:03:29 pve1.xxx.net pve-ha-crm[1756]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:30 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:30 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:30 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:34 pve1.xxx.net pve-ha-crm[1756]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:34 pve1.xxx.net pve-ha-crm[1756]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:34 pve1.xxx.net pve-ha-crm[1756]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:35 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:35 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:35 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
root@pve1:~#

Thanks.
 
Last edited:
pls run:

> apt-get update
> apt-get dist-upgrade

and try:

> apt-get install proxmox-ve
 
root@pve1:~# apt-get update
Ign cdrom://PVE 4.3 jessie InRelease
Ign cdrom://PVE 4.3 InRelease
Ign cdrom://PVE 4.3 jessie Release.gpg
Ign cdrom://PVE 4.3 Release.gpg
Ign cdrom://PVE 4.3 jessie Release
Ign cdrom://PVE 4.3 Release
Ign cdrom://PVE 4.3 jessie/pve amd64 Packages/DiffIndex
Ign cdrom://PVE 4.3 Packages/DiffIndex
Ign cdrom://PVE 4.3 jessie/pve Translation-en_US
Ign cdrom://PVE 4.3 jessie/pve Translation-en
Ign cdrom://PVE 4.3 Translation-en_US
Ign cdrom://PVE 4.3 Translation-en
Ign http://ftp.es.debian.org jessie InRelease
Hit http://ftp.es.debian.org jessie Release.gpg
Hit http://ftp.es.debian.org jessie Release
Hit http://security.debian.org jessie/updates InRelease
Hit http://ftp.es.debian.org jessie/main amd64 Packages
Hit http://ftp.es.debian.org jessie/contrib amd64 Packages
Hit http://ftp.es.debian.org jessie/contrib Translation-en
Hit http://ftp.es.debian.org jessie/main Translation-en
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://security.debian.org jessie/updates/contrib Translation-en
Hit http://security.debian.org jessie/updates/main Translation-en
Reading package lists... Done
root@pve1:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-cluster (4.0-46) ...
Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
Package pve-cluster is not configured yet.

dpkg: error processing package libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-firewall:
pve-firewall depends on pve-cluster; however:
Package pve-cluster is not configured yet.
pve-firewall depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.

dpkg: error processing package pve-firewall (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.
qemu-server depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on pve-cluster (>= 4.0-8); however:
Package pve-cluster is not configured yet.
pve-container depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.
pve-manager depends on libpve-access-control (>= 3.0-2); however:
Package libpve-access-control is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.
pve-manager depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.
pve-manager depends on pve-container; however:
Package pve-container is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
libpve-access-control
pve-firewall
pve-ha-manager
qemu-server
pve-container
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve1:~# apt-get install proxmox-ve
Reading package lists... Done
Building dependency tree
Reading state information... Done
proxmox-ve is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-cluster (4.0-46) ...
Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
Package pve-cluster is not configured yet.

dpkg: error processing package libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-firewall:
pve-firewall depends on pve-cluster; however:
Package pve-cluster is not configured yet.
pve-firewall depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.

dpkg: error processing package pve-firewall (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.
qemu-server depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on pve-cluster (>= 4.0-8); however:
Package pve-cluster is not configured yet.
pve-container depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.
pve-manager depends on libpve-access-control (>= 3.0-2); however:
Package libpve-access-control is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.
pve-manager depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.
pve-manager depends on pve-container; however:
Package pve-container is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
libpve-access-control
pve-firewall
pve-ha-manager
qemu-server
pve-container
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve1:~#
 
Hello,

I just disabled enterprise repo. But if i enable it i have the same problem:

root@pve1:~# apt-get update
Ign cdrom://PVE 4.3 jessie InRelease
Ign cdrom://PVE 4.3 InRelease
Ign cdrom://PVE 4.3 jessie Release.gpg
Ign cdrom://PVE 4.3 Release.gpg
Ign cdrom://PVE 4.3 jessie Release
Ign cdrom://PVE 4.3 Release
Ign cdrom://PVE 4.3 jessie/pve amd64 Packages/DiffIndex
Ign cdrom://PVE 4.3 Packages/DiffIndex
Ign cdrom://PVE 4.3 jessie/pve Translation-en_US
Ign cdrom://PVE 4.3 jessie/pve Translation-en
Ign cdrom://PVE 4.3 Translation-en_US
Ign cdrom://PVE 4.3 Translation-en
Ign http://ftp.es.debian.org jessie InRelease
Hit http://ftp.es.debian.org jessie Release.gpg
Hit http://ftp.es.debian.org jessie Release
Hit http://ftp.es.debian.org jessie/main amd64 Packages
Hit http://security.debian.org jessie/updates InRelease
Hit http://ftp.es.debian.org jessie/contrib amd64 Packages
Hit http://ftp.es.debian.org jessie/contrib Translation-en
Hit http://ftp.es.debian.org jessie/main Translation-en
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://security.debian.org jessie/updates/contrib Translation-en
Hit http://security.debian.org jessie/updates/main Translation-en
Get:1 https://enterprise.proxmox.com jessie InRelease [401 B]
Ign https://enterprise.proxmox.com jessie InRelease
Get:2 https://enterprise.proxmox.com jessie Release.gpg [401 B]
Ign https://enterprise.proxmox.com jessie Release.gpg
Get:3 https://enterprise.proxmox.com jessie Release [401 B]
Ign https://enterprise.proxmox.com jessie Release
Get:4 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [401 B]
Get:5 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en_US [401 B]
Get:6 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [401 B]
Get:7 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [401 B]
Get:8 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en_US [401 B]
Get:9 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [401 B]
Get:10 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [401 B]
Get:11 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en_US [401 B]
Get:12 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [401 B]
Get:13 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [401 B]
Get:14 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en_US [401 B]
Get:15 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [401 B]
Get:16 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [401 B]
Err https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages
HttpError401
Get:17 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en_US [401 B]
Ign https://enterprise.proxmox.com jessie/pve-enterprise Translation-en_US
Get:18 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [401 B]
Ign https://enterprise.proxmox.com jessie/pve-enterprise Translation-en
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/jessie/pve-enterprise/binary-amd64/Packages HttpError401

E: Some index files failed to download. They have been ignored, or old ones used instead.
root@pve1:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-cluster (4.0-46) ...
Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
Package pve-cluster is not configured yet.

dpkg: error processing package libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-firewall:
pve-firewall depends on pve-cluster; however:
Package pve-cluster is not configured yet.
pve-firewall depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.

dpkg: error processing package pve-firewall (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.
qemu-server depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on pve-cluster (>= 4.0-8); however:
Package pve-cluster is not configured yet.
pve-container depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.
pve-manager depends on libpve-access-control (>= 3.0-2); however:
Package libpve-access-control is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.
pve-manager depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.
pve-manager depends on pve-container; however:
Package pve-container is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
libpve-access-control
pve-firewall
pve-ha-manager
qemu-server
pve-container
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve1:~#
 
Did you change the IP?
If yes you have to set it in the /etc/hosts also.
 
wolfgang said:
Did you change the IP?
If yes you have to set it in the /etc/hosts also.
Click to expand...

I didn't do it.

The is that pve-cluster package is check cluster status with systemctl status pve-cluster.service but it is a single node. Can i upgrade this server without any multinode active?
 
can you send the output of
systemctl status pve-cluster.service
 
I sent in first post:

root@pve1:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: failed (Result: exit-code) since Wed 2016-09-28 15:14:35 CEST; 48min ago
Process: 113730 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
Main PID: 1692 (code=killed, signal=KILL)

Sep 28 15:14:35 pve1.xxx.net pmxcfs[113730]: [main] crit: Unable to get local IP address
Sep 28 15:14:35 pve1.xxx.net systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Sep 28 15:14:35 pve1.xxx.net systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 28 15:14:35 pve1.xxx.net systemd[1]: Unit pve-cluster.service entered failed state.
root@pve1:~# journalctl -xn
-- Logs begin at Fri 2016-09-23 13:30:50 CEST, end at Wed 2016-09-28 16:03:35 CEST. --
Sep 28 16:03:29 pve1.xxx.net pve-ha-crm[1756]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:30 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:30 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:30 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:34 pve1.xxx.net pve-ha-crm[1756]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:34 pve1.xxx.net pve-ha-crm[1756]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:34 pve1.xxx.net pve-ha-crm[1756]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:35 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:35 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
Sep 28 16:03:35 pve1.xxx.net pve-ha-lrm[1766]: ipcc_send_rec failed: Connection refused
root@pve1:~#
 
If i comment first line:

root@pve1:~# cat /etc/hosts
#127.0.0.1 pve1.xxx.net pve1
127.0.0.1 localhost.localdomain localhost
XX.XX.XX.XX pve1.xxx.net pve1 pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@pve1:~#

root@pve1:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: failed (Result: exit-code) since Thu 2016-09-29 08:25:08 CEST; 1min 57s ago
Process: 55377 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
Main PID: 1692 (code=killed, signal=KILL)

Sep 29 08:24:58 pve1.xxx.net pmxcfs[55377]: [main] notice: unable to aquire pmxcfs lock - trying again
Sep 29 08:24:58 pve1.xxx.net pmxcfs[55377]: [main] notice: unable to aquire pmxcfs lock - trying again
Sep 29 08:25:08 pve1.xxx.net pmxcfs[55377]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Sep 29 08:25:08 pve1.xxx.net pmxcfs[55377]: [main] notice: exit proxmox configuration filesystem (-1)
Sep 29 08:25:08 pve1.xxx.net systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Sep 29 08:25:08 pve1.xxx.net systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 29 08:25:08 pve1.xxx.net systemd[1]: Unit pve-cluster.service entered failed state.
root@pve1:~# journalctl -xn
-- Logs begin at Fri 2016-09-23 13:30:50 CEST, end at Thu 2016-09-29 08:26:05 CEST. --
Sep 29 08:25:01 pve1.xxx.net CRON[55379]: pam_unix(cron:session): session closed for user root
Sep 29 08:25:08 pve1.xxx.net pmxcfs[55377]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Sep 29 08:25:08 pve1.xxx.net pmxcfs[55377]: [main] notice: exit proxmox configuration filesystem (-1)
Sep 29 08:25:08 pve1.xxx.net pmxcfs[55377]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Sep 29 08:25:08 pve1.xxx.net pmxcfs[55377]: [main] notice: exit proxmox configuration filesystem (-1)
Sep 29 08:25:08 pve1.xxx.net systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Sep 29 08:25:08 pve1.xxx.net systemd[1]: Failed to start The Proxmox VE cluster filesystem.
-- Subject: Unit pve-cluster.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pve-cluster.service has failed.
--
-- The result is failed.
Sep 29 08:25:08 pve1.xxx.net systemd[1]: Unit pve-cluster.service entered failed state.
Sep 29 08:25:08 pve1.xxx.net systemd[1]: Started Corosync Cluster Engine.
-- Subject: Unit corosync.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit corosync.service has finished starting up.
--
-- The start-up result is done.
Sep 29 08:26:05 pve1.xxx.net systemd-timesyncd[70856]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.002s/0.001s/+5ppm
root@pve1:~#
 
right, but i doesn't work:

root@pve1:~# apt-get clean all
root@pve1:~# apt-get update
Ign cdrom://PVE 4.3 jessie InRelease
Ign cdrom://PVE 4.3 InRelease
Ign cdrom://PVE 4.3 jessie Release.gpg
Ign cdrom://PVE 4.3 Release.gpg
Ign cdrom://PVE 4.3 jessie Release
Ign cdrom://PVE 4.3 Release
Ign cdrom://PVE 4.3 jessie/pve amd64 Packages/DiffIndex
Ign cdrom://PVE 4.3 Packages/DiffIndex
Ign cdrom://PVE 4.3 jessie/pve Translation-en_US
Ign cdrom://PVE 4.3 jessie/pve Translation-en
Ign cdrom://PVE 4.3 Translation-en_US
Ign cdrom://PVE 4.3 Translation-en
Ign http://ftp.es.debian.org jessie InRelease
Hit http://ftp.es.debian.org jessie Release.gpg
Hit http://ftp.es.debian.org jessie Release
Hit http://ftp.es.debian.org jessie/main amd64 Packages
Hit http://security.debian.org jessie/updates InRelease
Hit http://ftp.es.debian.org jessie/contrib amd64 Packages
Hit http://ftp.es.debian.org jessie/contrib Translation-en
Hit http://ftp.es.debian.org jessie/main Translation-en
Ign http://download.proxmox.com jessie InRelease
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://download.proxmox.com jessie Release.gpg
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://download.proxmox.com jessie Release
Hit http://security.debian.org jessie/updates/contrib Translation-en
Hit http://download.proxmox.com jessie/pve-no-subscription amd64 Packages
Hit http://security.debian.org jessie/updates/main Translation-en
Ign http://download.proxmox.com jessie/pve-no-subscription Translation-en_US
Ign http://download.proxmox.com jessie/pve-no-subscription Translation-en
Reading package lists... Done
root@pve1:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-cluster (4.0-46) ...
Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
Package pve-cluster is not configured yet.

dpkg: error processing package libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-firewall:
pve-firewall depends on pve-cluster; however:
Package pve-cluster is not configured yet.
pve-firewall depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.

dpkg: error processing package pve-firewall (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.


#127.0.0.1 pve1.xxx.net pve1
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.
qemu-server depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on pve-cluster (>= 4.0-8); however:
Package pve-cluster is not configured yet.
pve-container depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.
pve-manager depends on libpve-access-control (>= 3.0-2); however:
Package libpve-access-control is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.
pve-manager depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.
pve-manager depends on pve-container; however:
Package pve-container is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
libpve-access-control
pve-firewall
pve-ha-manager
qemu-server
pve-container
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve1:~#









root@pve1:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: failed (Result: exit-code) since Thu 2016-09-29 09:32:26 CEST; 55s ago
Process: 60703 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
Main PID: 1692 (code=killed, signal=KILL)

Sep 29 09:32:16 pve1.xxx.net pmxcfs[60703]: [main] notice: unable to aquire pmxcfs lock - trying again
Sep 29 09:32:16 pve1.xxx.net pmxcfs[60703]: [main] notice: unable to aquire pmxcfs lock - trying again
Sep 29 09:32:26 pve1.xxx.net pmxcfs[60703]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Sep 29 09:32:26 pve1.xxx.net pmxcfs[60703]: [main] notice: exit proxmox configuration filesystem (-1)
Sep 29 09:32:26 pve1.xxx.net systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Sep 29 09:32:26 pve1.xxx.net systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 29 09:32:26 pve1.xxx.net systemd[1]: Unit pve-cluster.service entered failed state.
root@pve1:~# journalctl -xn
-- Logs begin at Fri 2016-09-23 13:30:50 CEST, end at Thu 2016-09-29 09:32:26 CEST. --
Sep 29 09:32:16 pve1.xxx.net pmxcfs[60703]: [main] notice: unable to aquire pmxcfs lock - trying again
Sep 29 09:32:16 pve1.xxx.net pmxcfs[60703]: [main] notice: unable to aquire pmxcfs lock - trying again
Sep 29 09:32:26 pve1.xxx.net pmxcfs[60703]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Sep 29 09:32:26 pve1.xxx.net pmxcfs[60703]: [main] notice: exit proxmox configuration filesystem (-1)
Sep 29 09:32:26 pve1.xxx.net pmxcfs[60703]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Sep 29 09:32:26 pve1.xxx.net pmxcfs[60703]: [main] notice: exit proxmox configuration filesystem (-1)
Sep 29 09:32:26 pve1.xxx.net systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Sep 29 09:32:26 pve1.xxx.net systemd[1]: Failed to start The Proxmox VE cluster filesystem.
-- Subject: Unit pve-cluster.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pve-cluster.service has failed.
--
-- The result is failed.
Sep 29 09:32:26 pve1.xxx.net systemd[1]: Unit pve-cluster.service entered failed state.
Sep 29 09:32:26 pve1.xxx.net systemd[1]: Started Corosync Cluster Engine.
-- Subject: Unit corosync.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit corosync.service has finished starting up.
--
-- The start-up result is done.
root@pve1:~#
 
please remove the first line of /etc/hosts
127.0.0.1 pve1.xxx.net pve1

and the
XX.XX.XX.XX pve1.xxx.net pve1 pvelocalhost
is the same IP like a interface IP and this interface is up?
 
wolfgang said:
please remove the first line of /etc/hosts
127.0.0.1 pve1.xxx.net pve1

and the
XX.XX.XX.XX pve1.xxx.net pve1 pvelocalhost
is the same IP like a interface IP and this interface is up?
Click to expand...

Yes i have first line commented with #... and IP for "XX.XX.XX.XX pve1.xxx.net pve1 pvelocalhost" is correct

It is the same IP that interface: vmbr0

auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_miimon 100
bond_mode balance-rr

auto vmbr0
iface vmbr0 inet static
address XX.XX.XX.XX
netmask 255.255.255.0
gateway XX.XX.XX.XX
 
Last edited:
your /etc/hosts should lock like this
127.0.0.1 localhost
XX.XX.XX.XX pve1.xxx.net pve1 pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
 
wolfgang said:
your /etc/hosts should lock like this
127.0.0.1 localhost
XX.XX.XX.XX pve1.xxx.net pve1 pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
Click to expand...

Yes:

root@pve1:~# cat /etc/hosts
#127.0.0.1 pve1.xxx.net pve1
127.0.0.1 localhost.localdomain localhost
XX.XX.XX.XX pve1.xxx.net pve1 pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@pve1:~#
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back