Problem With NVT's after installation

[andreborsatti]

Hi,

GSA Version 21.4.3
Rocky Linux 8.6 (Green Obsidian)
Instalation Date: 2022-07-25

I have problem when install GVM with atomic, using rock 9. I also tried using CentOS 8 and Ubuntu 20.04, all with the same symptom.

After installarion using procedure below:

https://github.com/Atomicorp/gvm

After finish installation, CVE's, OVAL, CERT's, are sync normally, but NVT's not show in GUI and Task is not applyed.

Scan Configs are 0 of 0

In LOG view, /var/log/gvm/gvmd.log below:

md manage:WARNING:2022-07-26 14h32.56 UTC:33577: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd.sock
md manage:WARNING:2022-07-26 14h33.11 UTC:33595: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd.sock
md manage:WARNING:2022-07-26 14h33.26 UTC:33614: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd.sock
md manage:WARNING:2022-07-26 14h33.41 UTC:33632: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd.sock
md manage:WARNING:2022-07-26 14h33.56 UTC:33655: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd.sock

is anyone else having this problem?

[applemodus]

Hello! Yes, the same story. Also with CentOS 8 and Ubuntu 22 LTS.
Will be nice to receive help in this case, please.

[tspedw]

I believe this is probably from mixing atomic packages with some other packages. But I also had the same issue and what I found was that the sock file atomic expects is in the log above but the systemd file was creating a different sock file. After spending a considerable amount of time looking for where atomic was storing the value, I ended up just doing this to get me back up and running:
` ls /var/run/ospd
ospd-openvas.pid ospd-openvas.sock

cd /var/run/ospd

ln -s ospd-openvas.sock ospd.sock

ls -la
total 4
drwxrwxrwx 2 gvm gvm 100 Sep 14 19:35 .
drwxr-xr-x 38 root root 1060 Sep 14 19:23 ..
-rw-r--r-- 1 gvm gvm 6 Sep 14 19:22 ospd-openvas.pid
srwxrwx--- 1 gvm gvm 0 Sep 14 19:22 ospd-openvas.sock
lrwxrwxrwx 1 root root 17 Sep 14 19:35 ospd.sock -> ospd-openvas.sock

sudo -u gvm gvmd --get-scanners
08b69003-5blah-blah-balh OpenVAS /var/run/ospd/ospd.sock 0 OpenVAS Default
6acd0832-blah-blah-blah CVE 0 CVE

sudo -u gvm gvmd --verify-scanner 08b69003-5blah-blah-blah
Scanner version: OpenVAS 21.4.4.`

And now starting scans does not have the immediate fails

[applemodus]

I believe this is probably from mixing atomic packages with some other packages. But I also had the same issue and what I found was that the sock file atomic expects is in the log above but the systemd file was creating a different sock file. After spending a considerable amount of time looking for where atomic was storing the value, I ended up just doing this to get me back up and running: ` ls /var/run/ospd ospd-openvas.pid ospd-openvas.sock

cd /var/run/ospd

ln -s ospd-openvas.sock ospd.sock

ls -la total 4 drwxrwxrwx 2 gvm gvm 100 Sep 14 19:35 . drwxr-xr-x 38 root root 1060 Sep 14 19:23 .. -rw-r--r-- 1 gvm gvm 6 Sep 14 19:22 ospd-openvas.pid srwxrwx--- 1 gvm gvm 0 Sep 14 19:22 ospd-openvas.sock lrwxrwxrwx 1 root root 17 Sep 14 19:35 ospd.sock -> ospd-openvas.sock

sudo -u gvm gvmd --get-scanners 08b69003-5blah-blah-balh OpenVAS /var/run/ospd/ospd.sock 0 OpenVAS Default 6acd0832-blah-blah-blah CVE 0 CVE

sudo -u gvm gvmd --verify-scanner 08b69003-5blah-blah-blah Scanner version: OpenVAS 21.4.4.`

And now starting scans does not have the immediate fails

Hello! Thanks for your reply. I am using Centos 8 and there is no ospd-openvas.sock on my distro.
What distro did you use? I want to try your reply on correct env.

[atomicturtle]

Packages have just been updated to 22.4.1+ are you still running into problems with this?

[applemodus]

Hello!
Sorry for my late answer
@atomicturtle I have migrate to container and have not try once again on RHEL based distros.
Thanks to all!