I never had this problem as well until I upgraded the software.  I use ansible 
to update the clients so sometimes I don't realize a system is actually 
upgraded to the latest and greatest, such as OpenVAS.

Here is the strace:
connect(4, {sa_family=AF_INET, sin_port=htons(9390), 
sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ECONNREFUSED (Connection refused)
close(4)                                = 0
write(2, "Failed to acquire socket.\n", 26Failed to acquire socket.
) = 26
write(2, "OMP ping failed: Failed to estab"..., 49OMP ping failed: Failed to 
establish connection.
) = 49



From: Openvas-discuss [mailto:[email protected]] On 
Behalf Of Thijs Stuurman
Sent: Thursday, May 18, 2017 9:46 AM
To: [email protected]
Subject: Re: [Openvas-discuss] omp --get-tasks

Jonas,

I never had this problem. OMP here automatically connects just fine. Try a 
strace to see what it does?
Just run: "strace omp --ping"

From that I could pick out the following:

connect(4, {sa_family=AF_INET, sin_port=htons(9390), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0

It connects locally to 127.0.0.1 port 9390 which has (netstat -vnepl) the 
openvasmd service listening on my machine:

tcp        0      0 127.0.0.1:9390          0.0.0.0:*               LISTEN      
0          30921       5816/openvasmd


Thijs Stuurman
Security Operations Center | KPN Internedservices
[email protected]<mailto:[email protected]> | 
[email protected]<mailto:[email protected]>
T: +31(0)299476185 | M: +31(0)624366778
PGP Key-ID: 0x16ADC048 (https://pgp.surfnet.nl/)
Fingerprint: 2EDB 9B42 D6E8 7D4B 6E02 8BE5 6D46 8007 16AD C048

W: https://www.internedservices.nl<https://www.internedservices.nl/> | L: 
http://nl.linkedin.com/in/thijsstuurman



Van: Openvas-discuss [mailto:[email protected]] 
Namens Turner,Jonas
Verzonden: donderdag 18 mei 2017 15:20
Aan: Antu Sanadi <[email protected]>
CC: [email protected]
Onderwerp: Re: [Openvas-discuss] omp --get-tasks

Yeah I have restarted the services and the server.  The scans and everything 
else works well but I just can't seem to use the omp cli

From: Antu Sanadi [mailto:[email protected]]
Sent: Thursday, May 18, 2017 1:26 AM
To: Turner,Jonas
Cc: 
[email protected]<mailto:[email protected]>
Subject: Re: [Openvas-discuss] omp --get-tasks


Hi,

Have you tried restarting openvas services?

Make sure you do not have two services trying to bind to the same port and 
there is no conflict.
Generally "Failed to acquire socket" occurs when you are trying  to bind the 
port which is already occupied.

And also run the openvas-check-setup script  
http://www.openvas.org/setup-and-start.html

Thanks,
Antu Sanadi



On Wednesday 17 May 2017 07:04 PM, Turner,Jonas wrote:
I had everything working great and I updated OpenVAS and apparently the omp CLI 
doesn't work. I get the "Failed to acquire socket." Error.  Any thoughts on 
getting this cli to work again? :)

  

_______________________________________________

Openvas-discuss mailing list

[email protected]<mailto:[email protected]>

https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss



_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to