problem with openvas after upgrade

[l1nu$]

problem after upgrade (repo) with openvas
can not be successful connection between the client and server

after upgrade
launched the server
All plugins loaded.

> netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp6 0 0 :::9390 :::* LISTEN 5788/openvassd: wai))

try to connect with the client to the server, but the client crashes and I can only kill

while the client is blocked in (start connection)
> root@bt:~# netstat -antp|grep openvas
tcp6 0 0 :::9390 :::* LISTEN 5788/openvassd: wai
tcp6 0 0 127.0.0.1:9390 127.0.0.1:53091 ESTABLISHED 6054/openvassd: ser

precise
certificato is ok
user/pass is ok
NVT -sync is ok
openvas-menu is ok

tried to change localhost with 127.0.0.1 (?) and it does not work
any ideas?
thanks

[Archangel-Amael]

Do you have any other network problems? I mean can you ping other networks?
How is your BT setup? VM HDD USB etc ?

[l1nu$]

Do you have any other network problems? I mean can you ping other networks?
How is your BT setup? VM HDD USB etc ?

there are no other problems in my small LAN and can ping other hosts without problems before doing the update openvas worked well.
i use BT4 final on HDD
thanks in advance

[thorin]

The client connection can take quite a while if it has to download the entire list of plugins etc, I suggest you fire up the client and give it even as much as 10 mins before killing it.

[Archangel-Amael]

hey thorin thanks for digging this one back up. I lost it.

@OP did you receive any error messages after updating? Or did you receive a message stating that all updates were successful?
Also waiting for the server to startup can indeed take quite a bit of time.

[l1nu$]

Hi thorin
yes sure but after 65 minutes of waiting ...
--- Window with title "Connecting ..." is not responding---

@OP did you receive any error messages after updating? Or did you receive a message stating that all updates were successful?
Also waiting for the server to startup can indeed take quite a bit of time.[/QUOTE]

Hi Archangel-Amael
remember it was alright

[thorin]

Hi thorin
yes sure but after 65 minutes of waiting ...
--- Window with title "Connecting ..." is not responding---

Ok agreed that's too long.

Looking at your original post it looks like netstat only lists openvas listening on IPv6 (not IPv4 ... 127.0.0.1). I don't have a machine in front of me that I can check this one but I'm fairly sure that's the what's meant by the "tcp6" leading all the netstat lines.

Have you checked openvas logs?

[Archangel-Amael]

Good call thorin.
OP Try this from the command line, and let me know what happens.

# nohup openvasd &
[1] 4508
# nohup: ignoring input and appending output to `nohup.out'
# tail -f nohup.out

Which will output something like:

tail -f nohup.out
Loading the plugins...

Then :

#/opt/openvas# ps aux |grep openvas

To make sure it is running. You really don't need the above but you can run it.
Then:

netstat -anp |grep openvas

To find again the port and in your case IP version.
If all goes well try this command:

# OpenVAS-Client -q 127.0.0.1 9390 admin password iptoscan.txt scanresults.html -T html

[l1nu$]

Hi
sorry...
once again hangs on connection

---> root@bt:~/open# nohup openvassd &
[1] 16083
root@bt:~/open# nohup: ignoring input and appending output to `nohup.out'

---> root@bt:~/open# tail -f nohup.out
W32.Sasser.Worm.nasl could not be added to the cache and is likely to stay invisible to the client.
W32.Sasser.Worm.nasl could not be added to the cache and is likely to stay invisible to the client.
W32.Sasser.Worm.nasl could not be added to the cache and is likely to stay invisible to the client.
W32.Sasser.Worm.nasl could not be added to the cache and is likely to stay invisible to the client.
Loading the plugins... 17442 (out of 17479)

--->always crashes on plug-17442

---> root@bt:~/open# ps aux |grep openvas
root 16102 0.0 2.3 79564 74412 ? Ss 01:41 0:00 openvassd: waiting for incoming connections
root 16211 0.0 0.0 3232 780 pts/2 R+ 01:45 0:00 grep openvas

---> root@bt:~/open# netstat -anp |grep openvas
root 6755 0.0 2.4 80132 74984 ? Ss May19 0:00 openvassd: waiting for incoming connections
root 7965 0.0 0.0 2016 580 pts/1 S+ 00:30 0:00 grep openvas

---> root@bt:~/open# OpenVAS-Client -q 127.0.0.1 9390 xxxx xxxxxxxx file-IP.txt scanresults.html -T html
Please choose your level of SSL paranoia (Hint: if you want to manage
many servers from your client, choose 2. Otherwise, choose 1. Or 3,
if you are paranoid.
1

and does not go ahead

Thank you so much Archangel-Amael & Thorin

[gambitz]

Hello all. I have the same problem as the OP. I followed ArchAngel-amael's how-to video to use OpenVAs. on BT4 R1 final.

The only difference between his video and this version is that I have to "start OpenVas Scanner" which is a server.

My client is able to connect to the server (localhost) and download plug-ins, etc. I made new task, scope, then connect again for plug-ins. (enable all plug-ins)

Put in the target IP.

"Excute". Worked and got a report.

-Closed client.

-"Stop OpenVas Scanner".

-Run "OpenVas NVT Sync" took a while to update all plug-ins.. Completed OK.

-Run "Start OpenVas Scanner"

-Run "OpenVas Client"

Tried to connect to server, it stays at "connecting...." forever.. I had to terminate it. I tried it few times. Didnt work. I even rebooted, tried restarting the server few times, etc. no luck.

By the way, i did netstat and on the top it shows openvas running ok.

"root@bt:~# netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost:57235 localhost:9390 ESTABLISHED
tcp6 0 0 localhost:9390 localhost:57235 ESTABLISHED"

I did not do the suggestions Amael suggested becasue OP said it didnt work for him.

Any other suggestions? Thanks for reading.