Recently, I've noticed the web interface a bit sluggish. Upon examination of 
the server, I noticed the openvasmd process stuck at 100% CPU. There was no 
active scan going on, and I'm the only one that uses this server. Nothing 
should have been utilizing the CPU like that. Here is some of the specifics I 

CentOS 7 (latest patches)
8x vCPU and 16 GB RAM

Results of top:

Tasks: 254 total, 2 running, 252 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.6 us, 7.2 sy, 0.0 ni, 87.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 16249820 total, 8476724 free, 1105044 used, 6668052 buff/cache
KiB Swap: 4063228 total, 4063228 free, 0 used. 14679544 avail Mem

69700 root 20 0 445832 152984 1820 R 100.0 0.9 5329:38 openvasmd: Updating

Output from :sudo /usr/bin/openvas-check-setup --v9

Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 7.0.2.
OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
OK: Access rights for the OpenVAS Manager database are correct.
OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
OK: OpenVAS Manager database is at revision 184.
OK: OpenVAS Manager expects database at revision 184.
OK: Database schema is up to date.
OK: OpenVAS Manager database contains information about 45368 NVTs.
OK: At least one user exists.
OK: OpenVAS SCAP database found in /var/lib/openvas/scap-data/scap.db.
OK: OpenVAS CERT database found in /var/lib/openvas/cert-data/cert.db.
OK: xsltproc found.


md omp:WARNING:2018-06-12 02h56.43 utc:37560: Authentication failure for 
'sadmin' from ::
md omp:WARNING:2018-06-12 02h56.46 utc:37567: Authentication failure for 
'admin' from ::
md omp:WARNING:2018-06-12 02h56.47 utc:37583: Authentication failure for 
'admin' from ::
md main:MESSAGE:2018-06-12 16h47.05 utc:68214: OpenVAS Manager version 7.0.2 
(DB revision 184)
md manage: INFO:2018-06-12 16h47.05 utc:68214: Getting users.

Database size:
-rw------- 1 root root 217M Jun  9 01:39 /var/lib/openvas/mgr/tasks.db

I was curious if I should openvas-migrate-to-postgres would be a path to fix 
this issue. Nothing in the log files show any issue, so I'm not really sure 
what openvasmd is stuck "Updating".

Any suggestions?

Daniel Bray
Office: +1 321-525-8081
Mobile: +1 321-213-8360

Openvas-discuss mailing list

Reply via email to