Andi Chandler

andibing

@john.c said:

nd need to be cleared, before re-attempting the update. Checking the logs will help

Just for completeness... it kept doing this after all the typical diagnosis steps. So never found a solution Definitely wasn't cache or disc space related.

In the end I built the XOA from source on the same VM and that worked fine.
Although subsequent to that I've moved XOA to the containerised version thus saving an extra VM!.

andibing

I'm seeing this on XOA:

xoa@xoa:~$ sudo xoa-updater --upgrade
✖ { message: 'missing string at offset 151' }
xoa@xoa:~$

Unless the sun has got to me, I don't seen any other references to this error. And Gemini was confused too!

Any thoughts?

Andi Chandler

@andibing