You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docker run --detach -e PASSWORD="my_password" --volume openvas:/data --name openvas immauss/openvas
It took quite long to update the NVTs and had some strange events logged like:
md manage: INFO:2021-03-21 13h41.38 utc:2391: OSP service has different VT status (version 202103191122) from database (version 202103121134, 65858 VTs). Starting update ...
imd manage: INFO:2021-03-21 13h43.23 utc:2391: Updating VTs in database ... 92 new VTs, 197 changed VTs
md manage:WARNING:2021-03-21 13h43.25 utc:2391: update_nvts_from_vts: SHA-256 hash of the VTs in the database (ccb34ff4b6b4f10a1aa5ded9e23c2772ea70797a2d825908347cabd219fbeb4e) does not match the one from the scanner (16cbd2fbcd8563b8cec70fdc9a3ef21b23908f4fcc8838f428ab82f19608fda5).
md main:MESSAGE:2021-03-21 13h43.25 utc:2391: Rebuilding NVTs because integrity check failed
Hi,
I just pulled the image and started with:
docker run --detach -e PASSWORD="my_password" --volume openvas:/data --name openvas immauss/openvas
It took quite long to update the NVTs and had some strange events logged like:
md manage: INFO:2021-03-21 13h41.38 utc:2391: OSP service has different VT status (version 202103191122) from database (version 202103121134, 65858 VTs). Starting update ...
imd manage: INFO:2021-03-21 13h43.23 utc:2391: Updating VTs in database ... 92 new VTs, 197 changed VTs
md manage:WARNING:2021-03-21 13h43.25 utc:2391: update_nvts_from_vts: SHA-256 hash of the VTs in the database (ccb34ff4b6b4f10a1aa5ded9e23c2772ea70797a2d825908347cabd219fbeb4e) does not match the one from the scanner (16cbd2fbcd8563b8cec70fdc9a3ef21b23908f4fcc8838f428ab82f19608fda5).
md main:MESSAGE:2021-03-21 13h43.25 utc:2391: Rebuilding NVTs because integrity check failed
but after this update seems to be done so far:
md manage: INFO:2021-03-21 13h53.52 utc:2391: Updating VTs in database ... 66027 new VTs, 0 changed VTs
md manage: INFO:2021-03-21 13h53.55 utc:2391: Updating VTs in database ... done (66027 VTs).
md main:MESSAGE:2021-03-21 13h55.27 utc:2391: update_nvt_cache_retry: rebuild successful
Problem is that now it stucked (see screenshot), does nothing (CPU and disk are not in use) and I still cannot connect to it with
http://localhost:9392
Why? What should I do now? Restart?
The text was updated successfully, but these errors were encountered: