Problem with client after some problem on CMS hosting server

Get Help
1

Hi,
i have today problem with my hosting company. The issue at hand was due to a global conflict between the CloudLinux core and CageFS file system caused by the updating system. After hosting server back to noraml Xibo CMS is working fine .

But after hosting is back to normal my client stop probably because i made changes in layouts.After that i erase changes in layouts but did not help…

I have Android and Windows clients.

On android client log error is :Player is missing dependecies
Scheduled layouts:0
Valid Layouts : 0
Invalid layouts: “empty”

On CMs errror for android clinet is: Unable to start XMR queue: class java.lang.Exception/XMR address not configured.

On windows on clinet on CMS error log is:
6409145 2017-12-01 23:47:26 XMDSSoap4 SubmitLog XML log: 1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutLayout Change to failed. Exception raised was: Default layout1.12.2017. 12:09:37UI ThreadMainForm - ChangeToNextLayoutPrepare Layout Failed. Exception raised was: Default layout

6409144 2017-12-01 12:09:37 Client [UI Thread] MainForm - ChangeToNextLayout Prepare Layout Failed. Exception raised was: Default layout

6409143 2017-12-01 12:09:37 Client [UI Thread] MainForm - ChangeToNextLayout Layout Change to failed. Exception raised was: Default layout

Please some advise or help. I tried to verify modules ,restart clients and reconfigure displays default settings in CMS…

2

Sounds like a couple of issues. One is that each player needs to be told to update its XMR information. The other is that what the players have versus what the CMS thinks they have are different.

I would try telling each display to update it’s XMR from the CMS and also for each to clear it cache and download everything anew from the CMS.

This can be done by going to edit on each display and the advanced tab. Put a check in “Clear Cache Data” and “Reconfigure XMR”. Hit save. Then wait for the amount of time to passed that each display is set to check in at. By the time the second check in time comes around, hopefully each display will then display properly.

If that does not work. I would look at restoring a backup.

1 Like