Hello Everyone,

Sorry for the last email re: separate report output issues and log output,
I had assumed the logs were incremental, not cleared / overwritten
per-incident like seems to be the case...

I have re-downloaded the GSA Beta5 tarball, re-configured, compiled, etc,
and still receive this when exporting to ITG format...

creating dictionary for stylesheet
reusing dictionary from /usr/local/etc/openvas/openvasmd/xsl/ITG.xsl for
stylesheet
xsltParseStylesheetProcess : found stylesheet
xsltPrecomputeStylesheet: removing ignorable blank node
xsltCompilePattern : parsing '/'
xsltCompilePattern : parsed /, default priority 0.500000
added pattern : '/' priority 0.500000
parsed 1 templates
Resolving attribute sets references
Creating sub-dictionary from stylesheet for transformation
Registered 0 modules
reusing transformation dict for output
Registering global variables
Registering global variables
from /usr/local/etc/openvas/openvasmd/xsl/ITG.xsl
xsltProcessOneNode: applying template '/' for /
xsltApplyTemplates: select get_report_response/report/result
[port='general/IT-Grundschutz-T']/description
xsltApplyTemplates: select didn't evaluate to a node list
freeing transformation dictionary
freeing dictionary from stylesheet

When exporting to CPE I receive a very similar output to the
openvasmd_generic.log...

creating dictionary for stylesheet
reusing dictionary from /usr/local/etc/openvas/openvasmd/xsl/CPE.xsl for
stylesheet
xsltParseStylesheetProcess : found stylesheet
xsltPrecomputeStylesheet: removing ignorable blank node
xsltCompilePattern : parsing '/'
xsltCompilePattern : parsed /, default priority 0.500000
added pattern : '/' priority 0.500000
parsed 1 templates
Resolving attribute sets references
Creating sub-dictionary from stylesheet for transformation
Registered 0 modules
reusing transformation dict for output
Registering global variables
Registering global variables
from /usr/local/etc/openvas/openvasmd/xsl/CPE.xsl
xsltProcessOneNode: applying template '/' for /
xsltApplyTemplates: select get_report_response/report/result
[port='general/CPE-T']/description
xsltApplyTemplates: select didn't evaluate to a node list
freeing transformation dictionary
freeing dictionary from stylesheet

Any thoughts???

Also, on an unrelated note... It seems like GSA is much more stable (at
least in my experience on a 32-bit host than 64-bit), however I still
notice that intermittently... I start GSA...

In my environment...

sudo gsad --mport=9391 --aport=9393 --port=9392 --http-only

Everything seems to run fine to scan initially and possibly one or two
subsequent scans, then scan attempted after that never actually initializes
via openvassd.  The console still responds, and I can navigate GSA, but all
I have been able to do to this point is kill the gsad / openvasmd process
and restart them both...

In the Openvasmd log in /usr/local/var/log/openvas/openvasmd, I notice the
following, which appear to be relevant...

md   main:WARNING:2010-03-12 12h19.00 AST:19918: sql_x: sqlite3_prepare
failed: no such table: meta
(this is after I religiously do a openvasmd --sport=9390 --rebuild prior to
starting up the main daemon)

md   main:WARNING:2010-03-12 12h20.38 AST:19918: sql_x: sqlite3_step
finished too soon
(no idea what it is trying to accomplish here??)

finally... many, many...

lib  serv:MESSAGE:2010-03-12 12h23.52 AST:20746:    Gave up trying to
gnutls_bye

(I tried updating to the latest gnutls packages, but the problem seems to
persist), this is the most frequent output noticed when for instance I try
to start up a 2nd, 3rd scan, when it doesn't init the scan with
openvassd....

Thanks in advance and cheers,




Matthew Coene


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to