OMV and php-fpm are only using 24% of one cpu though. There is something else going on with your system. If you stop omv and php-fpm, does the load go to 0?
sudo systemctl stop openmediavault-engined
sudo systemctl stop php8.2-fpm # if you are on omv7
sudo systemctl stop php7.4-fpm # if you are on omv6
I stopped openmediavault-engined and php7.4-fpm, but nothing helps.
Do you have any idea to find the problem? I really want to find the reason before reinstalling OMV
output from Diagnostics->Process (the original info are too long, so I put the entire in gist
top - 09:39:58 up 8:57, 0 users, load average: 2.00, 2.05, 2.02
Tasks: 142 total, 1 running, 139 sleeping, 0 stopped, 2 zombie
%Cpu(s): 57.1 us, 5.7 sy, 0.0 ni, 37.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 7778.8 total, 4571.4 free, 2618.6 used, 588.8 buff/cache
MiB Swap: 977.0 total, 977.0 free, 0.0 used. 4908.5 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
29056 openmed+ 20 0 202620 18456 12140 S 18.8 0.2 0:00.56 php-fpm7.4
29293 root 20 0 73268 16944 6688 S 6.2 0.2 0:00.01 omv-engined
1 root 20 0 169528 14176 7784 S 0.0 0.2 0:04.86 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 slub_flushwq
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns
8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-events_highpri
10 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
11 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_kthread
12 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_rude_kthread
13 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_trace_kthread
14 root 20 0 0 0 0 S 0.0 0.0 0:00.03 ksoftirqd/0output from htop:
you can see the cpu 0 and 1 are always 100%
That is the OMV web interface. Removing docker and compose won't help you there. You could try removing different widgets from the dash to reduce the load.
Downgrading is not supported and just avoiding the problem.
you can see my screenshots carefully. this high CPU usage is unnormal because the OMV web interface cannot use all the two core at all the time, you can see that from the CPU Usage in my first screenshot.
I tried removing all the widgets from the dash, but nothing help.
What problem? I still don't know what jata1's problem was. The docker line with the missing field is as designed because it is showing the status of docker itself in the first line.
If the widget is reporting something wrong with the container info, then the output of docker container ls is wrong (very doubtful). Nothing the widget can since it is just passing that exact info along. https://github.com/OpenMediaVa…ned/rpc/compose.inc#L1355
I upgraded openmediavault from 6.9.12-3 to 6.9.13-1 by `apt upgrade` at Feb.4th.
Then I found the unnormal high CPU usage caused by `php-fpm: pool openmediavault-webgui`.
I had uninstall docker and compose but the problem still exist.
I wonder how to downgrade the openmediavault by `apt-get`.
I upgrade my system yesterday, and then met the same problem even I remove compose later.
What do you mean you can't use omv-compose anymore? If you leave the path blank, you are responsible for creating a working /etc/docker/daemon.json.
If I left the path blank, everytime I use the omv-compose, it reports an error:
Please set shared folder for file storage.
OMV\Exception: Please set shared folder for file storage. in /usr/share/openmediavault/engined/rpc/compose.inc:92
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/compose.inc(219): OMVRpcServiceCompose->getComposePath(Array)
#1 [internal function]: OMVRpcServiceCompose->getFileList(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('getFileList', Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusMG...', '/tmp/bgoutputkB...')
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#6 /usr/share/openmediavault/engined/rpc/compose.inc(273): OMV\Rpc\ServiceAbstract->callMethodBg('getFileList', Array, Array)
#7 [internal function]: OMVRpcServiceCompose->getFileListBg(Array, Array)
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#9 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getFileListBg', Array, Array)
#10 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'getFileListBg', Array, Array, 1)
#11 {main}On install, it defaults the field to the directory listed in docker info but nothing applies those settings. It does not backup the previous files. If you install the plugin, set the shared folder, make the docker path blank, it shouldn't have overwritten you daemon.json.
hello, if I make the docker path blank, I cannot use omv-compose anymore; but if I set a docker path blank, the daemon.json will be rewritten. How should I do?