On Sat, Jun 21, 2003 at 04:37:22AM -0700, [EMAIL PROTECTED] wrote: > I have a simple shell script[0] which calls update-nessusrc and > supplies it with a list of families and plugins to use. This works > fine if I call it from the command line however it fails if run from > cron with the following error: > > Could not connect to nessusd (rc=1)!
This indicates nessus could not connect to the remote host. I run update-nessusrc with no problems from cron all the time, although my crontab entries call the update-nessusrc directly. > The $nessusd_* envirenment variables[1] are all set correctly in the > actuall update-nessusrc script While update-nessusrc does use variables such as $nessusd_host and $nessusd_port, their values must be hardcoded in the script directly, *not* read from the environment or commandline. If hardcoding the values doesn't resolve your problem -- and since you claim you can run this from the commandline fine I doubt it will -- then I suggest you run update-nessusrc in debug mode (ie, add "-d" option to your commandline) and examine the debugging messages that are produced. This will allow you to see exactly how nessus is being called as well as exactly what error messages it produces. George -- [EMAIL PROTECTED]
pgp00000.pgp
Description: PGP signature
