Nessus
[Top] [All Lists]

RE: overloaded CPU ?

To: "'Edy'" <email@edylie.net>
Subject: RE: overloaded CPU ?
From: "J. M. Seitz" <jms@bughunter.ca>
Date: Mon, 20 Nov 2006 09:25:23 -0800
Cc: nessus@list.nessus.org
Delivered-to: sp-com-lists@consult.net
Delivered-to: nessus-list1@securepoint.com
Delivered-to: nessus@list.nessus.org
In-reply-to: <4561DE9A.30501@edylie.net>
List-archive: <http://mail.nessus.org/pipermail/nessus>
List-help: <mailto:nessus-request@list.nessus.org?subject=help>
List-id: Discussion of Nessus software <nessus.list.nessus.org>
List-post: <mailto:nessus@list.nessus.org>
List-subscribe: <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=subscribe>
List-unsubscribe: <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=unsubscribe>
Sender: nessus-bounces@list.nessus.org
Thread-index: AccMxnpn7wTL13tVSLuqCGWT51L+FwAAL1tA
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>