Hello all.
I have previous experience succeeding upgrading Debian to PXVE4 from CLI
Today when attempting this on a remote host I find conflict with firmware.
I already saw: http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie
and did:
'apt-get install proxmox-ve ntp ssh postfix ksm-control-daemon open-iscsi systemd-sysv'
which all worked except for pve-firmware conflict with firmware-ti-connectivity 0.43
I tried:
and remove
Can anyone suggest how I can proceed?
[edit:] SOLUTION:
fix the package for firmware refusing to install with:
and then package installs completed, but pve-cluster config failed:
Answer re-edit /etc/hosts again so that $hostname did resolve to $EXTERNAL_IP
I have previous experience succeeding upgrading Debian to PXVE4 from CLI
Today when attempting this on a remote host I find conflict with firmware.
I already saw: http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie
and did:
'apt-get install proxmox-ve ntp ssh postfix ksm-control-daemon open-iscsi systemd-sysv'
which all worked except for pve-firmware conflict with firmware-ti-connectivity 0.43
I tried:
Code:
root@debian8:~/apt# apt-get install pve-firmware | tee apt-get_install_pve-firmware1
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
pve-firmware
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
172 not fully installed or removed.
Need to get 0 B/28.7 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 57974 files and directories currently installed.)e ...
Preparing to unpack .../pve-firmware_1.1-9_all.deb ...
Unpacking pve-firmware (1.1-9) ...
dpkg: error processing archive /var/cache/apt/archives/pve-firmware_1.1-9_all.deb (--unpack):
trying to overwrite '/lib/firmware/ti-connectivity/wl127x-fw-5-sr.bin', which is also in package firmware-ti-connectivity 0.43
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/pve-firmware_1.1-9_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian8:~/apt#
Code:
root@debian8:~/apt# apt-get remove firmware-ti-connectivity | tee apt-get_remove_firmware-ti-connectivity
Reading package lists...
Building dependency tree...
Reading state information...
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
proxmox-ve : Depends: pve-firmware but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
root@debian8:~/apt# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
pve-firmware
The following NEW packages will be installed:
pve-firmware
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
172 not fully installed or removed.
Need to get 28.7 MB of archives.
root@debian8:~/apt#
Can anyone suggest how I can proceed?
[edit:] SOLUTION:
fix the package for firmware refusing to install with:
Code:
root@debian8:~/apt# dpkg --purge firmware-ti-connectivity
(Reading database ... 57974 files and directories currently installed.)
Removing firmware-ti-connectivity (0.43) ...
root@debian8:~/apt# apt-get -f install pve-firmware
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
pve-firmware
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
172 not fully installed or removed.
Need to get 0 B/28.7 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 57953 files and directories currently installed.)
Preparing to unpack .../pve-firmware_1.1-9_all.deb ...
Unpacking pve-firmware (1.1-9)
...
and then package installs completed, but pve-cluster config failed:
Code:
root@debian8:~# 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-08 21:06:56 BST; 56s ago
Process: 20977 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
Sep 08 21:06:56 debian8 pmxcfs[20977]: [main] crit: Unable to get local IP address
Sep 08 21:06:56 debian8 pmxcfs[20977]: [main] crit: Unable to get local IP address
Sep 08 21:06:56 debian8 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Sep 08 21:06:56 debian8 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 08 21:06:56 debian8 systemd[1]: Unit pve-cluster.service entered failed state.
root@debian8:~#
root@debian8:~# journalctl -xn
-- Logs begin at Thu 2016-09-08 17:33:56 BST, end at Thu 2016-09-08 21:06:59 BST. --
Sep 08 21:06:25 debian8 systemd[1]: Unit pve-cluster.service entered failed state.
Sep 08 21:06:56 debian8 systemd-sysv-generator[20940]: Ignoring creation of an alias umountiscsi.service for itself
Sep 08 21:06:56 debian8 systemd-sysv-generator[20970]: Ignoring creation of an alias umountiscsi.service for itself
Sep 08 21:06:56 debian8 systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Sep 08 21:06:56 debian8 pmxcfs[20977]: [main] crit: Unable to get local IP address
Sep 08 21:06:56 debian8 pmxcfs[20977]: [main] crit: Unable to get local IP address
Sep 08 21:06:56 debian8 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Sep 08 21:06:56 debian8 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 08 21:06:56 debian8 systemd[1]: Unit pve-cluster.service entered failed state.
Sep 08 21:06:59 debian8 systemd-timesyncd[14354]: interval/delta/delay/jitter/drift 1024s/-0.005s/0.000s/0.004s/-22ppm
root@debian8:~#
...
Answer re-edit /etc/hosts again so that $hostname did resolve to $EXTERNAL_IP
Last edited: