Scanner with default OpenVas won't run, cant access /opt/gvm/var/run/ospd.sock

[nadavbuc]

Describe the bug
When trying to launch a scanner - it returns an error, in the logs you can see that it didn't had access to the ospd.sock

To Reproduce
Steps to reproduce the behavior:
Try running a scan

Expected behavior
Report is generated

Actual Behaviour
Report returns an error

Additional context
Fixeable by changing the ospd run line - and adding -m flag:
ospd-openvas --log-file /usr/local/var/log/gvm/ospd-openvas.log --unix-socket /var/run/ospd/ospd.sock --log-level INFO -m 0o777
And also

mkdir -p /opt/gvm/var/run/
ln -s /var/run/ospd/ospd.sock /opt/gvm/var/run/ospd.sock

I added these to start.sh file locally and everything worked like a charm

[pixelsquared]

Are the directory and file link required for it to work for you?

[nadavbuc]

Yes, or i can modify the scanner to use the original sock path, but its manual after the container is up

[pixelsquared]

I just don't understand why your setup is looking for the socket at /opt/gvm/var/run/ospd.sock

[austinsonger]

I'm converting to a discussion. This doesn't seem to be an issue for the majority of users.

[nadavbuc]

Sorry for very late response
Im trying it now from scratch on a new server
I'll let you know if it reoccours

[austinsonger]

Any update?

[Masaya-A]

I think this should be fixed with #143

[austinsonger]

If you can please upvote or downvote on feature requests, or you can even submit your own feature request.

[nadavbuc]

It works for me 🔥🔥🔥

…

Sent from my iPhone

On 23 Apr 2021, at 2:48, Masaya-A ***@***.***> wrote:  I think this should be fixed with #143 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[austinsonger]

If you can please upvote or downvote on feature requests, or you can even submit your own feature request.