You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a scan oscap xccdf eval with --report oscap-results.html argument, the following error appears at the end and the report creation fails:
XPath error : Memory allocation failed : growing nodeset hit limit
growing nodeset hit limit
^
runtime error: file /openscap/xsl/xccdf-report.xsl line 91 element value-of
XPath evaluation returned no result.
OpenSCAP Error: Could not apply XSLT /openscap/xsl/xccdf-report.xsl to XML file: NONEXISTENT [/openscap/src/source/xslt.c:183]
OpenSCAP Version:
1.3.10 (also tried with 1.3.8. Same error)
Operating System & Version:
Red Hat Enterprise Linux 8.9 (Ootpa)
Steps to Reproduce:
I believe this may be related to the number of files being scanned. So, have at least 318135 files in the system.
OSCAP_PROBE_MAX_COLLECTED_ITEMS works.
Any recommendations for the default value? Based on #2051, 1000 is fine?
Also, not sure if this is the right place to ask but, do you know how long would take to the openscap 1.3.10 release to reach the official distribution channels (so, a simple yum install would install version 1.3.10)?
It all depends on the system. And you should understand that limiting collected items might yield false-negative results. Pick the biggest you possibly can.
Description of Problem:
When running a scan
oscap xccdf eval
with--report oscap-results.html
argument, the following error appears at the end and the report creation fails:OpenSCAP Version:
1.3.10 (also tried with 1.3.8. Same error)
Operating System & Version:
Red Hat Enterprise Linux 8.9 (Ootpa)
Steps to Reproduce:
oscap xccdf eval --fetch-remote-resources --profile xccdf_org.ssgproject.content_profile_stig --report my-oscap-results.html --stig-viewer my-stig-viewer-results.xml /usr/share/xml/scap/ssg/content/ssg-rhel8-ds-1.2.xml
Actual Results:
HTML report is not generated.
Expected Results:
HTML report is generated.
Additional Information / Debugging Steps:
The text was updated successfully, but these errors were encountered: