CMS error - socket failed: EMFILE

Those errors are “normal” if you’ve got a device with intermittent connection to the CMS - this appears to be the case “Failed to connect to xxxxx”.

Under those circumstances it is expected that XMR would be unresponsive and reconfigure itself, it is also expected that calls to XMDS would fail.

That player must have re-established connection, because you’re viewing logs in the CMS, which means it has been able to dispatch those.


There is an awful lot of background to this issue, where we tried to help you guys before on a commercial basis. We couldn’t get files to download reliably on your devices, despite trying multiple things - however, exactly the same content worked well on 3 of 4 test devices we have here.

From your screenshot, it looks to me like you have the same problem again, using whichever CMS you are using now. I.e. files that are downloading constantly, because for some reason they are never received/saved on the device.

If you have an interest in continuing our previous discussion, please do feel free to re-open the ticket on our help desk.