So basically, your slave does not start any job and the master hangs on the
Request status.
I don't think it's a credential issue but rather firewalling?
I use slaves as such:
· Openvasmd listens on 0.0.0.0:9390 with iptables allowing access to
that port using TCP from the master
·
Hi,
Thank you very much for all the tips and guides.
I managed to go through the procedure advised by Christian at
http://plugins.openvas.org/ova_503.txt .
I had to modify the paths to the certificates slightly as they seem be located
directly under /var/lib instead of /usr/local/var/lib.
Strange, I figured the admin user starting the job is not relevant.
You may or may not start a job.
The job is pushed and running on the slave using the account which is
configured for that slave, there is only 1. I don't see any connection to the
actual user starting the job.
I am the only
Hi,
On 11/06/2016 07:59 AM, kalin m wrote:
> openvas-check-setup 2.3.2
please always use the latest available version of that
openvas-check-setup. The current version 2.3.3 is available here:
https://svn.wald.intevation.org/svn/openvas/trunk/tools/openvas-check-setup
> is not "fully
the scanner log says "The remote host is dead". it's not. not sure if
this has to do with the icmp. ping is disabled. using plain nmap i get
port scan results.
here is what the log says (ip is edited):
[Sun Nov 6 03:37:45 2016][3268] openvassd 5.0.7 started
[Sun Nov 6 03:47:37
