I am running nmap by itself against the troublesome host, which I have learned is an old DNS server running Solaris. In the meantime, I have noticed that although the task has completed (omp --get-tasks shows "Done" for that task), I still see processes which were part of the scan. dirb is still running/trying to run against 2 addresses in the subnet. Is this normal for processes to continue after scan ends?
Jack Harvey CISSP Synnex Corporation 864-349-4939 -----Original Message----- From: Henri Doreau [mailto:[email protected]] Sent: Wednesday, July 16, 2014 1:17 PM To: Jack Harvey Cc: [email protected] Subject: Re: [Openvas-discuss] nmap.nasl 2014-07-16 18:54 GMT+02:00 Jack Harvey <[email protected]>: > I run several scans each night all with the same, unmodified “Full and > very deep ultimate” config. Several of those are scanning /24 > subnets. One specific subnet scan > > “hangs” several (3-4) times during the week. I created tasks breaking > the subnet down into 4 parts and by watching the active processes, > have narrowed the problem/issue > > down to (I believe) a single computer. ps aux shows this: openvassd: > testing xxx.xxx.xxx.xxx (/var/lib/openvas/plugins/nmap.nasl). Does > this mean that an nmap scan > > is still trying to complete? Is there something that I can look > at/for to relieve this? > > > > Jack Harvey CISSP Hello, Yes it might be the case. With ps you can also check if nmap is properly running, and scanning this host. Does it exhibits peculiar behavior if you scan it manually with nmap? Regards -- Henri _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
