Ridiculous load average and CPU usage

I’m using the atomic rpm packages.

For some reason, any scans just use a huge amount of resources and it seems to be exhausting connections to postgres.

greenbone-security-assistant-22.5.0

Scans are extremely slow… in fact it’s doesn’t seem to be making any progress. I don’t see any obvious errors in the logs.

postgres 20108 0.0 0.1 718804 29992 ? Ss 21:41 0:00 postgres: gvm gvmd [local] idle
gvm 20111 3.2 1.0 442612 174952 ? R 21:41 0:24 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20113 0.0 0.1 717780 23872 ? Ss 21:41 0:00 postgres: gvm gvmd [local] idle
gvm 20118 3.2 1.0 442612 174952 ? R 21:41 0:24 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20120 0.0 0.1 717780 22932 ? Ss 21:41 0:00 postgres: gvm gvmd [local] idle
gvm 20134 3.2 1.0 442612 174900 ? R 21:42 0:24 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20136 0.0 0.2 726780 36252 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20137 3.1 1.0 442612 174900 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20139 0.0 0.2 729372 36744 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20140 3.1 1.0 442612 174900 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20142 0.0 0.2 728892 37184 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20143 3.1 1.0 442612 174900 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20145 0.0 0.1 718560 27008 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20146 3.1 1.0 442612 174900 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
gvm 20147 3.1 1.0 442612 174900 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20149 0.0 0.1 717780 22936 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
postgres 20152 0.0 0.2 719672 32956 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20154 3.1 1.0 442612 174900 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20156 0.0 0.1 718560 27328 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20172 3.1 1.0 442612 174840 ? R 21:42 0:22 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20174 0.0 0.2 719792 32948 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20176 3.1 1.0 442612 174840 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20178 0.0 0.2 729364 36752 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20179 3.1 1.0 442612 174840 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
gvm 20180 3.2 1.0 442612 174840 ? R 21:42 0:23 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20182 0.0 0.1 718560 27140 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
postgres 20184 0.0 0.2 728892 37248 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20198 3.1 1.0 442612 174904 ? R 21:42 0:22 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20200 0.0 0.2 719672 33020 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20202 3.1 1.0 442612 174904 ? R 21:42 0:22 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20204 0.0 0.2 729364 36812 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
gvm 20205 3.1 1.0 442612 174904 ? R 21:42 0:22 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
gvm 20206 3.1 1.0 442612 174904 ? R 21:42 0:22 gvmd: gvmd: Se --osp-vt-update=/var/run/ospd/ospd-openvas.sock
postgres 20208 0.0 0.2 728892 37192 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle
postgres 20210 0.0 0.1 718568 27152 ? Ss 21:42 0:00 postgres: gvm gvmd [local] idle

ps axuww | grep ospd-openvas.sock | wc -l
202

ps axuww | grep “postgres: gvm” | wc -l
199

Is this normal?

I think you have to contact atomcorp to troubleshoot since we don’t even know which source code or copy of GVM is being installed from their repo.

I found a post that seemed to suggest 22.5.2 of gvmd has issues. I upgraded to 22.5.4 and it seems the problem is solved. No more ridiculous load and I no longer see the flood of gvmd/postgres processes. Waiting for my first scan to complete now.

This issue: Gvmd cpu usage

Perhaps you can suggest to the package maintainers to update.

1 Like

Done. Thank you.