Closed avgDesti closed 3 weeks ago
IceOfWraith
commented
2 years ago 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.
avgDesti
commented
2 years ago https://www.toptal.com/developers/hastebin/jebigajeru.yaml
I remove my IP and user if thats alright with you
Greelan
commented
2 years ago 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
avgDesti
commented
2 years ago 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
Greelan
commented
2 years ago Just reboot the VPS
Bug Report
System Information
I confirm:
Symptoms
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.