Oops, look like when starting openvasmd to listen on TCP port instead of unix socket, I'm no longer able to connect to the GSA WUI ! Here what I can see in gsad.log file -> Failed to connect to server: No such file or directory
I've to make openvasmd to listen to unix socket again for the GSA WUI to work. Gerhard, > On Jun 8, 2017, at 9:42 AM, Gerhard Mourani <[email protected]> wrote: > > You're right. I've changed my init script to start openvasmd as follow -> > openvasmd -a 127.0.0.1 -p 9390 and it works now, thanks. > > Gerhard, > >> On Jun 8, 2017, at 9:37 AM, Thijs Stuurman >> <[email protected]> wrote: >> >> Gerhard, >> >> Still gsad is not the correct service. Gsad is the web gui, I got that >> listening on 80 and 443: >> >> root@ivss:~# netstat -vnepl |grep gsad >> tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN >> 0 3859250 23930/gsad >> tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN >> 0 3852040 23929/gsad >> >> Openvasmd or gvmd is probably not listening at all on TCP and communication >> is probably done through a socket. >> Look ‘m up using “netstat -vnepl”. >> >> Either try using omp without any parameters for the IP and port to >> communicate with or set openvasmd to listen on a TCP port starting it >> specifically with options such as: >> >> openvasmd -p 9390 -a 127.0.0.1 >> >> or >> >> gvmd -p 9390 -a 127.0.0.1 >> >> OpenVAS9 it will be gvmd. >> >> >> >> Thijs Stuurman >> Security Operations Center | KPN Internedservices >> [email protected] | [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 | L: >> http://nl.linkedin.com/in/thijsstuurman >> >> Van: Gerhard Mourani [mailto:[email protected]] >> Verzonden: donderdag 8 juni 2017 15:26 >> Aan: Thijs Stuurman <[email protected]> >> CC: Turner,Jonas <[email protected]>; >> [email protected] >> Onderwerp: Re: [Openvas-discuss] omg can't connect to openvas >> >> Thijs, >> >> No, on my installation I use port 9392 as shown with the netstat -nlp >> command: >> >> tcp 0 0 :::9392 :::* >> LISTEN 25854/gsad >> >> >> I've nothing listening on port 9390 and here the result if I try to run omp >> on port 9390: >> >> omp -u admin -w admin -p 9390 -g -v >> WARNING: Verbose mode may reveal passwords! >> Will try to connect to host 127.0.0.1, port 9390... >> (omp:55229): lib serv-WARNING **: Failed to connect to server >> Failed to acquire socket. >> >> You can see that the message is different, port 9392 is the good one in my >> case but the omp command never complet. >> >> Gerhard, >> >> >> On Jun 8, 2017, at 9:19 AM, Thijs Stuurman >> <[email protected]> wrote: >> >> Gerhard, >> >> You are using the wrong port. >> OMP needs to connect to the openvasmd process (or gvmd in openvas9) on port >> 9390.as Jonas is also doing. >> Openvasmd / gvmd is the master process, omp and gsad (the web gui) connect >> to that to get the information. >> >> >> Thijs Stuurman >> Security Operations Center | KPN Internedservices >> [email protected] | [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 | L: >> http://nl.linkedin.com/in/thijsstuurman >> >> Van: Openvas-discuss [mailto:[email protected]] >> Namens Turner,Jonas >> Verzonden: donderdag 8 juni 2017 14:33 >> Aan: Gerhard Mourani <[email protected]>; >> [email protected] >> Onderwerp: Re: [Openvas-discuss] omg can't connect to openvas >> >> I am not sure if this will help but this is what I do and it works for me. >> You can change the port of course. >> >> 1. Configure omp.config with credentials >> a. [Connection] >> b. host=127.0.0.1 >> c. port=9390 >> d. username=someuser >> e. password=somepassword >> 2. openvasmd -a 127.0.0.1 -p 9390 >> 3. omp -g -v >> >> This provided me with the following output: >> <someuser@someserver:~$> omp -g -v >> >> WARNING: Verbose mode may reveal passwords! >> >> Will try to connect to host 127.0.0.1, port 9390... >> 8715c877-47a0-438d-98a3-27c7a6ab2196 Discovery >> 085569ce-73ed-11df-83c3-002264764cea empty >> daba56c8-73ec-11df-a475-002264764cea Full and fast >> 698f691e-7489-11df-9d8c-002264764cea Full and fast ultimate >> 708f25c4-7489-11df-8094-002264764cea Full and very deep >> 74db13d6-7489-11df-91b9-002264764cea Full and very deep ultimate >> f14981cc-80d9-4bec-8cca-ff3aa25c57be HCR - Full and Fast >> 2d3f051c-55ba-11e3-bf43-406186ea4fc5 Host Discovery >> bbca7412-a950-11e3-9109-406186ea4fc5 System Discovery >> Command completed successfully. >> >> From: Openvas-discuss [mailto:[email protected]] >> On Behalf Of Gerhard Mourani >> Sent: Thursday, June 08, 2017 8:19 AM >> To: [email protected] >> Subject: [Openvas-discuss] omg can't connect to openvas >> >> Hello, >> >> I'm trying to use omp command to connect to openvas but it doesn't work and >> never finish. Here my command. >> >> omp -u admin -w admin -p 9392 -g -v >> WARNING: Verbose mode may reveal passwords! >> Will try to connect to host 127.0.0.1, port 9392... >> >> openvas-manager-7.0.1 >> openvas-gsa-7.0.2 >> openvas-scanner-5.1.1 >> openvas-libraries-9.0.1 >> openvas-cli-1.4.5 >> >> gsad is running on port 9392 as follow: >> >> tcp 0 0 :::9392 :::* >> LISTEN 25854/gsad >> >> Gerhard, >> >> >
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
