Bug #4263
closed
Inventory produces invalid XML if line is too long
Added by Dennis Cabooter almost 11 years ago.
Updated over 9 years ago.
Description
Inventory produces invalid XML if line is too long.
17:49 < Kegeruneku> We reproduced the issue, it seems the report line for a
java application got clipped (too long)
17:49 < Kegeruneku> so the line does not contain the ending anchor (</CMD>),
thus producing invalid XML
Files
Hi Girls,
I can confirm this bug on our server, the inventory made by fusion-inv is malformed :
10 00:00:53] INFO report - Reports database: Automatic archive started for all reports before 2013-11-10 00:00
[2013-12-10 00:00:53] INFO report - Reports database: Automatic delete started for all reports before 2013-09-11 00:00
[2013-12-10 00:00:53] INFO report - Reports database: automatic delete completed for all reports before 2013-09-11 00:00, no reports to delete
[2013-12-10 00:00:53] INFO report - Reports database: automatic archive completed for all reports before 2013-11-10 00:00, no reports to archive
...
[2013-12-10 00:46:58] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'rudder-2013-12-02-16-45-27.ocs'
[2013-12-10 00:46:58] ERROR com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Error when trying to parse report:
Can't parse the input report, aborting
cause: Cannot parse uploaded file as an XML Fusion Inventory report
[2013-12-10 00:46:58] ERROR com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Exception was:
org.xml.sax.SAXParseException: The element type "CMD" must be terminated by the matching end-tag "</CMD>".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) ~[na:1.7.0_25]
Best Regards,
- Status changed from New to Rejected
- Target version changed from 2.8.2 to 2.6.10
This will be fixed by #4314!
rejecting this issue.
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF