Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scan doesn't work #266

Closed
sergeymeleschenko opened this issue Apr 19, 2024 · 6 comments
Closed

scan doesn't work #266

sergeymeleschenko opened this issue Apr 19, 2024 · 6 comments
Assignees

Comments

@sergeymeleschenko
Copy link

image

when i run scan, the scan doesn't work. run to fast and 0 results, no vulnerabilities. GVM latest, NVT's db current.

@rkoosaar
Copy link

Anything in the logs?

@sergeymeleschenko
Copy link
Author

nothing suspicious, there are no errors. i'm trying to run the oldest version 22.4.30

Anything in the logs?

@immauss
Copy link
Owner

immauss commented Apr 21, 2024

@sergeymeleschenko
Can you give me some more details?
What is the host you are scanning? Did you give the scanner config good credentials? If it is a linux host you are scanning, can you ssh to that host with the credentials you configured from inside the container? And .. If linux host, what is the distribution of the host you are scanning?

@sergeymeleschenko
Copy link
Author

it works with 22.4.30 version. It will be enough for me. I will try to find why the latest version doesn't work for me.

@fredrik812
Copy link

Hi
I'm having the same problem, docker logs says this:

nasl_pread: Failed to close file descriptor for child process (Operation not permitted)

Seems to be this issue:
https://forum.greenbone.net/t/scans-are-working-but-return-0-results-on-gvm-22-4/12952

@immauss
Copy link
Owner

immauss commented May 2, 2024

This is a known issue. For the gory and painful details, you can review #241 and here #242. This is a problem I have been so far unable to isolate but is only in certain distributions. The solution is to allow the container to do ... well ... anything. I spent quite a few weeks trying to isolate and come up with a better solution, so if you find it, please share. For now, the only answer is to use:
--security-opt seccomp=unconfined
in the start command.

-Scott

@immauss immauss closed this as completed May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants