Hi,Yes, gzip'ing is breaking it, as the active scan is still writing to old file descriptor of the file rotated out.
Have you got logrotate setup to gzip the previous log file? The active scans will still be writing to it, so this will break them. Maybe turn off gzip'ing?
So I'll switch to syslog, but it still seems as if nessus is broken.
If the main process can write to the new file after a HUP, shouldn't the active scan?
Thx
Paul
Steve Francis wrote:
I have lots of networks to scan, so scans take several days. When I rotate the file /usr/local/nessus/var/nessus/logs/nessusd.messages , and send the master nessus process a HUP, I no longer get activity logged for the still ongoing scans.
e.g. right now I have a scan running, rotated my log file, sent a HUP, and the entire file consists of:
cat /usr/local/nessus/var/nessus/logs/nessusd.messages
Mar 26 23:00:00 rack1-401 newsyslog[99331]: logfile turned over
[Mon Mar 29 15:09:48 2004][81258] nessusd 2.0.10 started
Yet the scan is proceeeding - with no way for me to see what is going on.
Is log file rotation not supported while a scan is running? THis is using nessusd 2.0.10.
Thanks
_______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
