[PVE-User] pveproxy dying, node unusable

Emmanuel Kasper e.kasper at proxmox.com
Mon Dec 11 17:14:37 CET 2017


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 has many entries of:
>>
>>     [50996.416909] INFO: task pveproxy:6798 blocked for more than 120
>>     seconds.
>>     [50996.416914]       Tainted: P           O 4.4.95-1-pve #1
>>     [50996.416918] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
>>     disables this message.
>>     [50996.416922] pveproxy        D ffff8809194e3df8 0  6798      1
>>     0x00000004
>>     [50996.416925]  ffff8809194e3df8 ffff880ff6f5ed80 ffff880ff84fe200
>>     ffff880fded5e200
>>     [50996.416927]  ffff8809194e4000 ffff880fc7fb43ac ffff880fded5e200
>>     00000000ffffffff
>>     [50996.416929]  ffff880fc7fb43b0 ffff8809194e3e10 ffffffff818643b5
>>     ffff880fc7fb43a8
>>
>>
>> qm list hangs
>>
>> Node vms do not respond in web gui
>>
>> The node I did not upgrade is fine.


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)



More information about the pve-user mailing list