When a scan has completed, I am finding that the Severity (for some but not all) in the Hosts tab is still marked as 'Log' however if I drill down into the host it is shows that some of the scans at least report other levels, such as high.
My understanding is that the Host tab should show the highest recorde severity for that particular host in order to take a quick glance of overall status.
Is this a bug perhaps or am I missing some config somewhere?
Pretty much vanilla install on CentOS7 (save the sqlite3 faffing)
--
openvas-cli-1.4.5-1990.el7.art.x86_64
openvas-manager-7.0.2-1988.el7.art.x86_64
openvas-scanner-5.1.1-1986.el7.art.x86_64
openvas-9.0.0-1992.el7.art.noarch
openvas-libraries-9.0.1-25.el7.art.x86_64
openvas-smb-1.0.2-1980.el7.art.x86_64
[root@tower mgr]# sqlite3 --version
3.20.0 2017-08-01 13:24:15 9501e22dfeebdcefa783575e47c60b514d7c2e0cad73b2a496c0bc4b680900a8
edit:
Also notice this a fair bit in the md log ... (all clues much appreciated!)
md manage:WARNING:2017-08-21 04h15.15 utc sql_exec_internal: sqlite3_step failed: cannot start a transaction within a transaction
md manage:WARNING:2017-08-21 04h15.15 utc sqlv: sql_exec_internal failed
Severity not updating in Hosts tab.
-
- Atomicorp Staff - Site Admin
- Posts: 8355
- Joined: Wed Dec 31, 1969 8:00 pm
- Location: earth
- Contact:
Re: Severity not updating in Hosts tab.
its probably related to the sqlite 3.8 requirement in 7.0.2. Theres an update for this in the repo now