2023 Still! >> Failed to find config ‘daba56c8–73ec-11df-a475–002264764cea‘

reallytired · January 26, 2023, 1:31pm

Kali Linux Version:

┌──(root㉿kali)-[~]
└─# cat /etc/os-release 
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
VERSION="2022.4"
VERSION_ID="2022.4"

Installation Steps:

┌──(root💀kali)-[/home/kali/]
└─#  apt update && apt upgrade -y

┌──(root💀kali)-[/home/kali/]
└─# apt install gvm -y

┌──(root💀kali)-[/home/kali/]
└─# cd /usr/bin

┌──(root💀kali)-[/usr/bin]
└─# gvm-setup

┌──(root💀kali)-[/usr/bin]
└─# gvm-check-setup

┌──(root💀kali)-[/usr/bin]
└─# gvm-feed-update -h

┌──(root💀kali)-[/usr/bin]
└─# greenbone-feed-sync --type GVMD_DATA  
┌──(root💀kali)-[/usr/bin]
└─#greenbone-feed-sync --type SCAP  
┌──(root💀kali)-[/usr/bin]
└─#greenbone-feed-sync --type CERT

┌──(root💀kali)-[/usr/bin]
└─# gvm-start

I waited to finish also in the web GUI (feed status: Current)

I added one target and then came to tasks to create a task and I have got:
Failed to find config ‘daba56c8–73ec-11df-a475–002264764cea’

Logs:

┌──(root㉿kali)-[/var/log/gvm]
└─# tail -f gvmd.log 
md manage:WARNING:2023-01-26 11h30.54 UTC:4469: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock
md manage:WARNING:2023-01-26 11h31.04 UTC:4538: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock

After 3 hours of research, nothing is still useful. I found this but it did not help.

┌──(root㉿kali)-[~]
└─# sudo runuser -u _gvm -- gvmd --get-users --verbose                                                                             
┌──(root㉿kali)-[~]
└─# sudo runuser -u _gvm -- gvmd --get-scanners

┌──(root㉿kali)-[~]
└─# sudo runuser -u _gvm -- gvmd --modify-scanner 08b69003-5fc2-4037-a479-93b440211c73 --value b42e5c80-5d24-40f6-822d-a98c3a956a6f
Scanner modified.

I saw this: https://github.com/greenbone/gvmd/blob/main/INSTALL.md

gvmd --modify-scanner=08b69003-5fc2-4037-a479-93b440211c73 --scanner-host=<install-prefix>/var/run/ospd/ospd-openvas.sock

but I don’t understand what is
I am really desperate…

bricks · January 26, 2023, 2:22pm

Hi,

I’ve written a longer text for troubleshooting this issue with our source build which can be found at https://greenbone.github.io/docs/latest/22.4/source-build/troubleshooting.html#failed-to-find-config
For Kali you need to replace sudo -u gvm with sudo -u _gvm.

reallytired · January 26, 2023, 3:29pm

┌──(root㉿kali)-[~]
└─# find /var/lib/gvm/data-objects/ -name "*daba56c8-73ec-11df-a475-002264764cea*.xml"                                          
/var/lib/gvm/data-objects/gvmd/22.04/scan-configs/full-and-fast-daba56c8-73ec-11df-a475-002264764cea.xml
                                                                                                                                                             
