Hello.
I want to use the xmr.
You have stumbled on the following error.
・(xibo-player log) “Agent threads/XMR is dead not updating status.json”
・("$php xmr.phar") “Failed to bind the ZMQ: No such device”
I checked all the writes here for both errors, but I couldn’t find a solution.
The following environment is used:
・cms -2.2 .1
・player-v2 (201)
I have already read and set all the pages you indicated.
After that, I was looking around for the above error, but I couldn’t get any information.
(Many topic was closed before resolution.)
My current settings are as follows.
(Replaced localhost with 127.0.0.1.)
That would mean your tcp://{my _ ip}:9505 port cannot be bound to, because the port is already open and used by something else. You can try to find out what that other thing is, and stop it, or change the port number XMR tries to bind to.
To summarise… XMR sits there and publishes messages on the port you’ve configured as pubOn, and it can’t bind to that address you’ve given.
After the above, I reviewed the settings.
The error that caused xmr to fail to start up was that httpd had access to these ports.
I thought it necessary to open up httpd’s port 50001 (listenOn) and port 9505 (pubOn), but it was not necessary.
After starting xmr, I performed the following three operations from the CMS to verify operation.
・CollectNow
・ScreenShot
・Changing a running schedule
There operations were performed immediately without waiting for the collection interval.
The points I want to ask are as follows.
(1)Is xmr working properly?
(2)The player status still shows the following error:. Am I missing something?
[ScheduleManagerThread] “Agent threads/XMR is dead not updating status.json”
Sorry for asking so many questions.
I look forward to hearing from you.
The logs imply XMR is working correctly, you can see heartbeat messages every 30 seconds and the messages you sent going out also (the ones logged as INFO).
If you open the player information window, what do you see as the XMR status (above the error log grid)?
You should see the address you’ve entered as your pubOn listed there, and showing as connected. You should also see a last message date.
The error occurred again when I restarted the player this morning.
I checked the source and found a condition that caused this error.
It appears to occur when one of the following five threads does not exist.
That is indeed when the message gets logged, but usually the culprit here is the XMR subscriber thread as the others are basically wait/poll threads for making API requests.
The XMR thread is the only one there making a permanent socket connection.
You’re looking in the wrong repository by the way, the code for your player version is here.
This is the XMR run loop:
Its not uncommon to get disconnects and errors in there, which is why all the logging is marked as either audit/info.
I suggest you lower your logging level in Display Settings and see if anything else gets logged.
Now I know why xmr can be used when it has errors.
The console log screen of the player shows the information of all the logs, so even if there is no problem now, it shows the errors in the past. I see.