<![CDATA[xapi crash loop]]>Hi,

after recovering from a power failure, xapi keeps crashing with this obscure error in xensource.log:

Aug 13 11:34:20 hostname xapi: [debug||0 ||xapi] xapi top-level caught exception: INTERNAL_ERROR: [ (Scanf.Scan_failure\x0A  "scanf: bad input at char number 6: looking for ':', found '.'") ]

Does anyone have an idea what causes this situation?

All the best,
Sven

]]>https://xcp-ng.org/forum/topic/6210/xapi-crash-loopRSS for NodeThu, 13 Aug 2026 13:03:59 GMTSat, 13 Aug 2022 12:01:46 GMT60<![CDATA[Reply to xapi crash loop on Sun, 14 Aug 2022 21:26:01 GMT]]>Found it. Error is related to https://github.com/xapi-project/xen-api/issues/4141

Somehow, the PCIe bus address of the server's ASPEED VGA adapter changed.

I got the new bus address with lspci and edited state.db accordingly. Works now. However, this seems to be a very strange bug.

]]>https://xcp-ng.org/forum/post/52110https://xcp-ng.org/forum/post/52110Sun, 14 Aug 2022 21:26:01 GMT<![CDATA[Reply to xapi crash loop on Sun, 14 Aug 2022 20:25:06 GMT]]>Are there any tools to edit state.db?

]]>https://xcp-ng.org/forum/post/52109https://xcp-ng.org/forum/post/52109Sun, 14 Aug 2022 20:25:06 GMT<![CDATA[Reply to xapi crash loop on Sun, 14 Aug 2022 20:23:56 GMT]]>@Danp unfortunately not, at least not externally. And I think restore metadata would be kind of tricky, since the xapi tools won't work, XO is inside a VM and reinstalling xcp-ng would kill the SR on the primary disk.

It's a test/dev system at home anyway and not too important. I'll erase it and make a new one. However, I do now understand the importance of metadata backups better.

]]>https://xcp-ng.org/forum/post/52108https://xcp-ng.org/forum/post/52108Sun, 14 Aug 2022 20:23:56 GMT<![CDATA[Reply to xapi crash loop on Sat, 13 Aug 2022 13:16:14 GMT]]>Probably some corruption in your xapi database. Do you have a backup of the pool metadata?

]]>https://xcp-ng.org/forum/post/52095https://xcp-ng.org/forum/post/52095Sat, 13 Aug 2022 13:16:14 GMT