Hello,
We are experiencing a critical issue affecting all our Xibo Android displays after restoring the CMS from backup. Initially, XMR was not running due to a missing configuration file. We recreated config.json, resolved port conflicts, and configured XMR as a systemd service. Currently XMR is running correctly, ports 9505 and 5555 are listening, and communication between CMS and players is working.
Displays connect properly and initially show content, but after 10 to 60 minutes all screens turn black showing only the Xibo logo. This affects all displays simultaneously.
In the logs we consistently see errors indicating that the next layout cannot be set because the schedule is invalid and also messages about non existing version set on displayId.
We performed multiple tests. Complex layouts with videos fail after some time. Simple layouts with image and clock also fail. Even a minimal layout with a single image fails after around 10 minutes. This indicates the issue is not related to layout complexity or media.
All TVs behave the same, network connectivity is correct, and players check in normally, so this does not appear to be device specific. The CMS is accessible and layouts can be edited and previewed. Reassigning layouts and forcing updates temporarily restores content, but the issue reappears without changes.
At this point XMR and connectivity are confirmed working, but after some time players consider layouts invalid and stop rendering them.
We suspect a global CMS inconsistency after the restore, possibly related to schedule validation, layout version mismatch, or display state inconsistency.
We would appreciate guidance on the root cause of the schedule invalid error, the meaning of the version error on displayId, and recommended steps to rebuild or re synchronize the CMS after a restore.
This issue is currently impacting all production displays. Please let us know if additional logs or diagnostics are needed.
Thank you.