Hello all,
I noticed today that PVE 7 is now available, and attempted the upgrade from 6.4. This all seemed to go through smoothly, and I indeed appear to be running 7.1-5 now, though attempting to install updates now produces an error like below:
I have done multiple reboots and attempted to re-run
Having spent around an hour or so attempting various fixes posted on the forum, I'm at a bit of a loss, hence this post. Judging from the replies to other threads I found, hopefully some of the results below will be of use - apologies if this ends up being quite the wall of text!
As per the error message above, running
And running
The contents of this .JSON file just show
As one last bit of extra info, a couple of threads mentioned the /etc/hosts file. Having looked there, I can see that a domain has made its way in and can only assume that this was from when I was messing around on my router the other day and temporarily had a "default domain" specified. Let me know if this is worth looking at and I can share some more info.
Many thanks,
Chris
I noticed today that PVE 7 is now available, and attempted the upgrade from 6.4. This all seemed to go through smoothly, and I indeed appear to be running 7.1-5 now, though attempting to install updates now produces an error like below:
Code:
apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... 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]
Setting up pve-manager (7.1-5) ...
machine-id check OK
Job for pvescheduler.service failed because a timeout was exceeded.
See "systemctl status pvescheduler.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess 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-veI have done multiple reboots and attempted to re-run
apt-get update and apt-get dist-upgrade again, but Proxmox still hangs on the "machine-id check OK" line for a while, before producing the same timeout error.Having spent around an hour or so attempting various fixes posted on the forum, I'm at a bit of a loss, hence this post. Judging from the replies to other threads I found, hopefully some of the results below will be of use - apologies if this ends up being quite the wall of text!
As per the error message above, running
systemctl status pvescheduler.service produces:
Code:
● pvescheduler.service - Proxmox VE scheduler
Loaded: loaded (/lib/systemd/system/pvescheduler.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Fri 2021-11-19 15:59:36 GMT; 23min ago
Process: 6970 ExecStart=/usr/bin/pvescheduler start (code=exited, status=0/SUCCESS)
Tasks: 2 (limit: 77197)
Memory: 187.6M
CPU: 3.371s
CGroup: /system.slice/pvescheduler.service
├─4652 pvescheduler
└─6973 pvescheduler
Nov 19 16:21:58 r610 pvescheduler[12161]: server stopped
Nov 19 16:22:00 r610 pvescheduler[12163]: ERROR: invalid json data in '/var/lib/pve-manager/pve-replication-state.json'
Nov 19 16:22:00 r610 pvescheduler[12163]: got shutdown request, signal running jobs to stop
Nov 19 16:22:00 r610 pvescheduler[12163]: server stopped
Nov 19 16:22:58 r610 pvescheduler[12386]: ERROR: invalid json data in '/var/lib/pve-manager/pve-replication-state.json'
Nov 19 16:22:58 r610 pvescheduler[12386]: got shutdown request, signal running jobs to stop
Nov 19 16:22:58 r610 pvescheduler[12386]: server stopped
Nov 19 16:23:00 r610 pvescheduler[12388]: ERROR: invalid json data in '/var/lib/pve-manager/pve-replication-state.json'
Nov 19 16:23:00 r610 pvescheduler[12388]: got shutdown request, signal running jobs to stop
Nov 19 16:23:00 r610 pvescheduler[12388]: server stoppedAnd running
journalctl -xe shows these errors repeating every minute or so:
Code:
Nov 19 16:27:58 r610 pvescheduler[13470]: ERROR: invalid json data in '/var/lib/pve-manager/pve-replication-state.json'
Nov 19 16:27:58 r610 pvescheduler[13470]: got shutdown request, signal running jobs to stop
Nov 19 16:27:58 r610 pvescheduler[13470]: server stopped
Nov 19 16:28:00 r610 pvescheduler[13472]: ERROR: invalid json data in '/var/lib/pve-manager/pve-replication-state.json'
Nov 19 16:28:00 r610 pvescheduler[13472]: got shutdown request, signal running jobs to stop
Nov 19 16:28:00 r610 pvescheduler[13472]: server stopped
Nov 19 16:28:07 r610 ddclient[13507]: WARNING: file /etc/ddclient.conf, line 9: Invalid Value for keyword 'login' = ''
Nov 19 16:28:58 r610 pvescheduler[13690]: ERROR: invalid json data in '/var/lib/pve-manager/pve-replication-state.json'
Nov 19 16:28:58 r610 pvescheduler[13690]: got shutdown request, signal running jobs to stop
Nov 19 16:28:58 r610 pvescheduler[13690]: server stopped
Nov 19 16:29:00 r610 pvescheduler[13693]: ERROR: invalid json data in '/var/lib/pve-manager/pve-replication-state.json'
Nov 19 16:29:00 r610 pvescheduler[13693]: got shutdown request, signal running jobs to stop
Nov 19 16:29:00 r610 pvescheduler[13693]: server stoppedThe contents of this .JSON file just show
UP, but I'm not sure what it should look like really. Aside from something clearly being wrong here, everything else seems fine at the moment - VMs run OK, the web GUI looks good, I just can't get past this update issue... I have seen the suggestion of running apt install --reinstall pve-manager, though that person was not experiencing quite the same symptoms and I'm not sure of the implications of running this.As one last bit of extra info, a couple of threads mentioned the /etc/hosts file. Having looked there, I can see that a domain has made its way in and can only assume that this was from when I was messing around on my router the other day and temporarily had a "default domain" specified. Let me know if this is worth looking at and I can share some more info.
Many thanks,
Chris
Last edited:
