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: | Problem Running Nessus |
|---|---|
| Date: | Mon, 20 Jun 2005 10:47:25 -0400 |
Hi there --
I have had Nessus running for several months now where on a nightly basis
several cron jobs are run that do the following:
1. An update of the Nessus plugins via the
/usr/local/sbin/nessus-update-plugins script.
2. A scan on our Windows servers and generates a file
that I check the following day.
3. A scan on our UNIX servers that does a job similar to
that for Windows.
The syntax of the Windows and UNIX cron jobs is the following:
/usr/local/bin/nessus -x -q 127.0.0.1 1241 <username> <password>
/home/<username>/<targetfile> /usr/local/apache/htdocs/outputfiles/<resultsfile>
-T html
Starting this past Saturday morning, the nessus-update-plugins script failed
with the following error message:
An unknown HTTP error occured (http error code: 1)
Could not retrieve the Nessus plugins
Aborting
Similarly, the cron jobs failed and the error message that I encountered in both
instances is as follows:
nessus : Could not open a connection to 127.0.0.1
The version of Nessus that I am running is version 2.2.3. I also tried running
the program in daemon mode, /usr/local/sbin/nessusd -D, but when I did a ps -ef
|grep nessusd check, the program did not appear to be running. I have also
rebooted the server to see if that would help matters, and it did not. Finally,
I verified the ip address and hostname of the server will still valid, and they
appeared to be. Does anyone have any ideas? Thanks.
_______________________________________________
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: | Re: GET GET seen in Apache logs from Nessus Scan, Hugo van der Kooij |
|---|---|
| Next by Date: | Re: Problem Running Nessus, George A. Theall |
| Previous by Thread: | GET GET seen in Apache logs from Nessus Scan, Brian Jameson |
| Next by Thread: | Re: Problem Running Nessus, George A. Theall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |