Hi Dude,
what i need to check is that, the client that ur using should have some around
10 ip to scan at a time. If Possible reduce the no of simultaneous scanning.
With Regards,
Rajesh Kumar De
Sr. Information Security Analyst.
GE Money, India,
Notice: The information contained in this e-mail message and/or attachments to
it may contain confidential or privileged information. If you are not the
intended recipient, any dissemination, use, review, distribution, printing or
copying of the information contained in this e-mail message and/or attachments
to it are strictly prohibited. If you have received this communication in
error, please notify us by reply e-mail or telephone and immediately and
permanently delete the message and any attachments. Thank you !
-----Original Message-----
From: nessus-bounces@list.nessus.org
[mailto:nessus-bounces@list.nessus.org]On Behalf Of Hari Sekhon
Sent: Monday, October 09, 2006 6:58 PM
To: nessus@list.nessus.org
Subject: Nessus taking long time to format results html_graph
I did a scan on thursday evening of my work subnet, a standard class C
with 254 addresses, mostly used ips.
I ran the scan from the command line as follows:
nessus -T html_graph -q localhost 1241 myuser mypassword targetfile
nessus_results_dir
The scan finished fairly quickly judging from the process list, I think
it completed within 2-3 hours, but it is still generating the results
and today is MONDAY!
Why has it taken so long (and it's still not finished). In fact, a file
listing from nessus_results_dir shows
ll nessus_results_dir/
total 748
drwxr-x--- 2 root root 4096 Oct 5 22:45 192_168_1_0/
drwxr-x--- 2 root root 4096 Oct 6 09:54 192_168_1_1/
drwxr-x--- 2 root root 4096 Oct 6 20:57 192_168_1_2/
drwxr-x--- 2 root root 4096 Oct 7 08:05 192_168_1_3/
drwxr-x--- 2 root root 4096 Oct 7 18:57 192_168_1_4/
drwxr-x--- 2 root root 4096 Oct 8 05:57 192_168_1_5/
drwxr-x--- 2 root root 4096 Oct 8 05:57 192_168_1_6/
drwxr-x--- 2 root root 4096 Oct 8 16:54 192_168_1_7/
drwxr-x--- 2 root root 4096 Oct 8 16:54 192_168_1_8/
drwxr-x--- 2 root root 4096 Oct 9 04:05 192_168_1_9/
-rw-r--r-- 1 root root 20806 Oct 5 22:45 chart_dangerous_services.gif
-rw-r--r-- 1 root root 0 Oct 5 22:45 chart_operating_systems.gif
-rw-r--r-- 1 root root 25750 Oct 5 22:45 chart_services_occurences.gif
-rw-r--r-- 1 root root 0 Oct 5 22:45 index.html
-rw-r--r-- 1 root root 12840 Oct 5 22:45 pie_most.gif
-rw-r--r-- 1 root root 16150 Oct 5 22:45 pie_risks.gif
-rw-r--r-- 1 root root 632824 Oct 5 22:45 report.nsr
which means it hasn't even generated 1/25th of all the hosts
results!!!!!!!!??????????
What on earth is going on? This is an Opteron 246 server (2GHz), the cpu
is at 100% - monopolized by nessus for the last few days, shouldn't this
be done by now?
Any help/ideas would be most appreciated.
I am using nessus 2.3.1 on linux.
-h
--
Hari Sekhon
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
nessus-client.doc
Description: nessus-client.doc
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
