Hard to Keep Players Running 1.8.1 - R101

Developer Experience
1

Since changing to R101 and using CMS 1.8.1 it has been very hard to keep players running. We are constantly needing to manually clear the players cache and reconfigure the XMR key. Our players stop showing our main layout twice a day. Also the options to send commands to the players are ignored.

Here is the log from one of the players:

2017-04-29 11:32:13 - ERROR - Unable to report media inventory: handshake error: ssl=0x96f19968: I/O error during system call, Bad file number
2017-04-29 08:52:21 - ERROR - XMR unresponsive, issue reconfigure.
2017-04-29 08:47:21 - ERROR - XMR unresponsive, issue reconfigure.
2017-04-29 08:02:19 - ERROR - XMR unresponsive, issue reconfigure.
2017-04-29 07:57:18 - ERROR - XMR unresponsive, issue reconfigure.
2017-04-29 07:20:01 - ERROR - XMR unresponsive, issue reconfigure.
2017-04-29 07:15:01 - ERROR - XMR unresponsive, issue reconfigure.
2017-04-29 01:45:01 - ERROR - XMR unresponsive, issue reconfigure.
2017-04-29 01:36:59 - ERROR - XMR unresponsive, issue reconfigure.
2017-04-28 23:45:01 - ERROR - XMR unresponsive, issue reconfigure.

We have no idea why the players stop playing the main layout, as nothing seems to be logged to say anything else. I will turn on auditing for one of the displays and see what we get back.

Untitled.png1692×963 88 KB

So far nothing in the Audit logs show any errors. I can privately share those if needed. Generating about 1300 log entries in 5 minutes.

We removed a layout that contained two forecast.io widgets on two different regions. This along with a overlay layout were displaying fine. However when we removed the layout with forecast.io, our main layout began to play fine. Still we see no errors about playing the layout in the CMS log or on the displays.

We will continue to monitor the problem, but we are not sure were to look for the problem. As it stands right now it looks like some issue with the forecast.io module and widgets.

2

We have one display that we letf the layout with the forecast.io on. It seemingly is showing everything, but we see this in the logs:

6180	2017-04-29 12:25	Unable to open message: class javax.crypto.IllegalBlockSizeException/null
6092	2017-04-29 12:06	Unable to open message: class javax.crypto.BadPaddingException/error:0407106B:rsa routines:RSA_padding_check_PKCS1_type_2:block type is not 02
6091	2017-04-29 12:01	Unable to open message: class javax.crypto.BadPaddingException/error:0407106B:rsa routines:RSA_padding_check_PKCS1_type_2:block type is not 02
693	2017-04-29 00:03	Unable to open message: class javax.crypto.BadPaddingException/error:0407106B:rsa routines:RSA_padding_check_PKCS1_type_2:block type is not 02

No idea why things play on this unit, but apparently with some errors. The unit is a different model unit than the other 3 we are seeing this on. They are running the same Android version and are configured the same.

3

We’re investigating an issue with some devices not storing their crypto keys properly currently. What devices are these?

If the device can’t retain that key, then XMR communications can’t work as the key will change on the Player side, and then won’t match the public key held by the CMS. The CMS won’t accept a new public key unless you specifically authorise it to do so (by rekeying).

4

Hi Alex,

Sorry for the late reply, seems I missed this one. The Devices are RikoMagic 902II/16GB, Android 5.1.1.