My computer (debian bullseye) keeps shutting down after I run an instance of milvus(vector database), and I need milvus to do vector search for the app.
At first I thought it was thermal problem, but after more than 30 minutes of stress-ng -a 32, It really didn't seem like one.
Also, I noticed that thermals reported by stress-ng by using --tz was way lower than what sensors(coretemp) reported (stress-ng: ~45C, sensors: ~95C)
I also checked journalctl and syslog. Journalctl only reported "BOOT" without any mentioning of why, and syslog showed lots of @ signs.
Remembered reading that @ on syslog was NULL character, and likely caused by hardware issues, but the funny part is that it only happens when I launch milvus with docker compose, which takes significantly less CPU than stress-ng
Could it be a problem with the system shutting down the computer due to false alarm, or something else?
It's really strange since it only started happening yesterday, and before that It worked fine
I'll attach a screenshot of syslog and journalctl.
Thanks In advance, and as I need this as quickly as possible, please don't hesitate to give me an advice
