GVM versions
gsa: 8.0.1
gvm: 8.0.1
openvas-scanner: 6.0.1
gvm-libs: 10.0.1
Environment
Operating system: Arch Linux
Kernel: 5.2.14-arch2-1-ARCH
Installation method / source: pacman
################################################################################
Dear all,
My questions are related to the last 2 lines of the openvassd.log I recently found in one of my machines:
sd main:MESSAGE:2020-12-31 07h11.05 utc:733209: Starts a new scan. Target(s) : <IP>, with max_hosts = 30 and max_checks = 10
sd main:MESSAGE:2020-12-31 07h11.06 utc:737596: Testing <IP> (Vhosts: ********, *******) [737596]
lib misc:MESSAGE:2020-12-31 07h11.26 utc:736745: open_sock_tcp: <IP>:111 time-out.
lib misc:MESSAGE:2020-12-31 07h13.34 utc:743568: open_sock_tcp: <IP>:111 time-out.
- What is the OpenVAS default behaviour regarding TCP socket timeouts?
- Should I consider this an error?
- Is it related to a specific plugin or does it affect the whole scan?
- Is OpenVAS capable of recovering from this situation (retries, etc.)?
Thank you in advance for your answers.
I wish you all a happy and resilient 2021!
Regards.