┌──(root㉿kali)-[~]
└─# sudo -u _gvm greenbone-feed-sync --type GVMD_DATA                                                                             
...
receiving incremental file list
timestamp
             13 100%   12.70kB/s    0:00:00 (xfr#1, to-chk=0/1)
sent 71 bytes  received 111 bytes  121.33 bytes/sec
total size is 13  speedup is 0.07
                                                                                                                                                             
┌──(root㉿kali)-[~]
└─# sudo -u _gvm greenbone-nvt-sync                                                                                                
...
sent 1,797 bytes  received 2,587,232 bytes  739,722.57 bytes/sec
total size is 374,642,186  speedup is 144.70
sent 44 bytes  received 15,502 bytes  10,364.00 bytes/sec
total size is 238,314,524  speedup is 15,329.64
...
total size is 986  speedup is 10.06
/var/lib/openvas/feed-update.lock     
    
┌──(root㉿kali)-[~]
└─# sudo runuser -u _gvm -- gvmd --get-users --verbose                                                                             
admin b42e5c80-5d24-40f6-822d-a98c3a956a6f
                                                                                                                                                    
┌──(root㉿kali)-[~]
└─# gvmd --modify-setting 78eceaec-3385-11ea-b237-28d24461215b --value b42e5c80-5d24-40f6-822d-a98c3a956a6f

Still getting the same error when I want to add a task.
Also the log:

┌──(root㉿kali)-[/var/log/gvm]
└─# tail -f gvmd.log                                                                                                              
md manage:   INFO:2023-01-26 15h24.02 UTC:1407: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:WARNING:2023-01-26 15h24.13 UTC:1457: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock
md manage:WARNING:2023-01-26 15h24.23 UTC:1708: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock

┌──(root㉿kali)-[~]
└─# tail -f /var/log/gvm/ospd-openvas.log 
OSPD[2726] 2023-01-26 15:29:19,329: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.4.
OSPD[2726] 2023-01-26 15:29:19,353: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker
OSPD[2726] 2023-01-26 15:29:29,468: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait...
OSPD[2726] 2023-01-26 15:29:30,040: WARNING: (gnupg) potential problem: ERROR: add_keyblock_resource 33587201
OSPD[2726] 2023-01-26 15:29:30,040: WARNING: (gnupg) potential problem: ERROR: keydb_search 33554445
OSPD[2726] 2023-01-26 15:29:30,041: WARNING: (gnupg) potential problem: ERROR: keydb_search 33554445
OSPD[2726] 2023-01-26 15:29:30,041: WARNING: (gnupg) gpg returned a non-zero error code: 2
OSPD[2726] 2023-01-26 15:29:30,045: INFO: (ospd.main) Shutting-down server ...
OSPD[2918] 2023-01-26 15:30:30,973: INFO: (ospd.main) Starting OSPd OpenVAS  version 22.4.4.

bricks · January 26, 2023, 3:53pm

reallytired:

OSPD[2726] 2023-01-26 15:29:30,040: WARNING: (gnupg) potential problem: ERROR: add_keyblock_resource 33587201
OSPD[2726] 2023-01-26 15:29:30,040: WARNING: (gnupg) potential problem: ERROR: keydb_search 33554445
OSPD[2726] 2023-01-26 15:29:30,041: WARNING: (gnupg) potential problem: ERROR: keydb_search 33554445
OSPD[2726] 2023-01-26 15:29:30,041: WARNING: (gnupg) gpg returned a non-zero error code: 2

Never seen this error before. Seems to be an issue with the VTs signature verification via GPG. ospd-openvas fails to start because of the GPG issue, gvmd therefore can’t load the VT meta information from ospd-openvas and as a result the scan configs can’t be loaded because they require the VT meta information.

Could you try disabling the verification by running

echo "disable_notus_hashsum_verification = True" >> /etc/gvm/ospd-openvas.conf

(probably as _gvm user) and restart ospd-openvas (sudo systemctl restart ospd-openvas).

reallytired · January 26, 2023, 3:56pm

┌──(root㉿kali)-[/usr/bin]
└─# echo "disable_notus_hashsum_verification = True" >> /etc/gvm/ospd-openvas.conf

                                                                                                                                                             
┌──(root㉿kali)-[/usr/bin]
└─# sudo systemctl restart ospd-openvas
                                                                                                                                                             
┌──(root㉿kali)-[/usr/bin]
└─# tail -f /var/log/gvm/gvmd.log                                                                          
md manage:WARNING:2023-01-26 15h53.58 UTC:47412: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock
md manage:WARNING:2023-01-26 15h54.08 UTC:47514: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock
md manage:WARNING:2023-01-26 15h54.18 UTC:47617: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock
md manage:WARNING:2023-01-26 15h54.28 UTC:47720: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock
md manage:WARNING:2023-01-26 15h54.38 UTC:47823: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock
md manage:WARNING:2023-01-26 15h54.48 UTC:47919: osp_scanner_feed_version: failed to connect to /run/ospd/ospd.sock
md manage:   INFO:2023-01-26 15h55.03 UTC:48188: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
event task:MESSAGE:2023-01-26 15h55.09 UTC:48283: Status of task  (7a45efb7-7dc3-4657-96ce-921d56483fc7) has changed to New
md manage:   INFO:2023-01-26 15h55.19 UTC:48403: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
event task:MESSAGE:2023-01-26 15h55.27 UTC:48625: Status of task  (3e9b77df-a0bc-4cb7-a5fe-3d6c05c7710b) has changed to New
^C
                                                                                                                                                             
┌──(root㉿kali)-[/usr/bin]
└─# tail -f /var/log/gvm/ospd-openvas.log                                                                  
OSPD[47972] 2023-01-26 15:54:50,534: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:55:00,544: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:55:00,582: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait...
OSPD[47972] 2023-01-26 15:55:00,641: INFO: (ospd_openvas.notus) hashsum verification is disabled
OSPD[47972] 2023-01-26 15:55:10,555: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:55:20,563: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:55:30,571: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:55:40,576: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:55:50,583: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:56:00,591: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
^C

bricks · January 26, 2023, 4:06pm

OK I guess notus-scanner and the mosquitto MQTT broker are not running. Could you run sudo systemctl start notus-scanner?

reallytired · January 26, 2023, 4:08pm

┌──(root㉿kali)-[~]
└─# sudo systemctl start notus-scanner
                                                                                                                                                             
┌──(root㉿kali)-[~]
└─# tail -f /var/log/gvm/gvmd.log        
md manage:   INFO:2023-01-26 15h57.54 UTC:2740: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h58.04 UTC:2849: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h58.14 UTC:2956: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h58.24 UTC:3073: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h58.34 UTC:3176: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h58.45 UTC:3282: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h58.55 UTC:3385: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h59.05 UTC:3489: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h59.24 UTC:3701: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-01-26 15h59.39 UTC:3751: OSP service has different VT status (version 202301261013) from database (version (null), 0 VTs). Starting update ...
^[[A^[[A^C
                                                                                                                                                             
┌──(root㉿kali)-[~]
└─# tail -f /var/log/gvm/ospd-openvas.log
OSPD[47972] 2023-01-26 15:56:30,603: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:56:40,609: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:56:50,619: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:57:00,629: WARNING: (ospd_openvas.messaging.mqtt) Could not connect to MQTT broker, error was: [Errno 111] Connection refused. Trying again in 10s.
OSPD[47972] 2023-01-26 15:57:10,078: INFO: (ospd.main) Shutting-down server ...
OSPD[1289] 2023-01-26 15:56:38,483: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.4.
OSPD[1289] 2023-01-26 15:56:38,505: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker
OSPD[1289] 2023-01-26 15:56:48,633: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait...
OSPD[1289] 2023-01-26 15:56:48,675: INFO: (ospd_openvas.notus) hashsum verification is disabled
OSPD[1289] 2023-01-26 15:59:19,209: INFO: (ospd_openvas.daemon) VTs were up to date. Feed version is 202301261013.

bricks · January 26, 2023, 4:14pm

Nice! After gvmd has loaded the VT meta information you should get the scan configs too.

reallytired · January 26, 2023, 4:21pm

Thank you so much, it was a painful day.

Summary for others>

┌──(root㉿kali)-[~]
└─# find /var/lib/gvm/data-objects/ -name "*daba56c8-73ec-11df-a475-002264764cea*.xml"                                          
                                                                                                                                                             
┌──(root㉿kali)-[~]
└─# sudo -u _gvm greenbone-feed-sync --type GVMD_DATA                                                                             
                                                                                                                                                         
┌──(root㉿kali)-[~]
└─# sudo -u _gvm greenbone-nvt-sync                                                                                                
    
┌──(root㉿kali)-[~]
└─# sudo runuser -u _gvm -- gvmd --get-users --verbose                                                                             
admin b42e5c80-5d24-40f6-822d-a98c3a956a6f
                                                                                                                                                    
┌──(root㉿kali)-[~]
└─# gvmd --modify-setting 78eceaec-3385-11ea-b237-28d24461215b --value b42e5c80-5d24-40f6-822d-a98c3a956a6f

┌──(root㉿kali)-[~]
└─# echo "disable_notus_hashsum_verification = True" >> /etc/gvm/ospd-openvas.conf

┌──(root㉿kali)-[~]
└─# sudo systemctl restart ospd-openvas

┌──(root㉿kali)-[~]
└─#  sudo systemctl start notus-scanner

I AM ABLE TO CREATE TASKS!!

bricks · January 26, 2023, 4:28pm

Glad I could help. Also your issue resulted in a fix for the ospd-openvas.service (https://github.com/greenbone/ospd-openvas/pull/843). That’s always a nice outcome.

I know that the setup of our software can be very difficult especially on Kali where we don’t have influence on the environment and its changes. I still try my best to help to address such issues and get things fixed.

reallytired · January 26, 2023, 4:30pm

Thank you very much for your quick answers. It was a really bad day but it is important it is solved because of your help. I understand it is the community version