Start a Conversation

Unsolved

R

1 Rookie

 • 

4 Posts

83

December 6th, 2024 09:39

Omreport XML error

Hello

I know that fedora is not supported but until now the omreport command worked.

After updating to Fedora Server to version 41 on my Dell T140 I have an XSL error After entering the command:

omreport storage vdisk

Entity: line 1: parser error : Extra content at the end of the document
MA cli="true"><OMAUserRights>1</OMAUserRights><SMStatus>0</SMStatus></OMA></oma>
                                                                              ^
Entity: line 1: parser error : Extra content at the end of the document
MA cli="true"><OMAUserRights>1</OMAUserRights><SMStatus>0</SMStatus></OMA></oma>
                                                                              ^
Entity: line 1: parser error : Extra content at the end of the document
var/lib/openmanage/xslroot//sm/template/en/cli/RptVDisk.xsl" /></xsl:stylesheet>
                                                                              ^
xsltParseStylesheetMemory: parsing XSL memory failed
Error! XML Transformation failed

1 Rookie

 • 

4 Posts

December 12th, 2024 16:20

@pgajdos i don't understand how to solve my problem

1 Rookie

 • 

5 Posts

December 13th, 2024 12:34

If I am right and the issue you are seeing is the one described in upstream issue 638 linked in my comment, then I guess omreport devs should fix their code to work with libxml2 2.12. The temporary workaround could be to downgrade to libxml2 2.10.

1 Rookie

 • 

4 Posts

December 18th, 2024 10:49

I reported it to Dell support, I hope they will release an update :)

1 Rookie

 • 

5 Posts

December 18th, 2024 11:04

Maybe I should explicitly ask, whether omreport devs could outline the course of action, if possible. Otherwise people would be stuck with libxml2 2.10.

1 Rookie

 • 

5 Posts

December 18th, 2024 14:09

:) Nice coincidence. Thank you!

1 Rookie

 • 

4 Posts

December 18th, 2024 14:21

@pgajdosI got a respons:

"Thank you for the information, I verified the behavior of the command in the installed system with our older department. Unfortunately, such behavior is normal due to the lack of compatibility of the system with the server. Currently, there is no solution to the given problem, you have to wait for newer versions of OME or for the system to be added as compatible with the server."

1 Rookie

 • 

5 Posts

January 6th, 2025 13:13

Thanks @raftro for letting me know.

No Events found!

Top