> On 20/12/2017 12:41 AM, Lindsay Mathieson wrote:
> Is it possible to rollback the last update?
I'd backup contents of /etc/network/interfaces, /etc/pve/qemu-server (vm config
files), vm disk images, and anything else you don't want to lose and do a full
reinstall on the sick nodes. Last time
nb. This is with Proxmox 4
On 20/12/2017 10:13 AM, Lindsay Mathieson wrote:
On 20/12/2017 12:41 AM, Lindsay Mathieson wrote:
Having to hard reset them as I need them usable again before work
starts.
And pveproxy hung on both nodes again this morning, this is becoming
quite a problem for us.
On 12/12/2017 2:14 AM, Emmanuel Kasper wrote:
Hi Lindsay
As a quick check, is the cluster file system mounted on /etc/pve and can
you read files there normally ( ie cat /etc/pve/datacenter.cfg working ) ?
Are the node storages returning their status properly ?
(ie pvesm status does not hang)
On 12/12/2017 2:14 AM, Emmanuel Kasper wrote:
Hi Lindsay
As a quick check, is the cluster file system mounted on /etc/pve and can
you read files there normally ( ie cat /etc/pve/datacenter.cfg working ) ?
Unfortunately I hard reset both nodes as I needed them up. But a pvecm
status showed
On 12/11/2017 04:50 PM, Lindsay Mathieson wrote:
> Also I was unable to connect to the VM's on those nodes, not even via RDP
>
> On 12/12/2017 1:46 AM, Lindsay Mathieson wrote:
>>
>> I dist-upraded two nodes yesterday. Now both those nodes have multiple
>> unkilliable pveproxy processes. dmesg
Also I was unable to connect to the VM's on those nodes, not even via RDP
On 12/12/2017 1:46 AM, Lindsay Mathieson wrote:
I dist-upraded two nodes yesterday. Now both those nodes have multiple
unkilliable pveproxy processes. dmesg has many entries of:
[50996.416909] INFO: task
