[GUI] [Dbg] [Gui.cc:151] GUI requesting list of world names. The server may be busy downloading resources. Please be patient.

[lvmingzhe]

Hello.

When I try to launch this subt virtual environment, it get stuck at this error:

[GUI] [Dbg] [Gui.cc:151] GUI requesting list of world names. The server may be busy downloading resources. Please be patient.

sometimes it got launched after several hours waiting, but it always failed and kept looping this error..

[wolfgangschwab]

Hello,

it looks like that you are downloading the worlds every time you launch. And you might have a misspelled launch command. To help you, it would be good to have more information how you launch:

• Can you describe how you launch the subt virtual environment?
• Do you use a docker image or do you use catkin workspace?
• Can you please post the launch command you are using?

[lvmingzhe]

Hello,

it looks like that you are downloading the worlds every time you launch. And you might have a misspelled launch command. To help you, it would be good to have more information how you launch:

• Can you describe how you launch the subt virtual environment? I just follow the guidance of Docker-Setup and everything goes well before the launch operation.

• Do you use a docker image or do you use catkin workspace? I have tried them both on Ubuntu18.04.

• Can you please post the launch command you are using?

sudo ./run.bash osrf/subt-virtual-testbed competition.ign worldName:=tunnel_circuit_practice_01 circuit:=tunnel robotName1:=X1 robotConfig1:=X1_SENSOR_CONFIG_1

To solve this problem, can I pre-download some necessary installation packages to avoid downloading [list of world names] every time when launched？

It seems that this error message comes from the ign-gazebo/src/cmd/ign.cc website in Line 270-279.

Thanks for your kindly help.

[wolfgangschwab]

That sound Ok. I have two remarks to your commands.

1. Why do you use sudo? I do not use sudo and I would think that is should not be necessary.
2. I changed the run.bash script because I never solved the xauth failure. My workaround might be not the correct way, but it worked for us. So you can try to take out (erase) the following lines from the run.bash script.

   # Prevent executing "docker run" when xauth failed.
   if [ ! -f $XAUTH ]
   then
   echo "[$XAUTH] was not properly created. Exiting..."
   exit 1
   fi

[wlsdn9350]

Hi. I was also struggling with the same problem, I think it was caused by the firewall. I was able to solve my problem by disabling the firewall, but I am still not sure if a solution of allowing only specific ports or IPs while maintaining the firewall is possible.

[leng-96]

Hello, has the problem been solved? I also encountered the same problem, please give me some advice, thank you

[wlsdn9350]

@leng-96 In my case it was a firewall issue. Checking docker's inet and setting "ufw allow" solved the problem.

ifconfig
# check docker inet ex. 151.X.0.2

sudo ufw allow from 151.X.0.0/24