Clients not stable after moving from 1.6.4 to 1.7.5

Get Help Xibo Player for Android
1

Hi,

We’ve recently upgraded our xibo CMS from 1.6.4 to 1.7.4.

Just to give a little insight we’re running CMS from local IIS server with 30+ android clients.

We have players running across 4 different geographic sites and one of the site is not stable since we’ve moved displays from 1.6.4 to 1.7.5.

Sometime clients will lose connection to CMS and wont connect until we restart xibo player.

Current player version is R56.

please find the log from one of players.

7512	2016-02-10 05:18:45	Client	DisplayManager	Unable to StartNextLayout: Layout wont start: null
7126	2016-02-09 14:28:14	Client	ScheduleManager	Unexpected end of document
7072	2016-02-09 11:45:20	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
7064	2016-02-09 11:35:20	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
7061	2016-02-09 11:30:20	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
6893	2016-02-09 04:32:04	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
6879	2016-02-09 03:49:45	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
6817	2016-02-09 00:32:14	Client	ScheduleManager	Unexpected end of document
6816	2016-02-09 00:31:54	Client	ScheduleManager	Unexpected end of document
6625	2016-02-08 15:40:57	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
6588	2016-02-08 15:36:38	Client	Register	Error in Register: null
4523	2016-02-05 18:51:21	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
4375	2016-02-05 16:27:07	Client	ScheduleManager	Unexpected end of document
4374	2016-02-05 16:26:49	Client	ScheduleManager	Unexpected end of document
3752	2016-02-05 12:20:54	Client	ScheduleManager	Unexpected end of document
3649	2016-02-05 10:42:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
3634	2016-02-05 10:32:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
3630	2016-02-05 10:22:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
3629	2016-02-05 10:17:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
3628	2016-02-05 10:12:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
3627	2016-02-05 10:07:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
3626	2016-02-05 10:02:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
3625	2016-02-05 09:57:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)
3598	2016-02-05 09:47:52	Client	Register	Error in Register: sendto failed: ECONNRESET (Connection reset by peer)

Any help would be appreciated.

Thanks

2

The logs would seem to indicate that the web server is intermittently dropping connections - which is very strange as you wouldn’t have expected that to change between versions.

Have you upgraded the Android player version too? Or is that the same as it was when connection to 1.6?

3

Thanks for the quick response @dan .

We have so far only moved 2 sites across to 1.7 and rest are still running with 1.6 but we are slowly transferring every site to 1.7.

Out of two 1.7 sites, one of the site has 6 clients running much older R52 client which is very stable but the site running R56 (6 clients) is the one having connection issues.

To answer your question we have not updated the client versions and the worst offender so far is R56.

Thank you

4

R54 is 8 months old now and while i’ve gone through the changes between then and now and think that the communication protocols are broadly the same, I can’t be sure if the underlying android SDK has changed anything (because that has been updated a few times during those 8 months).

If you haven’t updated the players between upgrade then I think we are looking at something CMS side causing the problem. Once they realised they were connecting to a 1.7 CMS they would have switched over to using the additional calls available in that service (XMDS version 4). I.e. they would have started taking screenshots (if that were configured) and would have started using the configuration from the CMS Display Settings Profile.

The best suggestion I have is to try with the latest R59 on one of the offending players.

After thought, I think this might be due to the CMS web server being overloaded. Do you have a way of checking this?

5

have the same, started last month, did see it at first