You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into this situation today while I was imagining my new "cloud game cluster", this cluster consists of 9 nodes and all of them are running the same sunshine installation. All are going fine with 1 node up and connect to Moonlight with no problem, but things are going strange when I bring 2 or more node up.
Backstory and setup:
Moonlight is recognizing all the nodes in the network with mDNS correctly but only one random node will show up. Looked into the log files and found moonlight is classifying each machine with their uid(uniqueid) connected to sunshine, doesn't uniquely recognize computer's host name like other LAN control programs like Veyon.
All nodes are running off iSCSI boot and all change made to the node will be lost after a reboot.
So here's my workaround with UIDs:
All the nodes are set to automatically logged in when booted up, so I wrote a simple python script to parse the sunshine_state.json, find the root.uniqueid field and change the last character of the UUID to be the node number (0-9) when the default user is logged in, the script will then start the sunshine service and that way, the new uniqueid can be used "uniquely identified" all the imaged node.
This setup is running fine, but I wonder if anyone has tried this and their solution to this unique problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I ran into this situation today while I was imagining my new "cloud game cluster", this cluster consists of 9 nodes and all of them are running the same sunshine installation. All are going fine with 1 node up and connect to Moonlight with no problem, but things are going strange when I bring 2 or more node up.
Backstory and setup:
Moonlight is recognizing all the nodes in the network with mDNS correctly but only one random node will show up. Looked into the log files and found moonlight is classifying each machine with their uid(uniqueid) connected to sunshine, doesn't uniquely recognize computer's host name like other LAN control programs like Veyon.
All nodes are running off iSCSI boot and all change made to the node will be lost after a reboot.
So here's my workaround with UIDs:
All the nodes are set to automatically logged in when booted up, so I wrote a simple python script to parse the
sunshine_state.json
, find the root.uniqueid field and change the last character of the UUID to be the node number (0-9) when the default user is logged in, the script will then start the sunshine service and that way, the new uniqueid can be used "uniquely identified" all the imaged node.This setup is running fine, but I wonder if anyone has tried this and their solution to this unique problem.
Beta Was this translation helpful? Give feedback.
All reactions