I deployed Horde+UBA in UE5.5 according to this tutorial：UnrealBuildAccelerator (UBA) を利用した分散ビルドのセットアップ方法
It worked well, so I changed a computer to deploy HordeServer, but the HordeServer of this computer could not distribute tasks. The same situation occurred when I changed other computers. Only the computer where the initial deployment was successful could distribute tasks normally. There was no difference in software and hardware between these computers. How can I troubleshoot this problem?
1 Like
I am also having similar problems and I am wondering if there is something wrong with the Settings or maybe Horde+UBA has some Bug in UnrealEngine 5.5
Is there anyone else who has encountered this problem and solved it, can help to share，thanks
Official documentation has been published for 5.5. Please make sure you follow the instructions.
Has one Agent ever been able to participate in a distributed build?
If multiple PCs are available, try another PC.
Is your PC connected via LAN/wired or Wifi/wireless?
I checked both with LAN/wired connection and use a source build of this downloaded from Github, not the Launcher.
Otherwise, make sure the network ports are opend.
1 Like
Yes, when I use computer A as the service scheduling host, everything works fine, and other computers can also participate in distributed build acceleration code and shader compilation. However, when the service scheduling host is replaced by another B computer, the other collaborating computers can only be distributed to participate in the code compilation acceleration, and the shader compilation can never be carried out. All computers are connected via LAN/ wired, and the Unreal Engine uses a source code version downloaded from Github
Thank you very much for your answer, I will continue to try and carefully check the steps in the following document until it is solved
That’s a relief to hear that, both source code compilation and shader compilation are working well in the distributed case where computer A is the host. If so, then the setup you have done is correct.
If it is not working well in the case where you have changed hosts (computer B is the host), then perhaps just reviewing the setup is enough. The only thing you can do is to make sure that the correct settings are made for Host (computer B).
For example,
-
Is the Agent already registered with the Server?
This is to make sure that it is registered as an agent in the dashboard. -
Is the Ip address of the correct Server specified in BuildConfiguration.xml?
This needs to be changed to computer B.
If this does not work, try closing the UBA or Agent running on the client pc from the task tray and restarting the application. There are several other things you could try, but since you are already able to pass these on another host PC, you will be able to do so.
Thanks ! Yes, I have tried. I have been busy with work recently, so I have been delayed for some time.
On The first question “Is the Agent already registered with the Server?” yes, The Horde Agent computer is alaready reigstered whith the Server. I can see it from the IP web address, I can see each other correctly on the server and the agent machine, but I need to compile the local computer through the IP web address to see the agent machine showed " Offline - Unexpected ” , I think maybe something wrong with this step
Uploading: screen01.png…
Uploading: screen02.png…
“Offline - Unexpected” This is a good tip. This status indicates that the Horde Agent is not connected (turning off PC or closing agent application) or that the network connection is not working. Currently your agent is able to enroll to the server, so your settings server IP address is correct. It is likely that the Agent belongs to a different network than the Server, or the port is blocked by a firewall. I was recently connected to the Agent via wifi and saw this in the former case. I recommend that you first make sure that the Agent PC is on the same network as the Server.