I want to use it to run 30 - 50 browsers scraping data for me using Nodejs, playwright.

Any recommendations?

One of my box (KVM, 2 cores, if it matters), basically idling for nearly 2 years (1 simple instance of Syncthing + no-traffic websites), monitored with the HetrixTools agent (The Best!) has just been stopped because "constantly consuming 100-200% ( fully utilized 1-2 cores )".
1> Graphs from HT show nothing,
2> my personal checkup shows nothing either: ufw & failban clean, nothing in any log...

While I can find my way around, I'm not any kind of expert with linux: Debian 10 for that one. And I would appreciate any kind of lead, track, where-to-look stuff

Thanks for any light!

In what I believe are random moments of the day, I receive a Hetrixtools notification that my stuff is down, and it is. Can't even login. In case it happens when I am logged in, I can't even give a command.

When it's over, uptime reports insane values, like 49.6 38.5 22.9 or something.

The issue: htop does not report anything out of the ordinary, docker stats the same.

All I see is typical processes which are using 2-10% of the CPU and small spikes of the usual suspects (a mysql process using 60% for a second or so).

Hetrixtools CPU monitor is even flatter. This is the last 24 hours according to it.

It does not make sense. I can't see what it is when it happens, and when I can see, nothing looks weird.
Anything else I could look at? It's even happening as I am writing this post now.

Edit: this looks ridicolous

To add to this, I am using Ubuntu 20.04, ufw enabled.

We present CacheOut, a new speculative execution attack that is capable of leaking data from Intel CPUs across many security boundaries. We show that despite Intel's attempts to address previous generations of speculative execution attacks, CPUs are still vulnerable, allowing attackers to exploit these vulnerabilities to leak sensitive data.

Moreover, unlike previous MDS issues, we show in our work how an attacker can exploit the CPU's caching mechanisms to select what data to leak, as opposed to waiting for the data to be available. Finally, we empirically demonstrate that CacheOut can violate nearly every hardware-based security domain, leaking data from the OS kernel, co-resident virtual machines, and even SGX enclaves.

Source

Microcode updates are supposedly already available. Best update ASAP, if you're running Intel and haven't yet... you know the drill.