Nessus
[Top] [All Lists]

Re: Cron job Failure

To: nessus@list.nessus.org
Subject: Re: Cron job Failure
From: Dion Stempfley <dtsonline@verizon.net>
Date: Fri, 23 Feb 2007 16:06:10 -0500
Delivered-to: sp-com-lists@consult.net
Delivered-to: nessus-list1@securepoint.com
Delivered-to: nessus@list.nessus.org
In-reply-to: <037801c75783$5da1b700$6601a8c0@JSG>
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>
References: <881224.14639.qm@web53010.mail.yahoo.com> <037801c75783$5da1b700$6601a8c0@JSG>
Sender: nessus-bounces@list.nessus.org
User-agent: Thunderbird 1.5.0.9 (Windows/20061207)
Are there any messages in your cron log?  Are other cron jobs running okay?

In my experience, once you've eliminated the cron daemon and problems with the config file, job failures result from problems in the environment. Make sure that the system environment contains everything it needs to run the client program. Common problems I have had include the command path and dynamic library path.

I usually write a script that sets up the environment I need and then calls the executable. Then in the crontab put the full path to the script.

Good Luck,

Dion

*From:* nessus-bounces@list.nessus.org [mailto:nessus-bounces@list.nessus.org] *On Behalf Of *Frank OSborne
*Sent:* Friday, February 23, 2007 14:08
*To:* nessus@list.nessus.org
*Subject:* Cron job Failure

I have a dilemma that I hope someone else here has dealt with. I'm
using SUSE 10.1 and I have a scheduled cron job that fails to execute, but
runs fine from the CLI manually. Its a Scheduled Nessus scan with "safe
checks" enabled so I do get a prompt (see below) which doesn't require
any input but once scheduled this thing won't run. I'm doing everyting
as root so I don't think its a rights issue . Anyone have any ideas?

Command issued:
nessus -q 127.0.0.1 1241 user password
/home/osbfr01/iscan/testtarget.txt /home/osbfr01/iscan/test1.html

Prompt:

*** The plugins that have the ability to crash remote services or hosts
have been disabled. You should activate them if you want your security
audit to be complete
Thanks in advance, Frank

------------------------------------------------------------------------

Looking for earth-friendly autos?
Browse Top Cars by "Green Rating" <http://autos.yahoo.com/green_center/;_ylc=X3oDMTE4MGw4Z2hlBF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDZ3JlZW5jZW50ZXI-> at Yahoo! Autos' Green Center.


------------------------------------------------------------------------

_______________________________________________
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>