Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: overloaded CPU ? |
|---|---|
| Date: | Mon, 20 Nov 2006 09:25:23 -0800 |
Are you running this in cron? Do an uptime now to see what your load average is or a vmstat would work as well. If your load is fine now, then write a quick bash script to run just before nessus, and get it to do periodic snapshots: -----snip-snip--snip #!/bin/bash for((i=0;i<20;i++)) do echo "Snapshot: "`date` >> profile.log echo >> profile.log echo "Uptime: " >> profile.log uptime >> profile.log echo >> profile.log echo "Free: " >> profile.log free >> profile.log echo >> profile.log echo "Vmstat: " >> profile.log vmstat >> profile.log echo >> profile.log echo "End of Snapshot ---------" >> profile.log sleep 60 done -----snip-snip--snip This was just typed into Outlook so I would test it first but essentially 20 minutes should be sufficient to determine if you are running into resource starvation during your nessus runs. You could also add some ps information if you wanted to... JS -----Original Message----- From: nessus-bounces@list.nessus.org [mailto:nessus-bounces@list.nessus.org] On Behalf Of Edy Sent: Monday, November 20, 2006 8:58 AM To: nessus@list.nessus.org Subject: overloaded CPU ? Anyone know what causes this? [root@skipjack ~]# cat /opt/nessus/var/nessus/logs/nessusd.dump [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) [3890] internal_send->select (4) timed out after 60 secs (overloaded CPU ?) Thank you Edy _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | overloaded CPU ?, Edy |
|---|---|
| Next by Date: | os_send(4) failed, Edy |
| Previous by Thread: | overloaded CPU ?, Edy |
| Next by Thread: | Re: overloaded CPU ?, Edy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |