Thanks vm for the tips. I tried cat /myNessus/nessusd.messages | grep 
"nmap_wrapper.nes" but got nothing. I used the ps -aux, as you suggested and found the 
following processes: which leads me to believe that Nessus is locked up and hanging or 
else the processes would not appear, is that correct? 


25610 ?        R      0:00 nessusd: testing 192.168.80.30
(/usr/local/lib/nessus
25625 ?        R    105:47 nessusd: testing 192.168.80.30
(/usr/local/lib/nessus
28611 ?        R      0:00 nessusd: testing 192.168.80.2
(/usr/local/lib/nessus/
28633 ?        R    104:56 nessusd: testing 192.168.80.2
(/usr/local/lib/nessus/
30486 ?        R      0:01 nessusd: testing 192.168.92.1
30488 ?        R      0:01 nessusd: testing 192.168.92.2
32142 ?        R      0:00 nessusd: testing 192.168.92.2
(/usr/local/lib/nessus/
32183 ?        R    104:09 nessusd: testing 192.168.92.2
(/usr/local/lib/nessus/
32573 ?        R      0:00 nessusd: testing 192.168.92.1
(/usr/local/lib/nessus/
32590 ?        R    104:05 nessusd: testing 192.168.92.1
(/usr/local/lib/nessus/
  861 ?        R      0:04 nessusd: testing 192.168.94.1
  941 ?        R      0:04 nessusd: testing 192.168.94.21
  956 ?        R      0:04 nessusd: testing 192.168.94.26
  958 ?        R      0:05 nessusd: testing 192.168.94.27
  987 ?        R      0:04 nessusd: testing 192.168.94.29
  989 ?        R      0:05 nessusd: testing 192.168.94.30
 1054 ?        R      0:03 nessusd: testing 192.168.94.45
 1084 ?        R      0:04 nessusd: testing 192.168.94.50
 1162 ?        R      0:02 nessusd: testing 192.168.94.66
 1174 ?        R      0:02 nessusd: testing 192.168.94.67
 1178 ?        R      0:02 nessusd: testing 192.168.94.68
 1184 ?        R      0:04 nessusd: testing 192.168.94.70
 3512 ?        R      0:00 nessusd: testing 192.168.94.21
(/usr/local/lib/nessus
 3572 ?        R    103:32 nessusd: testing 192.168.94.21
(/usr/local/lib/nessus
 3627 ?        R      0:01 nessusd: testing 192.168.94.99
 3648 ?        R      0:12 nessusd: testing 192.168.94.100
 3977 ?        R      0:00 nessusd: testing 192.168.94.27
(/usr/local/lib/nessus
 4043 ?        R    103:31 nessusd: testing 192.168.94.27
(/usr/local/lib/nessus
 4111 ?        R      0:00 nessusd: testing 192.168.94.30
(/usr/local/lib/nessus
 4178 ?        R    103:30 nessusd: testing 192.168.94.30
(/usr/local/lib/nessus
 4320 ?        R      0:00 nessusd: testing 192.168.94.67
(/usr/local/lib/nessus
 4359 ?        R      0:00 nessusd: testing 192.168.94.29
(/usr/local/lib/nessus
 4374 ?        R    103:30 nessusd: testing 192.168.94.67
(/usr/local/lib/nessus
 4426 ?        R    103:29 nessusd: testing 192.168.94.29
(/usr/local/lib/nessus
 4814 ?        R      0:00 nessusd: testing 192.168.94.70
(/usr/local/lib/nessus
 4838 ?        R      0:00 nessusd: testing 192.168.94.50
(/usr/local/lib/nessus
 4859 ?        R    103:27 nessusd: testing 192.168.94.70
(/usr/local/lib/nessus
 4898 ?        R    103:27 nessusd: testing 192.168.94.50
(/usr/local/lib/nessus
 4901 ?        Z      0:00 [nessusd <defunct>]
 4929 ?        Z      0:00 [nessusd <defunct>]
 4931 ?        R    103:27 nessusd: testing 192.168.94.50
(/usr/local/lib/nessus
 5620 ?        R      0:00 nessusd: testing 192.168.94.99
(/usr/local/lib/nessus
 5644 ?        R    103:21 nessusd: testing 192.168.94.99
(/usr/local/lib/nessus
 5823 ?        S      0:06 nessusd: testing 192.168.94.115
 6643 ?        R      0:00 nessusd: testing 192.168.94.66
(/usr/local/lib/nessus
 6663 ?        R    103:08 nessusd: testing 192.168.94.66
(/usr/local/lib/nessus
 6782 ?        R      0:00 nessusd: testing 192.168.94.26
(/usr/local/lib/nessus
 6818 ?        R    103:07 nessusd: testing 192.168.94.26
(/usr/local/lib/nessus
 7142 ?        R      0:00 nessusd: testing 192.168.94.68
(/usr/local/lib/nessus
 7172 ?        R    103:04 nessusd: testing 192.168.94.68
(/usr/local/lib/nessus
 7638 ?        S      0:00 nessusd: testing 192.168.94.45
(/usr/local/lib/nessus
 7659 ?        R    102:58 nessusd: testing 192.168.94.45
(/usr/local/lib/nessus
 8832 ?        S      0:01 nessusd: testing 192.168.94.115
(/usr/local/lib/nessu
 8917 ?        S      0:00 nessusd: testing 192.168.94.100
(/usr/local/lib/nessu
 8939 ?        R    102:34 nessusd: testing 192.168.94.100
(/usr/local/lib/nessu
10779 ?        S      0:00 nessusd: testing 192.168.94.115
(/usr/local/lib/nessu
10792 ?        R    102:16 nessusd: testing 192.168.94.115
(/usr/local/lib/nessu
10809 ?        R    102:16 nessusd: testing 192.168.94.115
(/usr/local/lib/nessu
11223 ?        S      0:00 nessusd: testing 192.168.94.1
(/usr/local/lib/nessus/
11245 ?        R    102:10 nessusd: testing 192.168.94.1
(/usr/local/lib/nessus/
11266 ?        R    102:10 nessusd: testing 192.168.94.1
(/usr/local/lib/nessus/
12075 ?        S      0:02 nessusd: testing 192.168.94.158
12381 ?        S      0:00 nessusd: testing 192.168.94.158
(/usr/local/lib/nessu
12393 ?        R     74:06 nessusd: testing 192.168.94.158
(/usr/local/lib/nessu
12609 ?        S      0:00 cupsd
23295 ?        S      0:00 CROND
23296 ?        S      0:00 /bin/bash /usr/bin/run-parts
/etc/cron.daily
23528 ?        SN     0:00 /bin/sh /etc/cron.daily/slocate.cron
23529 ?        S      0:00 awk -v 
progname=/etc/cron.daily/slocate.cron progname
23531 ?        DN     0:00 [updatedb]
23560 pts/2    S      0:00 bash
23589 pts/3    S      0:00 bash
23616 pts/3    S      0:11 emacs nessusd.messages
23621 pts/4    S      0:00 bash
23651 pts/4    R      0:00 ps -ax


Quoting Skill2Die4 <[EMAIL PROTECTED]>:

> Aaron :
> 
> >> 2nd - What are you using for criteria to determine that
> Nessus had 
> >> indeed completed the port scan?
> 
> If you used nmap as scanner then , 
> .........................................
> $ find / -name nessusd.messages
> $ cat /myNessus/nessusd.messages | grep "nmap_wrapper.nes"
> .....<analyze the result>......
> 
> To see if the nmap_wrapper found anything you can delve into
> the 
> kb folder.
> 
> 
> >> 1st - don't trust the status bar!  The FAQ will fill you in
> on that.  ;)
> 
> I guess in such case you can just do a  "ps -ax |  grep
> "nessusd: serving"
> and see if its still serving your client.
> 
> OR, you could " tail -f /myNessus/nessusd.messages " , to
> check if any
> new scan is being initiated against your targets.
> 
> 
> It would have been easier to suggest you, if you gave more
> info on :
> 1. Portscan settings
> 2. Number of hosts
> 3. bandwidth
> 
> The above three would helped to guess regarding how much time
> the
> scan should have actually taken.
> 
> HTH,
> 
> -=skillz=-
> 
> 
> 
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to