pvestad crash

A

AlexDev_

New Member
Mar 1, 2024
3
3
3
Hi, I have been using proxmox for a month now but I am getting this error:

Code: 
Apr 03 21:43:10 ServerAlex systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV
Apr 03 21:43:10 ServerAlex systemd[1]: pvestatd.service: Failed with result 'signal'.
Apr 03 21:43:10 ServerAlex systemd[1]: pvestatd.service: Consumed 1min 21.680s CPU time.

I also attached "journalctl -xeb-1" output.
I also tried to update microcode but it didn't help.

My setup:

b450 gaming plus
ryzen 5 3600
16 GB ram ddr4

Cpu usage is most of the time under 1% and ram under 30/40%.

i tried MemTest but it passed all 12 tests.
photo_2024-04-03_22-26-06.jpg

I tried reinstalling proxmox, before on top of debian and now as os.
I tried multiple ssds, but they game the same result.
I'm on 8.1.0, with updated packages.
 

Attachments

I am experiencing the same issue. I will be keen to find out if your issue gets resolved.

image.png
 
Last edited:
Thank you so much for providing that info. I have since disabled everything in the BIOS to do with c-states, turbo boosting, etc. Literally any setting that I could get my hands on that looked like it changed how the CPU ran in any way, to either boost it or save power.

The system seems stable now. I'll have to remember to come back if we experience problems in the coming days, but it's been stable for a few days already now. I wanted to leave it a while before posting a response to see if it worked.
 
Last edited:
  • Like
Reactions: dsysemcrash2024 and AlexDev_
Programster said:
Thank you so much for providing that info. I have since disabled everything in the BIOS to do with c-states, turbo boosting, etc. Literally any setting that I could get my hands on that looked like it changed how the CPU ran in any way, to either boost it or save power.

The system seems stable now. I'll have to remember to come back if we experience problems in the coming days, but it's been stable for a few days already now. I wanted to leave it a while before posting a response to see if it worked.
Click to expand...
Thanks @AlexDev_ and @Programster . I'm having the same issue with one node. Kept seeing the below CPU errors after running journalctl -r -u pvestatd.service

Symptoms were that the one node in the cluster would regulary show question mark. Checking the pvestatd.service showed it to be stopped

Dec 27 23:46:48 homevs102 systemd[1]: pvestatd.service: Consumed 30.933s CPU time.
Dec 27 23:46:48 homevs102 systemd[1]: pvestatd.service: Failed with result 'signal'.
Dec 27 23:46:48 homevs102 systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV

Dec 21 00:13:03 homevs102 systemd[1]: pvestatd.service: Consumed 2h 8.912s CPU time.
Dec 21 00:13:03 homevs102 systemd[1]: pvestatd.service: Failed with result 'signal'.
Dec 21 00:13:03 homevs102 systemd[1]: pvestatd.service: Main process exited, code=killed, status=6/ABRT

Went into the BIOS and changed the C1E option to disabled (Lenovo M710q). WIll monitor and see what happens.
 
Last edited:
Disabling all the CPU stuff worked for me (dont remember having any issues since, and that was quite some time ago), and I'm now pretty certain it was to do with the voltage issues that got reported in the news to do with the 13th and 14th gen intel CPUs (we had a 14th gen i9).


If you continue to experience issues, I would suggest checking and making sure you have latest BIOS/firmware versions, and then checking to see if there are any other options in there that have anything to do with the voltage of the CPU. E.g. energy saving or "boost" / overclocking and disable them all.

I think this may be the link you would want for updated bios versions for that computer (M710q)
 
You must log in or register to reply here.
Top Bottom