Little correction first, I was trying to run: gvmd -a 127.0.0.1 -p 9390
The gvmd.log has following entry for the command:
main:MESSAGE:2019-07-08 08h33.40 utc:6164: Greenbone Vulnerability Manager version 8.0.0 (DB revision 205)
md main:WARNING:2019-07-08 08h33.40 utc:6164: main: Main process is already running
What I’m trying to do is establish a tls communication from a GMP Client to the gvmd. I’m using a VM for this, which has everything running on localhost. So far the only way to accomplish this is this for me:
gvm-cli socket --sockpath /var/run/gvmd.sock --gmp-username=admin --gmp-password=admin -X “<get_version/>”
Running the same command with tls I get following Error:
gvm-cli tls --hostname 127.0.0.1 --port 9390 --gmp-username=admin -X “<get_version/>”
Enter password for admin:
[Errno 111] Connection refused
In the older openvasmd Version, I could fulfill the get version request without providing a socket or anything: omp --username admin --xml="<get_version/>"
Having to provide a path to the socket is not desired, since I’m using a 3rd party program that is trying to connect to the gvmd (the code is tailored for the older openvasmd Version, but according to the docs it should still be compatible). The 3rd party program was able to connect to the openvasmd in the past, but since the rebrand to greenbone, it is unable to establish a connection.