[SOLVED] NRP Source install , on new experiment get the error : No server can handle your simulation at the moment. Please try again later


#1

I have tried fresh install of Neurorobotics platform. On starting a new experiment I get the error message, No server can handle your simulation at the moment. Please try again later.

in the command line I get the error,

2020-12-28 10:44:39 GMT+0530 Parsing experiment file /home/deadshot/Documents/NRP/Experiments/whiskeye_experiment/ExDWhiskeyeExperiment.exc
2020-12-28 10:44:39 GMT+0530 Parsing experiment file /home/deadshot/Documents/NRP/Experiments/zip_robot/ExDXMLExampleRobotZip.exc
2020-12-28 10:45:23+0530 [-] [INFO] [1609132523.054776, 0.000000]: Client connected. 1 clients total.
2020-12-28 10:45:23,245 [uWSGIWorker1] [hbp_nrp_back] [INFO] Requesting simulation resources
2020-12-28 10:45:23,245 [uWSGIWorker1] [hbp_nrp_back] [INFO] simulation timeout initialized
2020-12-28 10:45:23+0530 [-] [INFO] [1609132523.438487, 0.000000]: [Client 0] Subscribed to /ros_cle_simulation/status
2020-12-28 10:45:43,476 [uWSGIWorker1] [hbp_nrp_back] [INFO] State machine outcomes:
2020-12-28 10:45:44,483 [uWSGIWorker1] [hbp_nrp_back] [ERROR] “Error while communicating with the CLE (‘timeout exceeded while waiting for service /ros_cle_simulation/create_new_simulation’)” (CLE error)
Traceback (most recent call last):
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/flask/app.py”, line 1950, in full_dispatch_request
rv = self.dispatch_request()
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/flask/app.py”, line 1936, in dispatch_request
return self.view_functionsrule.endpoint
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/flask_restful/init.py”, line 468, in wrapper
resp = resource(*args, **kwargs)
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/flask/views.py”, line 89, in view
return self.dispatch_request(*args, **kwargs)
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/flask_restful/init.py”, line 583, in dispatch_request
resp = meth(*args, **kwargs)
File “./hbp_nrp_backend/rest_server/__SimulationService.py”, line 189, in post
sim.state = “initialized”
File “./hbp_nrp_backend/simulation_control/__Simulation.py”, line 269, in state
self.__lifecycle.accept_command(new_state)
File “/home/deadshot/Documents/NRP/ExDBackend/hbp_nrp_commons/hbp_nrp_commons/simulation_lifecycle.py”, line 181, in accept_command
self.__machine.events[command].trigger()
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/transitions/extensions/locking.py”, line 22, in trigger
super(LockedEvent, self).trigger(*args, **kwargs)
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/transitions/core.py”, line 222, in trigger
return self.machine.process(f)
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/transitions/extensions/locking.py”, line 15, in call
return self.func(*args, **kwargs)
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/transitions/core.py”, line 526, in process
return trigger()
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/transitions/core.py”, line 247, in _trigger
if t.execute(event):
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/transitions/core.py”, line 145, in execute
machine.callback(func, event_data)
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/transitions/extensions/locking.py”, line 15, in call
return self.func(*args, **kwargs)
File “/home/deadshot/.opt/platform_venv/lib/python2.7/site-packages/transitions/core.py”, line 516, in callback
func(event_data)
File “./hbp_nrp_backend/simulation_control/__BackendSimulationLifecycle.py”, line 214, in initialize
“CLE error”)

NRPServicesGeneralException: “Error while communicating with the CLE (‘timeout exceeded while waiting for service /ros_cle_simulation/create_new_simulation’)” (CLE error)

Please guide me to get this up and running.


#2

Dear patilmandarm,

It seems like either your “CLE” (a part of the NRP) or roscore is not running properly. Do you have other error messages before that one?
The correct roscore launch should output this:

Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://127.0.0.1:43637/
ros_comm version 1.14.10


SUMMARY
========

PARAMETERS
 * /rosdistro: melodic
 * /rosversion: 1.14.10

NODES

auto-starting new master
process[master]: started with pid [14833]
ROS_MASTER_URI=http://127.0.0.1:11311/

setting /run_id to e3610786-48f2-11eb-81be-e4a7a08e388e
process[rosout-1]: started with pid [14844]
started core service [/rosout]