This sounds similar to an issue we had before and which was discussed here, where our findings were also that the running image had been corrupted somehow and weston.ini was similarly empty:
This sounds similar to an issue we had before and which was discussed here, where our findings were also that the running image had been corrupted somehow and weston.ini was similarly empty: