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: Problem Running Nessus |
|---|---|
| Date: | Mon, 20 Jun 2005 15:21:05 -0400 |
Hi there -- Thanks for your reply. I don't have an explanation for it, but when I manually ran the nessus-update-plugins script and then the nessusd -D command, the program appeared to run properly. I then ran the two scans that had previously failed and both appear to be running properly. I'll continue to monitor the program overnight and see what, if anything, develops. One other quick question: I currently do not have nessusd automatically starting at system boot. I was planning on adding a line to the rc.local file in order to accomplish this. Do you foresee any problems by my doing so? Thanks. -----Original Message----- From: nessus-bounces@list.nessus.org [mailto:nessus-bounces@list.nessus.org] On Behalf Of George A. Theall Sent: Monday, June 20, 2005 11:35 AM To: Nessus@list.nessus.org Subject: Re: Problem Running Nessus On Mon, Jun 20, 2005 at 10:47:25AM -0400, Kaplan, Andrew H. wrote:
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
Are you able to run nessus-update-plugins by hand today?
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
This suggests that nessusd was down when you tried to run the scans.
The version of Nessus that I am running is version 2.2.3.
Once you get things working, you may want to upgrade as 2.2.4 offers improvements, especially in terms of SSL reads.
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.
nessusd.messages should have information explaining why the daemon shut down and possibly why it won't start. Do you see anything in there that might explain the problem? If not, try using a tool such as strace to trace nessusd's execution as it starts up and study the last few lines. George -- theall@tenablesecurity.com _______________________________________________ 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: | Make Plugins run on different port, Deepen Desai |
|---|---|
| Next by Date: | RE: Problem Running Nessus, Lachniet, Mark |
| Previous by Thread: | Re: Problem Running Nessus, George A. Theall |
| Next by Thread: | RE: Problem Running Nessus, Lachniet, Mark |
| Indexes: | [Date] [Thread] [Top] [All Lists] |