Why I can't access web Openvas

Community Containers
1

Hello everyone, I can’t access web here is log

| md manage:WARNING:2023-11-08 00h31.47 UTC:70: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h31.57 UTC:71: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h32.07 UTC:72: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h32.17 UTC:73: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h32.27 UTC:74: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h32.37 UTC:75: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h32.47 UTC:76: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h32.57 UTC:77: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h33.07 UTC:78: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h33.17 UTC:79: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 00h33.27 UTC:80: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 00h33.37 UTC:81: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 00h33.47 UTC:82: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 00h33.57 UTC:83: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 00h34.07 UTC:84: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 00h34.17 UTC:85: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 00h34.28 UTC:86: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 00h34.38 UTC:87: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 00h34.48 UTC:88: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting

Please help me I just
docker-compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition stop ospd-openvas
docker-compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition run --rm ospd-openvas greenbone-nvt-sync
docker-compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition up -d
this command after Openvas not working
Best regards.

2

Hi,

first of all please take a look at Troubleshooting - Greenbone Community Documentation

Second where did you get the docker-compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition run --rm ospd-openvas greenbone-nvt-sync command from? It’s not mentioned in our docs. At least not anymore. Please always follow the latest content of our docs for troubleshooting and not just paste various commands found somewhere in the internet.

1 Like
3

still doesn’t work sir.
I try to run this command again but it’s doesn’t work

docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition pull notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects

docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition up -d notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects

When I run 2 of this command it’s not help
Here is Log after I run 2 how this command

greenbone-community-edition-ospd-openvas-1         | OSPD[7] 2023-11-08 06:56:10,945: ERROR: (ospd_openvas.daemon) Updating VTs failed.
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h56.12 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2012.xml
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h56.18 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2023.xml
greenbone-community-edition-mqtt-broker-1          | 1699426597: New connection from 172.18.0.8:39666 on port 1883.
greenbone-community-edition-mqtt-broker-1          | 1699426597: New client connected from 172.18.0.8:39666 as f341e921-c5c7-4d5a-83db-4bce35700597 (p5, c1, k0).
greenbone-community-edition-mqtt-broker-1          | 1699426597: Client f341e921-c5c7-4d5a-83db-4bce35700597 closed its connection.
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h56.37 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2015.xml
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h56.43 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2020.xml
greenbone-community-edition-ospd-openvas-1         | OSPD[7] 2023-11-08 06:56:46,594: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait...
greenbone-community-edition-ospd-openvas-1         | OSPD[7] 2023-11-08 06:56:51,549: ERROR: (ospd_openvas.openvas) OpenVAS Scanner failed to load VTs. Command '['openvas', '--update-vt-info']' returned non-zero exit status 1.
greenbone-community-edition-ospd-openvas-1         | OSPD[7] 2023-11-08 06:56:51,549: ERROR: (ospd_openvas.daemon) Updating VTs failed.
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h57.06 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2002.xml
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h57.10 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2016.xml
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h57.18 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2009.xml
greenbone-community-edition-ospd-openvas-1         | OSPD[7] 2023-11-08 06:57:23,081: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait...
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h57.26 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2003.xml
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 06h57.27 UTC:1516: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2022.xml
greenbone-community-edition-ospd-openvas-1         | OSPD[7] 2023-11-08 06:57:28,123: ERROR: (ospd_openvas.openvas) OpenVAS Scanner failed to load VTs. Command '['openvas', '--update-vt-info']' returned non-zero exit status 1.
greenbone-community-edition-ospd-openvas-1         | OSPD[7] 2023-11-08 06:57:28,123: ERROR: (ospd_openvas.daemon) Updating VTs failed.
4

Yes but we are one step closer to the solution and now found the real problem. The scanner couldn’t load the vulnerability tests. Most likely you messed up the file permissions in some kind. Please run

docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition stop
docker volume rm greenbone-community-edition_openvas_data_vol greenbone-community-edition_ospd_openvas_socket_vol greenbone-community-edition_redis_socket_vol greenbone-community-edition_vt_data_vol greenbone-community-edition_notus_data_vol greenbone-community-edition_gvmd_socket_vol
docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition up -d

which deletes (most of) the used docker volumes and re-creates them. That should fix possible file permissions issues.

2 Likes
5

It’s still not work sir.
Here is log when I follow your command

