~~~
When you wrote in your initial post that you're on Ubuntu 22.04.x (with x as unspecified), I'm wondering why you've been on such an old kernel like 5.15.0? (I'm not entirely convinced that this matters, because if kernel 5.15.0 supports your hardware well enough, it should run with it just fine.)
I usually accept Ubuntu kernel updates when they're offered by the Ubuntu update process. Never had an issue with it so far.
Now i'm full paranoid, i turn off all services and nothing happened since 33minutes, i believe it's a security issue.
i add a .htaccess file in the database directory, i'm mad but now 42minutes quiet.
Are you sure, you know what you're doing?? I'm not convinced when you place a
.htaccess file and think this might solve something or is appropriate at all. And your reasoning it could be a security issue is very likely flawed.
Of course, nobody here has an idea what services are running on your Ubuntu and what components you've installed. But... I clearly doubt that you know which services you can safely turn off or better shouldn't.
With my new kernel i have debugged the problem ;
due to memory pressure for /user.slice/user-1000.slice/
[email protected] being 71.38% > 50.00% for > 20s with reclaim activity
Bitcoin-qt takes 12GB of RAM while downloading the blockchain.
Now we're coming to something more concrete.
journalctl --no-pager --since "2024-09-18 21:47" --until "2024-09-18 21:49"
sept. 18 21:47:01 localhost systemd-oomd[763]: Killed /user.slice/user-1000.slice/
[email protected]/app.slice/app-org.gnome.Terminal.slice/vte-spawn-2b8e69c4-9a86-45f6-b1a5-90c523681b99.scope due to memory pressure for /user.slice/user-1000.slice/
[email protected] being 71.38% > 50.00% for > 20s with reclaim activity
sept. 18 21:47:01 localhost systemd[8336]: vte-spawn-2b8e69c4-9a86-45f6-b1a5-90c523681b99.scope: systemd-oomd killed 25 process(es) in this unit.
sept. 18 21:47:01 localhost systemd[8336]: vte-spawn-2b8e69c4-9a86-45f6-b1a5-90c523681b99.scope: Consumed 28min 49.683s CPU time.
sept. 18 21:47:02 localhost gnome-shell[8515]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
_registerItem/<@/usr/share/gnome-shell/extensions/
[email protected]/statusNotifierWatcher.js:106:59
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_nameOwnerChanged@/usr/share/gnome-shell/extensions/
[email protected]/appIndicator.js:162:14
Async*_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
AppIndicatorsNameWatcher/this._watcherId<@/usr/share/gnome-shell/extensions/
[email protected]/util.js:212:22
If the OOM daemon has reasons to kick in (either by too high memory consumption pressure of some processes or when it's ill configuered; I doubt the latter, because unlikely you fiddled with it or it's default config is bad in the first place), it will just kill processes to reclaim memory and lower memory pressure. Likely your Bitcoin Core won't be spared...
The OOM daemon shouldn't need to slice through your processes!
Question is why your Bitcoin-Qt is allowed to grab that much memory, even when you have 16GB installed. It won't do it on it's own (my guess, as it doesn't seem likely to me, that memory demand of v27 branch has changed that drastically from v26 that I'm still on), there is likely an ill-configuered setting for Bitcoin Core OR other apps and stuff that runs on your Ubuntu needs too much at the same time.
My daily internet driver with Ubuntu has only 8GB RAM, a bitcoind with a watch-only wallet runs permanently in the background. I surf with Firefox and quite a bunch of tabs open. That's basically it. No visible issues with high memory pressure on my system and Bitcoin Core and Firefox run rock-solid.
Have a closer look at
bitcoin.conf and
settings.json in your
~/.bitcoin/ directory (not sure if Bitcoin-Qt stores settings somewhere else).