SEVERE *** ERROR *** Can not parse content

JJ20
Kilo Guru

Restarted MID server (due to it appearing hung thanks to a discovery job). Noticing the following error in agent.0.log: how do we determine what is causing that fatal? 11/04/20 05:07:41 (622) Worker-Standard:ServiceDiscoveryProbe-3286778d1b9ce0108ef69829bc4bcba5 SEVERE *** ERROR *** Can not parse content com.snc.sw.exception.FileParsingException: Failed to parse XML file. Error: Problem with File Structure, Invalid XPath expression: "": Unexpected ''

1 ACCEPTED SOLUTION

JJ20
Kilo Guru

bug in the kubernetes pattern to be fixed in Paris.

View solution in original post

13 REPLIES 13

FLP1
Tera Contributor

Hello @Sandeep132 can you share your workaround? thank you!! 

@FLP1 This issue is very old one and I do not think is happening anymore. As mentioned in the solution accepted, the issue is fixed in Paris release.

Ashutosh Munot1
Kilo Patron
Kilo Patron

Hi,

I suggest to debug the pattern and check the EVAL scripts which is causing this issue.

Thanks,
Ashutosh

The biggest challenge is figuring out which pattern is causing the noise.

 

I'd love to debug it once I know what IT is.

HI,

you can check that by doing a search in pattern log table and see which pattern has this error.


Thakns,
Ashutosh