greenbone-community-edition-gvmd-1                 | md manage:MESSAGE:2023-11-08 07h13.56 utc:57: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.111091:1 has changed from 'Report NVT debug logs' to 'Report VT debug logs'.
greenbone-community-edition-pg-gvm-1               | 2023-11-08 07:13:48.635 UTC [100] LOG:  listening on IPv4 address "0.0.0.0", port 5432
greenbone-community-edition-pg-gvm-1               | 2023-11-08 07:13:48.635 UTC [100] LOG:  listening on IPv6 address "::", port 5432
greenbone-community-edition-pg-gvm-1               | 2023-11-08 07:13:48.639 UTC [100] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
greenbone-community-edition-pg-gvm-1               | 2023-11-08 07:13:48.647 UTC [101] LOG:  database system was shut down at 2023-11-08 07:13:48 UTC
greenbone-community-edition-pg-gvm-1               | 2023-11-08 07:13:48.659 UTC [100] LOG:  database system is ready to accept connections
greenbone-community-edition-pg-gvm-1               | 2023-11-08 07:13:52.233 UTC [111] gvmd@gvmd WARNING:  there is already a transaction in progress
greenbone-community-edition-pg-gvm-1               | 2023-11-08 07:13:52.611 UTC [111] gvmd@gvmd WARNING:  there is no transaction in progress
greenbone-community-edition-gvmd-1                 | md manage:MESSAGE:2023-11-08 07h13.57 utc:57: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
greenbone-community-edition-gvmd-1                 | md   main:MESSAGE:2023-11-08 07h13.57 utc:59:    Greenbone Vulnerability Manager version 23.0.1 (DB revision 255)
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 07h13.57 utc:59:    Getting users.
greenbone-community-edition-gvmd-1                 | md   main:MESSAGE:2023-11-08 07h13.58 utc:62:    Greenbone Vulnerability Manager version 23.0.1 (DB revision 255)
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 07h13.58 utc:62:    Modifying setting.
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 07h14.50 UTC:87: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 07h15.00 UTC:88: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 07h15.10 UTC:89: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 07h15.20 UTC:90: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 07h15.30 UTC:91: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 07h15.40 UTC:92: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock UTC:102: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 07h17.31 UTC:103: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:WARNING:2023-11-08 07h17.41 UTC:104: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 07h17.51 UTC:105: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 07h18.01 UTC:106: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 07h18.11 UTC:107: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 07h18.21 UTC:108: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 07h18.31 UTC:109: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
greenbone-community-edition-gvmd-1                 | md manage:   INFO:2023-11-08 07h18.41 UTC:110: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
6

I just found the error is Database is shutdown

 starting PostgreSQL 13.11 (Debian 13.11-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:49:42.775 UTC [23] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:49:42.808 UTC [24] LOG:  database system was interrupted; last known up at 2023-11-07 08:45:08 UTC
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:49:47.969 UTC [24] LOG:  database system was not properly shut down; automatic recovery in progress
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:49:47.970 UTC [24] LOG:  redo starts at 4/9CE84F50
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:49:47.973 UTC [24] LOG:  invalid record length at 4/9CECC4D8: wanted 24, got 0
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:49:47.973 UTC [24] LOG:  redo done at 4/9CECC4B0
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:49:47.990 UTC [23] LOG:  database system is ready to accept connections
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:50:18.770 UTC [100] LOG:  starting PostgreSQL 13.11 (Debian 13.11-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:50:18.772 UTC [100] LOG:  listening on IPv4 address "0.0.0.0", port 5432
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:50:18.772 UTC [100] LOG:  listening on IPv6 address "::", port 5432
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:50:18.777 UTC [100] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:50:18.791 UTC [101] LOG:  database system was shut down at 2023-11-07 08:50:18 UTC
greenbone-community-edition-pg-gvm-1               | 2023-11-07 08:50:18.804 UTC [100] LOG:  database system is ready to accept connections
greenbone-community-edition-pg-gvm-1               | 2023-11-07 10:04:04.903 UTC [102] LOG:  checkpoints are occurring too frequently (29 seconds apart)
greenbone-community-edition-pg-gvm-1               | 2023-11-07 10:04:04.903 UTC [102] HINT:  Consider increasing the configuration parameter "max_wal_size".
greenbone-community-edition-pg-gvm-1               | 2023-11-08 02:48:15.619 UTC [8744] gvmd@gvmd WARNING:  there is already a transaction in progress
greenbone-community-edition-pg-gvm-1               | 2023-11-08 02:48:15.976 UTC [8744] gvmd@gvmd WARNING:  there is no transaction in progress

so how can I do it ?
Best regards.

7

It’s still scan but I can’t access Web

greenbone-community-edition-gvmd-1                 | event task:MESSAGE:2023-11-08 15h30.11 +07:540: Task SMC  (aeac3280-e634-452f-8b9b-31aeabfdbd29) could not be resumed by admin
greenbone-community-edition-gvmd-1                 | event task:MESSAGE:2023-11-08 15h30.11 +07:540: Status of task SMC  (aeac3280-e634-452f-8b9b-31aeabfdbd29) has changed to Requested
greenbone-community-edition-gvmd-1                 | event task:MESSAGE:2023-11-08 15h30.11 +07:540: Task SMC  (aeac3280-e634-452f-8b9b-31aeabfdbd29) has been requested to start by admin
greenbone-community-edition-gvmd-1                 | event task:MESSAGE:2023-11-08 15h30.27 +07:542: Status of task SMC  (aeac3280-e634-452f-8b9b-31aeabfdbd29) has changed to Queued
greenbone-community-edition-gvmd-1                 | event task:MESSAGE:2023-11-08 15h30.32 +07:542: Status of task SMC  (aeac3280-e634-452f-8b9b-31aeabfdbd29) has changed to Running
8

But you can start tasks?

9

Yes sir.
Task still running follow schedule I set but Web can’t access.