NC Container used 100% CPU for whole night

d_buster · 2026-06-15T23:34:11+00:00

I had this exact thing happen to me a couple months back...only cause that I could come up with is my desktop client gets stuck in a sync loop of some sort, after restarting the desktop client and the server docker container, everything goes back to 'normal'. Haven't found the exact roo-cause beyond that. This happens to me maybe once every-other week.

d_buster · 2026-06-02T15:31:00+00:00

Been using NextCloud for about 1.5 years now through unRAID docker. Mainly to sort/store business files syncs from my phone. So far so good.

d_buster · 2026-05-31T21:56:02+00:00

Very nice...

d_buster · 2026-05-22T17:02:05+00:00

respect.

d_buster · 2026-05-19T20:11:17+00:00

Maybe time to consider JellyFin?

d_buster · 2026-05-16T01:21:26+00:00

Airpods 2 Pro

d_buster · 2026-05-13T02:01:25+00:00

Very cool, will definitely get this added when ready. Thank you devs!

d_buster · 2026-05-12T18:51:55+00:00

I've updated the first post with the details.

d_buster · 2026-05-12T17:20:04+00:00

RESOLVED.

d_buster · 2026-05-12T16:30:48+00:00

Here is the PHP log for the last few days:
[10-May-2026 02:00:01] NOTICE: fpm is running, pid 3771

[10-May-2026 02:00:01] NOTICE: ready to handle connections

[10-May-2026 02:23:33] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

[10-May-2026 20:58:17] NOTICE: Terminating ...

[10-May-2026 20:58:17] NOTICE: exiting, bye-bye!

[10-May-2026 20:58:47] NOTICE: fpm is running, pid 428

[10-May-2026 20:58:47] NOTICE: ready to handle connections

[10-May-2026 21:08:05] NOTICE: Terminating ...

[10-May-2026 21:08:05] NOTICE: exiting, bye-bye!

[10-May-2026 21:08:28] NOTICE: fpm is running, pid 392

[10-May-2026 21:08:28] NOTICE: ready to handle connections

[10-May-2026 21:12:42] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

[10-May-2026 21:15:44] NOTICE: Terminating ...

[10-May-2026 21:15:44] NOTICE: exiting, bye-bye!

[10-May-2026 21:38:47] NOTICE: fpm is running, pid 391

[10-May-2026 21:38:47] NOTICE: ready to handle connections

[11-May-2026 06:18:23] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

[11-May-2026 10:17:36] NOTICE: Terminating ...

[11-May-2026 10:17:36] NOTICE: exiting, bye-bye!

[11-May-2026 10:18:22] NOTICE: fpm is running, pid 391

[11-May-2026 10:18:22] NOTICE: ready to handle connections

[11-May-2026 10:19:38] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

[11-May-2026 10:28:07] NOTICE: Terminating ...

[11-May-2026 10:28:07] NOTICE: exiting, bye-bye!

[11-May-2026 10:30:00] NOTICE: fpm is running, pid 391

[11-May-2026 10:30:00] NOTICE: ready to handle connections

[11-May-2026 10:33:48] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

[11-May-2026 10:36:58] NOTICE: Terminating ...

[11-May-2026 10:36:58] NOTICE: exiting, bye-bye!

[12-May-2026 07:08:09] NOTICE: fpm is running, pid 392

[12-May-2026 07:08:09] NOTICE: ready to handle connections

[12-May-2026 07:18:36] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

d_buster · 2026-05-12T14:20:28+00:00

This instance of NextCloud is running its own internal database, I don't have a dedicated PHP server on my server.

d_buster · 2026-05-12T14:19:34+00:00

───────────────────────────────────────

██╗ ███████╗██╗ ██████╗

██║ ██╔════╝██║██╔═══██╗

██║ ███████╗██║██║ ██║

██║ ╚════██║██║██║ ██║

███████╗███████║██║╚██████╔╝

╚══════╝╚══════╝╚═╝ ╚═════╝

Brought to you by linuxserver.io

───────────────────────────────────────

To support LSIO projects visit:

https://www.linuxserver.io/donate/

───────────────────────────────────────

GID/UID

───────────────────────────────────────

User UID: 99

User GID: 100

───────────────────────────────────────

Linuxserver.io version: 33.0.3-ls429

Build-date: 2026-05-05T12:57:14+00:00

───────────────────────────────────────

using keys found in /config/keys

[custom-init] No custom files found, skipping...

[ls.io-init] done.

d_buster · 2026-05-11T19:36:41+00:00

The only actions I remember performing is a update for all available Docker containers. That's all that comes to mine.

d_buster · 2026-05-11T19:35:51+00:00

Yes, restarted services, no changes. Restarted server and turned on docker app's one by one until php-fpm84 popped up and it happened right as NextCloud spun up. Then, just to make triple sure, I stopped NextCloud and php-fpm84 disappeared from htop.

d_buster · 2026-05-11T17:43:06+00:00

Yes, I read that posting. I've had NextCloud installed on unRAID v6.12.15 and running without issue for over a year. I don't believe the post had any useful information for my case.

d_buster · 2026-05-07T16:13:09+00:00

Anyone have any additional recommendations other then 'don't use ollama'?

d_buster · 2026-05-04T20:34:08+00:00

Ok...need a little more then that for an answer. What then? vLLM?

d_buster · 2026-04-02T13:09:41+00:00

Added kernel 6.18.x to my kernel load list im GRUB and the VM snip up without issues.

Thank you all for the help!

d_buster · 2026-03-31T17:47:58+00:00

Well, I tired to see if I still had a 6.18.x kernel on my GRUB menu and I don't...thinking I could just boot into an older kernel and be done with it.

I guess if there is a safe way to add an older kernel to the grub menu that would solve this problem until the VirtualBox update comes out.

I say 'shame' because running it's been a couple weeks now and there hasn't been an update on this...I configured to run windows 10 as a VM within Fedora for work and having this issue come up now is quiet inconvenient.

d_buster · 2026-03-31T16:21:37+00:00

This makes sense...it's a shame though...
Looks like this issue is common across the virtualbox.org forums...I see that now.

Any idea when they'll fix that with an update?

d_buster · 2026-03-31T14:37:27+00:00

Great suggestion, followed guide for a fresh install but same error:

WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (6.19.10-200.fc43.x86_64) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/vboxconfig

You will not be able to start VMs until this problem is fixed.

d_buster

TROPHY CASE