RE: nessusd failure on Redhat 2.4.9-e.30smp

Jimmy Corio Wed, 12 May 2004 08:33:15 -0700

Keyur...

I am experiencing the same failure on a box that is not part of our Tenable solution. It is a failure in the Nessus installation and not the Tenable/Nessus coordination... and as a side note, I do not see a Nessus RPM available on the Tenable site...

To answer Sonny's questions... there is nothing in the Nessus logs or the system logs... I do not get a failure message of any sort on the screen, only the job run number as it closes. After it closes, I no longer see nessusd running in PS nor do I see the port listening in NETSTAT.

I am comparing the packages between my lab setup and my field installation to see what the difference is.

Thanks...

Jimmy

Keyur Lavingia <[EMAIL PROTECTED]> wrote:

Its because Tenable has made changes in the way nessus runs/performs according to the way the Lightning Console works. You should only use the Nessus RPM available from the Tenable website for use with the console. It will work best only then.

Keyur

From: Discini, Sonny [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 9:01 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: nessusd failure on Redhat 2.4.9-e.30smp

You mentioned that Nessusd dies. What did you find in the logs? Are you presented with an error message of any sort? Have you compared what packages are installed on your lab machine vs. your field machine?

Sonny Discini

Senior Network Security Engineer

Department of Technology Services

Enterprise Infrastructure Division

Montgomery County Government

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jimmy Corio
Sent: Tuesday, May 11, 2004 9:18 PM
To: [EMAIL PROTECTED]
Subject: nessusd failure on Redhat 2.4.9-e.30smp

I have a nessus installation that worked perfect in the lab when installed with the Tenable Lightning console management system, but when trying to installation in the field for production, I am running into an issue where nessusd fails after starting.

Here is my config (nessusd -d)

This is Nessus 2.0.10 for Linux 2.4.9-e.30smp

compiled with gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-118.7.2)

Current setup :

    Experimental session-saving         : enabled

    Experimental KB saving                : enabled

    Thread manager                           : fork

    nasl                                            : 2.0.10

    libnessus                                    : 2.0.10

    SSL Support                               : enabled

    SSL is used for client/server communication

    Running as euid                          : 0

This is installed on a Dell PowerEdge 1750. Dual proc, 1Gb of RAM... the box in the lab was the exact same system... the OS builds were from the same basic image although they were completed by two different techs.

The installation in the lab I allows the Tenable Lightning installation run the nessus-installation.sh and in the field I am doing it myself as I don't have proxy configuration yet... Other than that I do not see any differences in the configurations... it is just that nessusd will die within a minute of starting in the field... and runs all day long in the lab.

Thanks in reading through this... and for any thoughts...

Jimmy

Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'

Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'

_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus

RE: nessusd failure on Redhat 2.4.9-e.30smp

Reply via email to