2016-11-10 14:16 GMT+02:00 Christian Fischer <christian.fischer@greenbone. net>:
> log_whole_attack is only logging the following into your > openvassd.messages: > Well, here is what I try to understand: how can I find the reason of error status of the scan? More specifically, how can I catch any output from nasl script? For example if debug_print in http://plugins.openvas.org/nasl.php?oid=11801 emits something, how can I catch it? My assumption is that it should appear in the file set by dumpfile option: > dumpfile > Some plugins might issue messages, most of the time to inform you that something went wrong. If you want to read these messages, set this value to a given file name. If you want to save space, set this option value to /dev/null Is my assumption correct? Also it's unclear to me of how verbose regular output to the dumpfile is. Is that a normal situation when several 'Full and fast ultimate' scans result in literally couple of lines in the dumpfile? > pcap_compile: syntax error > pcap_compile: syntax error > pcap_compile: syntax error > pcap_compile: syntax error > pcap_compile: syntax error > pcap_compile: syntax error > pcap_compile: unknown host 'addr'
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
