[PVE-User] pveproxy dying, node unusable

[Lindsay Mathieson]

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.


[21360.917460] INFO: task pveproxy:18122 blocked for more than 120 seconds.
[21360.917465]       Tainted: P           O    4.4.95-1-pve #1
[21360.917469] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
[21360.917473] pveproxy        D ffff8807799cbdf8     0 18122      1 
0x00000004
[21360.917476]  ffff8807799cbdf8 ffff880ff114a840 ffff880ff84fc600 
ffff880fd9979c00
[21360.917478]  ffff8807799cc000 ffff880fc30143ac ffff880fd9979c00 
00000000ffffffff
[21360.917480]  ffff880fc30143b0 ffff8807799cbe10 ffffffff818643b5 
ffff880fc30143a8
[21360.917482] Call Trace:
[21360.917485]  [<ffffffff818643b5>] schedule+0x35/0x80
[21360.917487]  [<ffffffff8186466e>] schedule_preempt_disabled+0xe/0x10
[21360.917489]  [<ffffffff81866369>] __mutex_lock_slowpath+0xb9/0x130
[21360.917491]  [<ffffffff818663ff>] mutex_lock+0x1f/0x30
[21360.917493]  [<ffffffff812211ca>] filename_create+0x7a/0x160
[21360.917495]  [<ffffffff81222163>] SyS_mkdir+0x53/0x100
[21360.917497]  [<ffffffff818684f6>] entry_SYSCALL_64_fastpath+0x16/0x75


Is it possible to rollback the last update?

-- 
Lindsay Mathieson