search

yu210148 / gvm_install

A script to install GVM 20 or 21 on Ubuntu 20.04 or Debian 10.
GNU General Public License v3.0
142 stars 71 forks source link

Could not connect to Scanner. Interrupting scan because GVM is exiting. #53

Open lateralraises opened 3 years ago

lateralraises commented 3 years ago

I used the script to install the GVM21 version on a Debian 10 OS. I followed the instruction to wait for 24 hours after the installation to finish the update. I also restarted the VM and apply the Port Scanner changes on the Scan Config based on the other issues encountered. When I did a test scan I encounter the errors: Could not connect to Scanner. Interrupting scan because GVM is exiting.

Screen Shot 2021-08-05 at 9 25 43 AM

This is also the result when I installed on a new Ubuntu 20.04 OS. I also have a previous installation using the script on an Ubuntu 20.04 OS, and it works fine except that the References are not included on the .csv report. This is installed in a VirtualBox machine. The other two that encountering this error are Debian 10 and Ubuntu 20.04 also that installed in a hypervisor. But that shouldn't affect right?

This is what I found on the gvmd.log. 

md manage:WARNING:2021-08-05 02h14.17 UTC:1203: Could not connect to Scanner at /var/run/ospd/ospd.sock
md manage:WARNING:2021-08-05 02h14.17 UTC:1203: OSP start_scan da76cda6-494c-4cff-bac4-67617f30220a: Could not connect to Scanner
event task:MESSAGE:2021-08-05 02h14.17 UTC:1203: Status of task test scan (43e1b716-a4f4-4fd1-ae80-11b37efe3d6a) has changed to Done
event task:MESSAGE:2021-08-05 02h14.17 UTC:1203: Status of task test scan (43e1b716-a4f4-4fd1-ae80-11b37efe3d6a) has changed to Interrupted

What could be the solution for this?

CTPAyCCC commented 3 years ago

Hi I subscribe to this question.

5. To check the status of each command above go to https://localhost from the server, login with the user credentials (likely gvmadmin and StrongPass), go to Administration, Feed Status.

Did not help

xxedgexx commented 2 years ago

I used the script to install the GVM21 version on a Debian 10 OS. I followed the instruction to wait for 24 hours after the installation to finish the update. I also restarted the VM and apply the Port Scanner changes on the Scan Config based on the other issues encountered. When I did a test scan I encounter the errors: Could not connect to Scanner. Interrupting scan because GVM is exiting. Screen Shot 2021-08-05 at 9 25 43 AM This is also the result when I installed on a new Ubuntu 20.04 OS. I also have a previous installation using the script on an Ubuntu 20.04 OS, and it works fine except that the References are not included on the .csv report. This is installed in a VirtualBox machine. The other two that encountering this error are Debian 10 and Ubuntu 20.04 also that installed in a hypervisor. But that shouldn't affect right?

This is what I found on the gvmd.log.

md manage:WARNING:2021-08-05 02h14.17 UTC:1203: Could not connect to Scanner at /var/run/ospd/ospd.sock
md manage:WARNING:2021-08-05 02h14.17 UTC:1203: OSP start_scan da76cda6-494c-4cff-bac4-67617f30220a: Could not connect to Scanner
event task:MESSAGE:2021-08-05 02h14.17 UTC:1203: Status of task test scan (43e1b716-a4f4-4fd1-ae80-11b37efe3d6a) has changed to Done
event task:MESSAGE:2021-08-05 02h14.17 UTC:1203: Status of task test scan (43e1b716-a4f4-4fd1-ae80-11b37efe3d6a) has changed to Interrupted

What could be the solution for this?

Having this same issue right now.

gvm-tools-1.4.1-9393.el8.art.noarch gvm-libs-devel-21.4.3-23769.el8.art.x86_64 gvmd-21.4.4-24047.el8.art.x86_64 gvm-libs-21.4.3-23769.el8.art.x86_64 gvm-21.4.0-18459.el8.art.noarch OSPd-openvas-21.4.3-24064.el8.art.x86_64 openvas-scanner-21.4.3-24048.el8.art.x86_64 openvas-smb-21.4.0-24053.el8.art.x86_64

yu210148 commented 2 years ago

Hi there,

Humm, not sure what would be causing this. I seem to remember that /var/run/ospd/ospd.sock has to do with the redis server although I may be wrong about that. Does that file exist for you? If so, is it readable/writable for the 'gvm' user?

If anyone else seeing this has any ideas please chime in. :)

kev.

MandersonMuahahaha commented 2 years ago

I found that gvmd was looking for the socket at /var/run/ospd/ospd.sock, but ospd-openvas is creating the socket at /var/run/ospd/ospd-openvas.sock. I created the symlink /var/run/ospd/ospd.sock -> /var/run/ospd/ospd-openvas.sock and restarted gvmd - seems to be working fine. I am running Oracle Enterprise Linux 8.5

yu210148 commented 2 years ago

Thanks, I'll see about putting something in there to create that symlink when I get a chance. It shouldn't hurt if it's not needed on other systems I wouldn't think.

Kev.

On Wed, Feb 16, 2022, 10:33 PM Anderson Manly @.***> wrote:

I found that gvmd was looking for the socket at /var/run/ospd/ospd.sock, but ospd-openvas is creating the socket at /var/run/ospd/ospd-openvas.sock. I created the symlink /var/run/ospd/ospd.sock -> /var/run/ospd/ospd-openvas.sock and restarted gvmd - seems to be working fine. I am running Oracle Enterprise Linux 8.5

— Reply to this email directly, view it on GitHub https://github.com/yu210148/gvm_install/issues/53#issuecomment-1042539383, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKFY4LFZ6H4WFJCAW57HPTU3RUBPANCNFSM5BSPKS6A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

marchwicki commented 2 years ago

I was getting, "Could not connect to Scanner at /opt/gvm/run/ospd/ospd-openvas.sock" in the logs on a fresh install of 20.04. I did a "ln -s /opt/gvm/var/run/ospd.sock /opt/gvm/run/ospd/ospd-openvas.sock" and it started working.

yu210148 commented 2 years ago

Cool, thanks for the info. I'll put it in next time I've got the code open. 🙂

Kev.

On Mon, Feb 28, 2022, 12:32 PM marchwicki @.***> wrote:

I was getting, "Could not connect to Scanner at /opt/gvm/run/ospd/ospd-openvas.sock" in the logs on a fresh install of 20.04. I did a "ln -s /opt/gvm/var/run/ospd.sock /opt/gvm/run/ospd/ospd-openvas.sock" and it started working.

— Reply to this email directly, view it on GitHub https://github.com/yu210148/gvm_install/issues/53#issuecomment-1054495439, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKFY4PLMVLWIDLO6QKF5JTU5OWRFANCNFSM5BSPKS6A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

MarcSN311 commented 2 years ago

Had the same issue on ubuntu 20.04. I had to create the directory /opt/gvm/run/ospd/ first, then create the symlink. Seems to work now.