XMR bug causes the android player to close itself

Get Help
1

XMR bug causes the android player to close itself.

After a few minutes the player is closed,
In the log, the message displayed is:

“Unable to start XMR queue: class java.lang.Exception / XMR address not configured.”

After a few minutes the player starts automatically, but then restarts itself after a few minutes, and keeps repeating it every 5/6 minutes.

This occurred in the configuration:
Android Player 1.8
Cms 1.7 manually installed.
Shared hosting.

After updating cms to 1.8.1 the player has stopped rebooting, but error messages continue to appear in the log.

Can I disable these XMR connection attempts? Since I will not use them since I can not install ZeroQM.

2

You should probably use 1.7 R63 with 1.7.9 CMS.

1.8 player’s features are available only if it’s connected to 1.8 cms.

In your case, with shared hosting, even if you’d install 1.8 CMS, you will most likely not be able to configure and run XMR, as shared hosting aren’t really suitable for Xibo, for 1.8 series even less so.

3

Ok, but I do not care about XMR, can I use the 1.8 android and cms and ignore these error messages?

Or if I leave like this at some point something bad can happen, such as the log getting too big, etc?

Is there a way to disable this log for these XMR-related messages?

4

You can do that, it shouldn’t affect normal player functionalities, just the screenshots, send commands etc will not work.

I don’t think so, player will try to do that, so it will log the errors.

5

Stupid question.

01 - Since the error is for not having the XMR address set, would not it be the case for me to set an address in the Public address field? Would not that make the mistake go away?

02 - Just out of curiosity, what addresses would I put in public and private addresses if I was using Docker correctly? I was unable to find instructions on these addresses in the manual.

Would it be the ip address of my server? Or the domain I use to access my xibo system?

6

Private should be

tcp://xmr:50001

Public should be the DNS name or IP address that you access the CMS at (as the Player sees it)

tcp://name:9505 or tcp://ip.address:9505

It shouldn’t show that it’s not configured anymore, but it might show other errors related to the fact that you know it’s not there and not running.

7

In the “Troubleshooting” options under

“Resting Log Level” and “Log” are there any options that I can define
So that the logs are completely disabled?

8

They refer to the CMS logs. You can change the Player log level from the Display Settings Profile. “Off” will stop any logs being sent to the CMS.

9

Thanks, this work for now :smiley: