When updating from 4.4 to 5.1, I chose the option to use the Maintainers config file instead of using the default and now I can't get logged into the Proxmox web page. I can putty in though. Can this be easily fixed? I have very little linux experience. Thanks in advance for any help.
Updated 4.4 to 5.1 and chose to use maintainers config file..help
- Thread starter wvscanner
- Start date
TBH, I'm not sure what it's called. It was the only question asked when upgrading the distro from 4.4 to 5.1. At the end of the upgrade, it asked I wanted to change, the config file and the Default was (N)o, and I chose (Y)es. Proxmox seems to be running, as I can putty into it. But I have no Idea on how or where to access the config files.
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at....
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /us....
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at....
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /us....
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at....
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /us....
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at....
Nov 06 07:27:07 Proxmox systemd[1]: pvestatd.service: control process exite...55
Nov 06 07:27:07 Proxmox systemd[1]: Failed to start PVE Status Daemon.
Nov 06 07:27:07 Proxmox systemd[1]: Unit pvestatd.service entered failed state.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: active (running) since Mon 2017-11-06 07:27:06 EST; 1h 49min ago
Main PID: 1250 (pmxcfs)
CGroup: /system.slice/pve-cluster.service
└─1250 /usr/bin/pmxcfs
Nov 06 07:27:06 Proxmox systemd[1]: Started The Proxmox VE cluster filesystem.
Hint: Some lines were ellipsized, use -l to show in full.
root@Proxmox:~#
root@Proxmox:~#
root@Proxmox:~# clear
root@Proxmox:~# systemctl status pveproxy pvedaemon pvestatd pve-cluster -l
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: exit-code) since Mon 2017-11-06 07:27:08 EST; 1h 49min ago
Nov 06 07:27:08 Proxmox pveproxy[1313]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 14, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 14, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: Compilation failed in require at /usr/bin/pveproxy line 11, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, <DATA> line 751.
Nov 06 07:27:08 Proxmox systemd[1]: pveproxy.service: control process exited, code=exited status=255
Nov 06 07:27:08 Proxmox systemd[1]: Failed to start PVE API Proxy Server.
Nov 06 07:27:08 Proxmox systemd[1]: Unit pveproxy.service entered failed state.
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: failed (Result: exit-code) since Mon 2017-11-06 07:30:22 EST; 1h 46min ago
Process: 1522 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)
Nov 06 07:30:22 Proxmox pvedaemon[1522]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: Compilation failed in require at /usr/bin/pvedaemon line 11, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11, <DATA> line 751.
Nov 06 07:30:22 Proxmox systemd[1]: pvedaemon.service: control process exited, code=exited status=255
Nov 06 07:30:22 Proxmox systemd[1]: Failed to start PVE API Daemon.
Nov 06 07:30:22 Proxmox systemd[1]: Unit pvedaemon.service entered failed state.
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled)
Active: failed (Result: exit-code) since Mon 2017-11-06 07:27:07 EST; 1h 49min ago
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuConfig.pm line 6, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /usr/share/perl5/PVE/QemuServer.pm line 30, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuServer.pm line 30, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvestatd.pm line 18, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvestatd.pm line 18, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /usr/bin/pvestatd line 9, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at /usr/bin/pvestatd line 9, <DATA> line 751.
Nov 06 07:27:07 Proxmox systemd[1]: pvestatd.service: control process exited, code=exited status=255
Nov 06 07:27:07 Proxmox systemd[1]: Failed to start PVE Status Daemon.
Nov 06 07:27:07 Proxmox systemd[1]: Unit pvestatd.service entered failed state.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: active (running) since Mon 2017-11-06 07:27:06 EST; 1h 49min ago
Main PID: 1250 (pmxcfs)
CGroup: /system.slice/pve-cluster.service
└─1250 /usr/bin/pmxcfs
Nov 06 07:27:06 Proxmox systemd[1]: Started The Proxmox VE cluster filesystem.
root@Proxmox:~#
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /us....
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at....
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /us....
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at....
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /us....
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at....
Nov 06 07:27:07 Proxmox systemd[1]: pvestatd.service: control process exite...55
Nov 06 07:27:07 Proxmox systemd[1]: Failed to start PVE Status Daemon.
Nov 06 07:27:07 Proxmox systemd[1]: Unit pvestatd.service entered failed state.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: active (running) since Mon 2017-11-06 07:27:06 EST; 1h 49min ago
Main PID: 1250 (pmxcfs)
CGroup: /system.slice/pve-cluster.service
└─1250 /usr/bin/pmxcfs
Nov 06 07:27:06 Proxmox systemd[1]: Started The Proxmox VE cluster filesystem.
Hint: Some lines were ellipsized, use -l to show in full.
root@Proxmox:~#
root@Proxmox:~#
root@Proxmox:~# clear
root@Proxmox:~# systemctl status pveproxy pvedaemon pvestatd pve-cluster -l
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: exit-code) since Mon 2017-11-06 07:27:08 EST; 1h 49min ago
Nov 06 07:27:08 Proxmox pveproxy[1313]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 14, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 14, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: Compilation failed in require at /usr/bin/pveproxy line 11, <DATA> line 751.
Nov 06 07:27:08 Proxmox pveproxy[1313]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, <DATA> line 751.
Nov 06 07:27:08 Proxmox systemd[1]: pveproxy.service: control process exited, code=exited status=255
Nov 06 07:27:08 Proxmox systemd[1]: Failed to start PVE API Proxy Server.
Nov 06 07:27:08 Proxmox systemd[1]: Unit pveproxy.service entered failed state.
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: failed (Result: exit-code) since Mon 2017-11-06 07:30:22 EST; 1h 46min ago
Process: 1522 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)
Nov 06 07:30:22 Proxmox pvedaemon[1522]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: Compilation failed in require at /usr/bin/pvedaemon line 11, <DATA> line 751.
Nov 06 07:30:22 Proxmox pvedaemon[1522]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11, <DATA> line 751.
Nov 06 07:30:22 Proxmox systemd[1]: pvedaemon.service: control process exited, code=exited status=255
Nov 06 07:30:22 Proxmox systemd[1]: Failed to start PVE API Daemon.
Nov 06 07:30:22 Proxmox systemd[1]: Unit pvedaemon.service entered failed state.
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled)
Active: failed (Result: exit-code) since Mon 2017-11-06 07:27:07 EST; 1h 49min ago
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuConfig.pm line 6, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /usr/share/perl5/PVE/QemuServer.pm line 30, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuServer.pm line 30, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvestatd.pm line 18, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvestatd.pm line 18, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: Compilation failed in require at /usr/bin/pvestatd line 9, <DATA> line 751.
Nov 06 07:27:07 Proxmox pvestatd[1303]: BEGIN failed--compilation aborted at /usr/bin/pvestatd line 9, <DATA> line 751.
Nov 06 07:27:07 Proxmox systemd[1]: pvestatd.service: control process exited, code=exited status=255
Nov 06 07:27:07 Proxmox systemd[1]: Failed to start PVE Status Daemon.
Nov 06 07:27:07 Proxmox systemd[1]: Unit pvestatd.service entered failed state.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: active (running) since Mon 2017-11-06 07:27:06 EST; 1h 49min ago
Main PID: 1250 (pmxcfs)
CGroup: /system.slice/pve-cluster.service
└─1250 /usr/bin/pmxcfs
Nov 06 07:27:06 Proxmox systemd[1]: Started The Proxmox VE cluster filesystem.
root@Proxmox:~#
root@Proxmox:~# pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.13.4-1-pve)
pve-manager: not correctly installed (running version: 5.1-36/131401db)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.15-1-pve: 4.4.15-60
pve-kernel-4.13.4-1-pve: 4.13.4-25
pve-kernel-4.4.83-1-pve: 4.4.83-96
libpve-http-server-perl: 2.0-6
lvm2: 2.02.116-pve3
corosync: not correctly installed
libqb0: 1.0.1-1
pve-cluster: 4.0-53
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.0-5~pve4
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.7-pve4
criu: 1.6.0-1
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1~pve80
zfsutils-linux: 0.7.2-pve1~bpo90
proxmox-ve: not correctly installed (running kernel: 4.13.4-1-pve)
pve-manager: not correctly installed (running version: 5.1-36/131401db)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.15-1-pve: 4.4.15-60
pve-kernel-4.13.4-1-pve: 4.13.4-25
pve-kernel-4.4.83-1-pve: 4.4.83-96
libpve-http-server-perl: 2.0-6
lvm2: 2.02.116-pve3
corosync: not correctly installed
libqb0: 1.0.1-1
pve-cluster: 4.0-53
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.0-5~pve4
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.7-pve4
criu: 1.6.0-1
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1~pve80
zfsutils-linux: 0.7.2-pve1~bpo90
root@Proxmox:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following package was automatically installed and is no longer required:
libelf1
Use 'apt-get autoremove' to remove it.
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 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-manager (5.1-36) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed 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 package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following package was automatically installed and is no longer required:
libelf1
Use 'apt-get autoremove' to remove it.
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 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-manager (5.1-36) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed 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 package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
IDK about that.....all I've done is update and run and install vm's and containers via the web interface....I'm not much with linux.
deb http://ftp.us.debian.org/debian jessie main contrib
deb http://download.proxmox.com/debian jessie pve-no-subscription
deb http://ftp.debian.org/debian jessie main contrib
# security updates
deb http://security.debian.org jessie/updates main contrib
deb http://ftp.us.debian.org/debian jessie main contrib
deb http://download.proxmox.com/debian jessie pve-no-subscription
deb http://ftp.debian.org/debian jessie main contrib
# security updates
deb http://security.debian.org jessie/updates main contrib
did you follow https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0 when upgrading ?
it explicitely states that you have to change jessie to stretch in the /etc/apt/sources.list etc.
please read that guide and try again
it explicitely states that you have to change jessie to stretch in the /etc/apt/sources.list etc.
please read that guide and try again
Did as you requested...and it's now seemed to of stopped.....do I need to do something, or just wait?
Fetched 254 MB in 4min 25s (959 kB/s)
Reading changelogs... Done
by setting ISCSI_ROOT_KEEP_ALL_SESSIONS_AT_SHUTDOWN=1 in
/etc/default/open-iscsi.
HANDLE_NETDEV=0 BEHAVIOR CHANGE
If you are running sysvinit and have HANDLE_NETDEV=0, please note
that this flag is now also checked at bootup, i.e. filesystems with
_netdev will not be mounted automatically at boot anymore by
open-iscsi. (Previously, this flag was only checked at shutdown.)
On systemd systems, HANDLE_NETDEV is now completely ignored, as
systemd handles mounting of network filesystems directly.
PURGING OPEN-ISCSI
If you purge open-iscsi, it will now remove the database in
/etc/iscsi (it previously didn't).
-- Christian Seiler <christian@iwakd.de> Thu, 20 Aug 2015 11:08:37 +0200
Waiting for data... (interrupt to abort)
Fetched 254 MB in 4min 25s (959 kB/s)
Reading changelogs... Done
by setting ISCSI_ROOT_KEEP_ALL_SESSIONS_AT_SHUTDOWN=1 in
/etc/default/open-iscsi.
HANDLE_NETDEV=0 BEHAVIOR CHANGE
If you are running sysvinit and have HANDLE_NETDEV=0, please note
that this flag is now also checked at bootup, i.e. filesystems with
_netdev will not be mounted automatically at boot anymore by
open-iscsi. (Previously, this flag was only checked at shutdown.)
On systemd systems, HANDLE_NETDEV is now completely ignored, as
systemd handles mounting of network filesystems directly.
PURGING OPEN-ISCSI
If you purge open-iscsi, it will now remove the database in
/etc/iscsi (it previously didn't).
-- Christian Seiler <christian@iwakd.de> Thu, 20 Aug 2015 11:08:37 +0200
Waiting for data... (interrupt to abort)
Ok...did it again, and here's what I got.....can it be repaired?
518 upgraded, 157 newly installed, 10 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0 B/254 MB of archives.
After this operation, 251 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs... Done
apt-listchanges: Mailing root: apt-listchanges: news for Proxmox
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 62078 files and directories currently installed.)
Removing libkadm5clnt-mit9:amd64 (1.12.1+dfsg-19+deb8u2) ...
Removing libkadm5srv-mit9:amd64 (1.12.1+dfsg-19+deb8u2) ...
Removing libkdb5-7:amd64 (1.12.1+dfsg-19+deb8u2) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62061 files and directories currently installed.)
Preparing to unpack .../libkeyutils1_1.5.9-9_amd64.deb ...
Unpacking libkeyutils1:amd64 (1.5.9-9) over (1.5.9-5+b1) ...
Preparing to unpack .../libk5crypto3_1.15-1+deb9u1_amd64.deb ...
Unpacking libk5crypto3:amd64 (1.15-1+deb9u1) over (1.12.1+dfsg-19+deb8u2) ...
Preparing to unpack .../libgssapi-krb5-2_1.15-1+deb9u1_amd64.deb ...
Unpacking libgssapi-krb5-2:amd64 (1.15-1+deb9u1) over (1.12.1+dfsg-19+deb8u2) ...
Preparing to unpack .../libkrb5-3_1.15-1+deb9u1_amd64.deb ...
Unpacking libkrb5-3:amd64 (1.15-1+deb9u1) over (1.12.1+dfsg-19+deb8u2) ...
Preparing to unpack .../libkrb5support0_1.15-1+deb9u1_amd64.deb ...
Unpacking libkrb5support0:amd64 (1.15-1+deb9u1) over (1.12.1+dfsg-19+deb8u2) ...
Preparing to unpack .../libcomerr2_1.43.4-2_amd64.deb ...
Unpacking libcomerr2:amd64 (1.43.4-2) over (1.42.12-2+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libcomerr2:amd64 (1.43.4-2) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Selecting previously unselected package libfdisk1:amd64.
(Reading database ... 62060 files and directories currently installed.)
Preparing to unpack .../libfdisk1_2.29.2-1_amd64.deb ...
Unpacking libfdisk1:amd64 (2.29.2-1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libfdisk1:amd64 (2.29.2-1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62066 files and directories currently installed.)
Preparing to unpack .../libtinfo5_6.0+20161126-1+deb9u1_amd64.deb ...
Unpacking libtinfo5:amd64 (6.0+20161126-1+deb9u1) over (5.9+20140913-1+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libtinfo5:amd64 (6.0+20161126-1+deb9u1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62066 files and directories currently installed.)
Preparing to unpack .../libncursesw5_6.0+20161126-1+deb9u1_amd64.deb ...
Unpacking libncursesw5:amd64 (6.0+20161126-1+deb9u1) over (5.9+20140913-1+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libncursesw5:amd64 (6.0+20161126-1+deb9u1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62066 files and directories currently installed.)
Preparing to unpack .../libselinux1_2.6-3+b3_amd64.deb ...
Unpacking libselinux1:amd64 (2.6-3+b3) over (2.3-2) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libselinux1:amd64 (2.6-3+b3) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62067 files and directories currently installed.)
Preparing to unpack .../libsmartcols1_2.29.2-1_amd64.deb ...
Unpacking libsmartcols1:amd64 (2.29.2-1) over (2.25.2-6) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libsmartcols1:amd64 (2.29.2-1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62067 files and directories currently installed.)
Preparing to unpack .../bash-completion_1%3a2.1-4.3_all.deb ...
Unpacking bash-completion (1:2.1-4.3) over (1:2.1-4) ...
Preparing to unpack .../sysvinit-utils_2.88dsf-59.9_amd64.deb ...
Unpacking sysvinit-utils (2.88dsf-59.9) over (2.88dsf-59) ...
Replacing files in old package initscripts (2.88dsf-59) ...
Preparing to unpack .../util-linux_2.29.2-1_amd64.deb ...
Unpacking util-linux (2.29.2-1) over (2.25.2-6) ...
Replacing files in old package initscripts (2.88dsf-59) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u7) ...
Processing triggers for mime-support (3.58) ...
Setting up util-linux (2.29.2-1) ...
Installing new version of config file /etc/init.d/hwclock.sh ...
Processing triggers for systemd (215-17+deb8u7) ...
(Reading database ... 62084 files and directories currently installed.)
Preparing to unpack .../init-system-helpers_1.48_all.deb ...
Unpacking init-system-helpers (1.48) over (1.22) ...
Replacing files in old package sysv-rc (2.88dsf-59) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up init-system-helpers (1.48) ...
(Reading database ... 62090 files and directories currently installed.)
Preparing to unpack .../libncurses5_6.0+20161126-1+deb9u1_amd64.deb ...
Unpacking libncurses5:amd64 (6.0+20161126-1+deb9u1) over (5.9+20140913-1+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libncurses5:amd64 (6.0+20161126-1+deb9u1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62090 files and directories currently installed.)
Preparing to unpack .../bootlogd_2.88dsf-59.9_amd64.deb ...
Unpacking bootlogd (2.88dsf-59.9) over (2.88dsf-59) ...
Preparing to unpack .../startpar_0.59-3.1_amd64.deb ...
Unpacking startpar (0.59-3.1) over (0.59-3) ...
Processing triggers for systemd (215-17+deb8u7) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up startpar (0.59-3.1) ...
(Reading database ... 62090 files and directories currently installed.)
Preparing to unpack .../insserv_1.14.0-5.4+b1_amd64.deb ...
Unpacking insserv (1.14.0-5.4+b1) over (1.14.0-5) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up insserv (1.14.0-5.4+b1) ...
(Reading database ... 62092 files and directories currently installed.)
Preparing to unpack .../sysv-rc_2.88dsf-59.9_all.deb ...
Unpacking sysv-rc (2.88dsf-59.9) over (2.88dsf-59) ...
Processing triggers for systemd (215-17+deb8u7) ...
Setting up sysvinit-utils (2.88dsf-59.9) ...
Setting up sysv-rc (2.88dsf-59.9) ...
(Reading database ... 62090 files and directories currently installed.)
Preparing to unpack .../base-files_9.9+deb9u1_amd64.deb ...
Unpacking base-files (9.9+deb9u1) over (8+deb8u9) ...
Processing triggers for install-info (5.2.0.dfsg.1-6) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up base-files (9.9+deb9u1) ...
Installing new version of config file /etc/debian_version ...
Configuration file '/etc/issue'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** issue (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/issue 2017-11-06 07:27:04.378514557 -0500
+++ /etc/issue.dpkg-new 2017-07-13 09:04:04.000000000 -0400
@@ -1,10 +1,2 @@
-
-------------------------------------------------------------------------------
-
-Welcome to the Proxmox Virtual Environment. Please use your web browser to
-configure this server - connect to:
-
- https://192.168.1.18:8006/
-
-------------------------------------------------------------------------------
+Debian GNU/Linux 9 \n \l
(END)
518 upgraded, 157 newly installed, 10 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0 B/254 MB of archives.
After this operation, 251 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs... Done
apt-listchanges: Mailing root: apt-listchanges: news for Proxmox
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 62078 files and directories currently installed.)
Removing libkadm5clnt-mit9:amd64 (1.12.1+dfsg-19+deb8u2) ...
Removing libkadm5srv-mit9:amd64 (1.12.1+dfsg-19+deb8u2) ...
Removing libkdb5-7:amd64 (1.12.1+dfsg-19+deb8u2) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62061 files and directories currently installed.)
Preparing to unpack .../libkeyutils1_1.5.9-9_amd64.deb ...
Unpacking libkeyutils1:amd64 (1.5.9-9) over (1.5.9-5+b1) ...
Preparing to unpack .../libk5crypto3_1.15-1+deb9u1_amd64.deb ...
Unpacking libk5crypto3:amd64 (1.15-1+deb9u1) over (1.12.1+dfsg-19+deb8u2) ...
Preparing to unpack .../libgssapi-krb5-2_1.15-1+deb9u1_amd64.deb ...
Unpacking libgssapi-krb5-2:amd64 (1.15-1+deb9u1) over (1.12.1+dfsg-19+deb8u2) ...
Preparing to unpack .../libkrb5-3_1.15-1+deb9u1_amd64.deb ...
Unpacking libkrb5-3:amd64 (1.15-1+deb9u1) over (1.12.1+dfsg-19+deb8u2) ...
Preparing to unpack .../libkrb5support0_1.15-1+deb9u1_amd64.deb ...
Unpacking libkrb5support0:amd64 (1.15-1+deb9u1) over (1.12.1+dfsg-19+deb8u2) ...
Preparing to unpack .../libcomerr2_1.43.4-2_amd64.deb ...
Unpacking libcomerr2:amd64 (1.43.4-2) over (1.42.12-2+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libcomerr2:amd64 (1.43.4-2) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Selecting previously unselected package libfdisk1:amd64.
(Reading database ... 62060 files and directories currently installed.)
Preparing to unpack .../libfdisk1_2.29.2-1_amd64.deb ...
Unpacking libfdisk1:amd64 (2.29.2-1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libfdisk1:amd64 (2.29.2-1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62066 files and directories currently installed.)
Preparing to unpack .../libtinfo5_6.0+20161126-1+deb9u1_amd64.deb ...
Unpacking libtinfo5:amd64 (6.0+20161126-1+deb9u1) over (5.9+20140913-1+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libtinfo5:amd64 (6.0+20161126-1+deb9u1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62066 files and directories currently installed.)
Preparing to unpack .../libncursesw5_6.0+20161126-1+deb9u1_amd64.deb ...
Unpacking libncursesw5:amd64 (6.0+20161126-1+deb9u1) over (5.9+20140913-1+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libncursesw5:amd64 (6.0+20161126-1+deb9u1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62066 files and directories currently installed.)
Preparing to unpack .../libselinux1_2.6-3+b3_amd64.deb ...
Unpacking libselinux1:amd64 (2.6-3+b3) over (2.3-2) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libselinux1:amd64 (2.6-3+b3) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62067 files and directories currently installed.)
Preparing to unpack .../libsmartcols1_2.29.2-1_amd64.deb ...
Unpacking libsmartcols1:amd64 (2.29.2-1) over (2.25.2-6) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libsmartcols1:amd64 (2.29.2-1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62067 files and directories currently installed.)
Preparing to unpack .../bash-completion_1%3a2.1-4.3_all.deb ...
Unpacking bash-completion (1:2.1-4.3) over (1:2.1-4) ...
Preparing to unpack .../sysvinit-utils_2.88dsf-59.9_amd64.deb ...
Unpacking sysvinit-utils (2.88dsf-59.9) over (2.88dsf-59) ...
Replacing files in old package initscripts (2.88dsf-59) ...
Preparing to unpack .../util-linux_2.29.2-1_amd64.deb ...
Unpacking util-linux (2.29.2-1) over (2.25.2-6) ...
Replacing files in old package initscripts (2.88dsf-59) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u7) ...
Processing triggers for mime-support (3.58) ...
Setting up util-linux (2.29.2-1) ...
Installing new version of config file /etc/init.d/hwclock.sh ...
Processing triggers for systemd (215-17+deb8u7) ...
(Reading database ... 62084 files and directories currently installed.)
Preparing to unpack .../init-system-helpers_1.48_all.deb ...
Unpacking init-system-helpers (1.48) over (1.22) ...
Replacing files in old package sysv-rc (2.88dsf-59) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up init-system-helpers (1.48) ...
(Reading database ... 62090 files and directories currently installed.)
Preparing to unpack .../libncurses5_6.0+20161126-1+deb9u1_amd64.deb ...
Unpacking libncurses5:amd64 (6.0+20161126-1+deb9u1) over (5.9+20140913-1+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Setting up libncurses5:amd64 (6.0+20161126-1+deb9u1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 62090 files and directories currently installed.)
Preparing to unpack .../bootlogd_2.88dsf-59.9_amd64.deb ...
Unpacking bootlogd (2.88dsf-59.9) over (2.88dsf-59) ...
Preparing to unpack .../startpar_0.59-3.1_amd64.deb ...
Unpacking startpar (0.59-3.1) over (0.59-3) ...
Processing triggers for systemd (215-17+deb8u7) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up startpar (0.59-3.1) ...
(Reading database ... 62090 files and directories currently installed.)
Preparing to unpack .../insserv_1.14.0-5.4+b1_amd64.deb ...
Unpacking insserv (1.14.0-5.4+b1) over (1.14.0-5) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up insserv (1.14.0-5.4+b1) ...
(Reading database ... 62092 files and directories currently installed.)
Preparing to unpack .../sysv-rc_2.88dsf-59.9_all.deb ...
Unpacking sysv-rc (2.88dsf-59.9) over (2.88dsf-59) ...
Processing triggers for systemd (215-17+deb8u7) ...
Setting up sysvinit-utils (2.88dsf-59.9) ...
Setting up sysv-rc (2.88dsf-59.9) ...
(Reading database ... 62090 files and directories currently installed.)
Preparing to unpack .../base-files_9.9+deb9u1_amd64.deb ...
Unpacking base-files (9.9+deb9u1) over (8+deb8u9) ...
Processing triggers for install-info (5.2.0.dfsg.1-6) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up base-files (9.9+deb9u1) ...
Installing new version of config file /etc/debian_version ...
Configuration file '/etc/issue'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** issue (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/issue 2017-11-06 07:27:04.378514557 -0500
+++ /etc/issue.dpkg-new 2017-07-13 09:04:04.000000000 -0400
@@ -1,10 +1,2 @@
-
-------------------------------------------------------------------------------
-
-Welcome to the Proxmox Virtual Environment. Please use your web browser to
-configure this server - connect to:
-
- https://192.168.1.18:8006/
-
-------------------------------------------------------------------------------
+Debian GNU/Linux 9 \n \l
(END)