AMP
AMP copied to clipboard
CubeCoders
Project Zomboid issue with CPU
Bug Report
System Information
- Operating System: Debian 10
- AMP version and build date: v2.3.4.3, built 12/07/2022 13:00
- Which AMP release stream you're using: Mainline
I confirm:
- [x] that I have searched for an existing bug report for this issue.
- [x] that I am using the latest available version of AMP.
- [x] that my operating system is up-to-date.
Symptoms
- What are you trying to do? Running project zomboid
- What are you expecting to happen? The server running well with processor used and no error on logs
- What is actually happening? There is 0% processor usage while server is running and found 2 errors line
Reproduction
After clean installation and update project zomboid, I start the server and found the processor still on 0% while there are couple of people is playing on the server. Then I restart the server to see if it going to fix and found errors on console logs that said:
[0.108s][warning][os] Invalid processor id reported by the operating system (got processor id 28, valid processor id range is 0-5) [0.108s][warning][os] Falling back to assuming processor id is 0. This could have a negative impact on performance.
The ram consumption is working fine but one of my friend told me there is a lag when he tried to zoom out so I assume this is an issue with the processor. I tried to contact with my vps provider and they recommended me to report this issue on this github.
Right click the instance and view logs. Share the whole log using something like hastebin. That error seems to be coming from PZ rather than AMP though. Not sure there's anything we can do to help that.
https://www.toptal.com/developers/hastebin/jebigajeru.yaml
I remove my IP and user if thats alright with you
I've seen an issue like this before when the host (in my case an LXD container) stops reporting CPU info correctly. The ZGC algo that PZ uses by default for garbage collection relies on getting processor info (apparently the only algo that does) and hence the issue. In my case a reboot of the container fixed it
I've seen an issue like this before when the host (in my case an LXD container) stops reporting CPU info correctly. The ZGC algo that PZ uses by default for garbage collection relies on getting processor info (apparently the only algo that does) and hence the issue. In my case a reboot of the container fixed it
May I know how to reboot it? I'm new with PZ