Dear support team,
As the member Curtain, I had also faced this issue 2 days ago. In my case, it was in 2 different servers, which are our develop servers with several VM in them.
I had the same situation and the same output as Curtain in pveproxy.service. The service pveproxy.service restart...