Failed to connect.run/ospd/ospd.sock

Hello.
I have problems with feed updating process. I waited a long time, but “scan configs” is empty(( After that I decided to check logs by sudo tail -f /var/log/gvm/gvmd.log command and so messages like “failed to connect to /run/ospd/ospd.sock”.
Also I launched ls /var /run/ospd and it’s not found(
I used Oracle VM and Kali 2022.4
Do somebody know the solution of this issue?

Did you take a look at the ospd-openvas.log file to find out why it doesn’t start?

1 Like

This is Log of the ospd-openvas.log file:

OSPD[14717] 2023-01-30 13:16:18,171: INFO: (ospd.main) Starting OSPd OpenVAS version 22.4.4.
OSPD[14717] 2023-01-30 13:16:18,174: INFO: (ospd_openvas.messaging.mqtt) Successfully connected to MQTT broker
OSPD[14717] 2023-01-30 13:16:28,206: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested|queued] until VTs are loaded. This may take a few minutes, please wait…
OSPD[14717] 2023-01-30 13:16:28,260: WARNING: (gnupg) potential problem: ERROR: add_keyblock_resource 33587201
OSPD[14717] 2023-01-30 13:16:28,260: WARNING: (gnupg) potential problem: ERROR: keydb_search 33554445
OSPD[14717] 2023-01-30 13:16:28,260: WARNING: (gnupg) potential problem: ERROR: keydb_search 33554445
OSPD[14717] 2023-01-30 13:16:28,260: WARNING: (gnupg) gpg returned a non-zero error code: 2
OSPD[14717] 2023-01-30 13:16:28,264: INFO: (ospd.main) Shutting-down server …

What does it mean?

There have been some pointers recently in various threads:

1 Like

Thank you. First topic is the solution.

1 Like

Please do note that disabling the signature checks is no permanent solution and it is still suggested / required that a user of Kali is opening a new issue at https://bugs.kali.org (according to some previous comments) so that the Kali team can look into this potential problem: ERROR messages.

Yes ok. You are right.