Open_sock_tcp: time-out

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.
  1. What is the OpenVAS default behaviour regarding TCP socket timeouts?
  2. Should I consider this an error?
  3. Is it related to a specific plugin or does it affect the whole scan?
  4. 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.

Hi @victor.sanchez,

It seems that openvas found the port 111 open, but after that it was closed. Two different process, corresponding to two different plugins, are not being to open the socket. It could be a firewall related issue.
You can get a bit more information from the openvassd man page about the socket timeout and retries.
Regards,
Juan

1 Like

Please note your tool chain is end of life, i would suggest to update ASAP to GVM 20.08.

1 Like