timscotland
commented
1 year ago Try using this and seeing if you can connect
docker run --detach --publish 444:9392 -e PASSWORD="redacted" --volume openvas:/data -e HTTPS=true --name openvas immauss/openvas:latest
Works for me as happy as can be (I use 8443 rather than 444)
Tim
Weston George @.***> 18/12/2022 21:13 >>> I am having some trouble getting OpenVAS up and running. I have tried on 3 different docker servers, one Ubuntu 18.06, one Debian 8, and I built a new Ubuntu 20.02 server just to try it. I have tried with an without the volume as well. I am using the latest version of the container as of December 18th, 2022. It says 'starting' for quite a while, and then goes to 'unhealthy' status when I am viewing it in Portainer. This is what it has done on all three docker servers I have tried. This is my first time installing it, so I may just be doing something wrong. Here is the line I used to run the container after creating the volume: docker run --detach --publish 444:9392 -e PASSWORD="redacted" --volume openvas:/data --name openvas immauss/openvas I tried connecting to the webserver, just to see if maybe it was running anyway, but I got an error that the site couldn't provide a secure connection. Here are the logs (note, if the timestamps look off, I restarted the container to grab the top portion of the log output): `Pulling scapdata from greenbone starting container at: Sun Dec 18 21:08:46 UTC 2022 Looks like this container has already been started once. Just doing a little cleanup instead of the whole fs-setup. Choosing container start method from: Starting gvmd & openvas in a single container !! Wait for redis socket to be created... Testing redis status... Redis not yet ready... �Redis ready. Starting PostgreSQL... waiting for server to start....2022-12-18 21:08:49.716 UTC [26] LOG: redirecting log output to logging collector process 2022-12-18 21:08:49.716 UTC [26] HINT: Future log output will appear in directory "/data/var-log/postgresql". done server started pg exit with 0 . Checking for existing DB Running first start configuration... Checking DB Version Current GVMd database version is 250 NOTICE: relation "vt_severities" already exists, skipping NOTICE: relation "vt_severities" already exists, skipping NOTICE: relation "vt_severities" already exists, skipping NOTICE: relation "vt_severities" already exists, skipping Migrate the database if needed. Updating NVTs and other data This could take a while if you are not using persistent storage for your NVTs or this is the first time pulling to your persistent storage. the time will be mostly dependent on your available bandwidth. We sleep for 2 seconds between sync command to make sure everything closes and it doesnt' look like we are connecting more than once. Pulling NVTs from greenbone
<28>Dec 18 21:08:50 greenbone-nvt-sync: The log facility is not working as expected. All messages will be written to the standard error stream. <29>Dec 18 21:08:50 greenbone-nvt-sync: No Greenbone Security Feed access key found, falling back to Greenbone Community Feed <29>Dec 18 21:08:55 greenbone-nvt-sync: Configured NVT rsync feed: rsync://feed.community.greenbone.net:/community/vulnerability-feed/22.04/vt-data/nasl/ <29>Dec 18 21:08:55 greenbone-nvt-sync: Loading NASL data to /var/lib/openvas/plugins Greenbone community feed server - http://feed.community.greenbone.net/ This service is hosted by Greenbone Networks - http://www.greenbone.net/ All transactions are logged. If you have any questions, please use the Greenbone community portal. See https://community.greenbone.net for details. By using this service you agree to our terms and conditions. Only one sync per time, otherwise the source ip will be temporarily blocked. receiving incremental file list .........(clipped out sync)......... Setup environment Import the key gpg: keybox '/tmp/openvas-gnupg/pubring.kbx' created gpg: /tmp/openvas-gnupg/trustdb.gpg: trustdb created gpg: key 9823FAA60ED1E580: public key "Greenbone Community Feed integrity key" imported gpg: Total number processed: 1 gpg: imported: 1 gpg: inserting ownertrust of 6 Setup key for openvas .. Starting Greenbone Security Assistant... Oops, secure memory pool already initialized gsad main-Message: 20:51:19.124: Starting GSAD version 22.04.0 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Your GVM/openvas/postgresql container is now ready to use! +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ gvmd --version Greenbone Vulnerability Manager 22.4.0~dev1 Manager DB revision 250 Copyright (C) 2009-2021 Greenbone Networks GmbH License: AGPL-3.0-or-later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Image DB date: Thu Oct 13 13:07:27 UTC 2022 � : pg_gvm=v22.4.0 notus_scanner=v22.4.1 �gvmd=v22.4.0 openvas=v22.4.0 openvas_smb=v22.4.0 gvm_libs=v22.4.0 openvas_scanner=v22.4.0 gsa=v22.4.0 �ospd=v21.4.4 ospd_openvas=v22.4.2 python_gvm=v22.9.1 gvm_tools=v22.9.0 ++++++++++++++++ Tailing logs +
++++++++++++++++ ==> /usr/local/var/log/gvm/gvmd.log <== md main:MESSAGE:2022-12-18 20h51.07 utc:554: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md main:WARNING:2022-12-18 20h51.07 utc:554: gvmd: Another process is busy starting up md main:MESSAGE:2022-12-18 20h51.08 utc:558: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md main:WARNING:2022-12-18 20h51.08 utc:558: gvmd: Another process is busy starting up md manage:WARNING:2022-12-18 20h51.08 UTC:561: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd-openvas.sock md main:MESSAGE:2022-12-18 20h51.09 utc:565: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h51.09 utc:565: Getting users. md main:MESSAGE:2022-12-18 20h51.11 utc:571: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h51.11 utc:571: Modifying user password. md manage:WARNING:2022-12-18 20h51.18 UTC:971: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd-openvas.sock ==> /usr/local/var/log/gvm/healthchecks.log <== openvas gvmd gsad HEALTHECHECK FAILED ! These services failed openvas gvmd gsad HEALTHECHECK FAILED ! These services failed openvas gvmd gsad HEALTHECHECK FAILED ! These services failed openvas gvmd gsad ==> /usr/local/var/log/gvm/notus-scanner.log <== 2022-12-18 20:51:19,049 notus-scanner: INFO: (notus.scanner.daemon) Starting notus-scanner version 22.4.1. ==> /usr/local/var/log/gvm/openvas.log <== ==> /usr/local/var/log/gvm/ospd-openvas.log <== OSPD[970] 2022-12-18 20:51:18,747: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.2. OSPD[970] 2022-12-18 20:51:18,758: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker ==> /usr/local/var/log/gvm/redis-server.log <== 88:C 18 Dec 2022 20:46:50.189 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 88:C 18 Dec 2022 20:46:50.189 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=88, just started 88:C 18 Dec 2022 20:46:50.189 # Configuration loaded 88:M 18 Dec 2022 20:46:50.193 # Server initialized 88:M 18 Dec 2022 20:46:50.193 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. ==> /usr/local/var/log/gvm/gvmd.log <== md manage: INFO:2022-12-18 20h51.28 UTC:1002: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting ==> /usr/local/var/log/gvm/ospd-openvas.log <== OSPD[970] 2022-12-18 20:51:28,877: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait... ==> /usr/local/var/log/gvm/gvmd.log <== md manage: INFO:2022-12-18 20h51.38 UTC:1011: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h51.48 UTC:1016: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h51.58 UTC:1019: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md main:MESSAGE:2022-12-18 20h52.02 utc:1035: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h52.02 utc:1035: Getting scanners. md main:MESSAGE:2022-12-18 20h52.05 utc:1041: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h52.05 utc:1041: Verifying scanner. ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues. ==> /usr/local/var/log/gvm/gvmd.log <== md manage: INFO:2022-12-18 20h52.08 UTC:1069: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h52.18 UTC:1072: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h52.28 UTC:1076: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h52.39 UTC:1079: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h52.49 UTC:1083: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting ==> /usr/local/var/log/gvm/openvas.log <== libgvm util:MESSAGE:2022-12-18 20h52.55 utc:1014: Updated NVT cache from version 0 to 202212161019 ==> /usr/local/var/log/gvm/ospd-openvas.log <== OSPD[970] 2022-12-18 20:52:55,837: INFO: (ospd_openvas.daemon) Finished loading VTs. The VT cache has been updated from version 0 to 202212161019. ==> /usr/local/var/log/gvm/gvmd.log <== md manage: INFO:2022-12-18 20h52.59 UTC:1086: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md main:MESSAGE:2022-12-18 20h53.05 utc:1102: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h53.05 utc:1102: Getting scanners. md main:MESSAGE:2022-12-18 20h53.08 utc:1108: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h53.08 utc:1108: Verifying scanner. md manage: INFO:2022-12-18 20h53.09 UTC:1110: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues. ==> /usr/local/var/log/gvm/gvmd.log <== md manage: INFO:2022-12-18 20h53.19 UTC:1139: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h53.29 UTC:1143: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h53.39 UTC:1146: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h53.49 UTC:1150: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h53.59 UTC:1153: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md main:MESSAGE:2022-12-18 20h54.08 utc:1169: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h54.08 utc:1169: Getting scanners. md manage: INFO:2022-12-18 20h54.09 UTC:1171: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md main:MESSAGE:2022-12-18 20h54.10 utc:1178: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h54.10 utc:1178: Verifying scanner. ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues. ==> /usr/local/var/log/gvm/gvmd.log <== md manage: INFO:2022-12-18 20h54.19 UTC:1206: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h54.29 UTC:1210: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md manage: INFO:2022-12-18 20h54.39 UTC:1213: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting md main:MESSAGE:2022-12-18 20h55.11 utc:1239: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h55.11 utc:1239: Getting scanners. md main:MESSAGE:2022-12-18 20h55.13 utc:1245: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h55.13 utc:1245: Verifying scanner. ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues. ==> /usr/local/var/log/gvm/gvmd.log <== md main:MESSAGE:2022-12-18 20h56.14 utc:1306: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h56.14 utc:1306: Getting scanners. md main:MESSAGE:2022-12-18 20h56.16 utc:1312: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h56.16 utc:1312: Verifying scanner. ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues. ==> /usr/local/var/log/gvm/gvmd.log <== md main:MESSAGE:2022-12-18 20h57.17 utc:1373: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h57.17 utc:1373: Getting scanners. md main:MESSAGE:2022-12-18 20h57.19 utc:1379: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h57.19 utc:1379: Verifying scanner. ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues. ==> /usr/local/var/log/gvm/gvmd.log <== md main:MESSAGE:2022-12-18 20h58.20 utc:1446: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h58.20 utc:1446: Getting scanners. md main:MESSAGE:2022-12-18 20h58.22 utc:1456: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h58.22 utc:1456: Verifying scanner. ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues. ==> /usr/local/var/log/gvm/gvmd.log <== md main:MESSAGE:2022-12-18 20h59.23 utc:1518: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h59.23 utc:1518: Getting scanners. md main:MESSAGE:2022-12-18 20h59.25 utc:1524: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 20h59.25 utc:1524: Verifying scanner. ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues. ==> /usr/local/var/log/gvm/gvmd.log <== md main:MESSAGE:2022-12-18 21h00.26 utc:1586: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 21h00.26 utc:1586: Getting scanners. md main:MESSAGE:2022-12-18 21h00.28 utc:1592: Greenbone Vulnerability Manager version 22.4.0dev1 (DB revision 250)
md manage: INFO:2022-12-18 21h00.28 utc:1592: Verifying scanner. ==> /usr/local/var/log/gvm/healthchecks.log <== Healthchecks completed with no issues.` Any help would be greatly appreciated. Thanks! — Reply to this email directly, view it on GitHub ( https://github.com/immauss/openvas/issues/164) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AHCA2AG6ZTB5WQRB3P5FCM3WN547DANCNFSM6AAAAAATCW5UDE) . You are receiving this because you are subscribed to this thread.Message ID: @.***>
nitsewg
immauss
Edit: I'm an idiot. I thought HTTPS was enabled by default, so I was trying to hit it over https. Disregard.
I am having some trouble getting OpenVAS up and running. I have tried on 3 different docker servers, one Ubuntu 18.06, one Debian 8, and I built a new Ubuntu 20.02 server just to try it. I have tried with an without the volume as well. I am using the latest version of the container as of December 18th, 2022. It says 'starting' for quite a while, and then goes to 'unhealthy' status when I am viewing it in Portainer. This is what it has done on all three docker servers I have tried. This is my first time installing it, so I may just be doing something wrong. Here is the command I used to run the container after creating the volume:
docker run --detach --publish 444:9392 -e PASSWORD="redacted" --volume openvas:/data --name openvas immauss/openvasI tried connecting to the webserver, just to see if maybe it was running anyway, but I got an error that the site couldn't provide a secure connection. Here are the logs (note, if the timestamps look off, I restarted the container to grab the top portion of the log output):
Any help would be greatly appreciated. Thanks!