Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start stucked #29

Closed
DevyV opened this issue Mar 21, 2021 · 2 comments
Closed

Start stucked #29

DevyV opened this issue Mar 21, 2021 · 2 comments

Comments

@DevyV
Copy link

DevyV commented Mar 21, 2021

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?

Screenshot from 2021-03-21 15-13-34

@DevyV
Copy link
Author

DevyV commented Mar 21, 2021

I got it: "localhost" not working as I did not use --publish 8080:9392.
I can access it by IP: http:172.17.0.3:9392

@DevyV DevyV closed this as completed Mar 21, 2021
@immauss
Copy link
Owner

immauss commented Mar 22, 2021

Glad you worked it out. Let me know if you run in to any other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants