Hi
I use automatized nessus from CLI every monday with cron in this way:
$nessus -c <MyNessusrc> -T nbe -V -qx <server> 1241 <user> <pass>
<MyTargets.txt> <MyResults.nbe>

My last successful scan was on July 10th. After, I always get a null
result. This appears in nessusd.messages log file
        [Fri Jul 21 09:31:22 2006][13738] connection from <ClientIP>
        [Fri Jul 21 09:31:22 2006][13944] Client requested protocol version 12.
        [Fri Jul 21 09:31:22 2006][13944] successful login of <user>
from <ClientIP>
        [Fri Jul 21 09:33:54 2006][13944] Empty data string --
closing comm. channel

I use nessusd v2.7 in a Linux kernel 2.6.5-7 box. Update to v2.8 but
the problem persists (both with CLI and GUI clients))

# nessusd -v
        nessusd (Nessus) 2.2.8 for Linux
        (C) 1998 - 2006 Tenable Network Security, Inc.

# nessus -v
        nessus (Nessus) 2.2.8 for Linux
        (C) 1998 - 2006 Tenable Network Security, Inc.
        SSL used for client - server communication
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to