jhart98169
commented
4 years ago Closing as I posted it in the deepracer_for_dummies github.
Closed jhart98169 closed 4 years ago
jhart98169
commented
4 years ago Closing as I posted it in the deepracer_for_dummies github.
I started with a clean Ubuntu 18.04 LTS install, and used the deepracer_for_dummies install, which ran smoothly.
But when I runs the ./start.sh script I see some errors in the logs in the robomaker logs. It seems like I am pretty close to getting this working as I do get a vncviewer window and a couple of other terminal windows.
I am running on a dell T7500 with 24 Gb memory and a geforce gtx 1070 from gigabyte with 6GB of memory, and all of the checks that were part of the install looked like then worked correctly to me. Other logs look clean as far as I can tell.
Any help getting local deepracer training running would be appreciated.
The docker log robomaker looks like this:
auto-starting new master process[master]: started with pid [876] ROS_MASTER_URI=http://localhost:11311 the rosdep view is empty: call 'sudo rosdep init' and 'rosdep update' ]2;/app/robomaker-deepracer/simulatioSpawnModel script started [INFO] [1578153836.596603, 0.000000]: Loading model XML from ros parameter [INFO] [1578153836.600068, 0.000000]: Waiting for service /gazebo/spawn_urdf_model [INFO] [1578153836.601705, 0.000000]: Calling service /gazebo/spawn_urdf_model [INFO] [1578153836.745759, 0.393000]: Spawn status: SpawnModel: Successfully spawned entity
python3 -m markov.rollout_worker /app/robomaker-deepracer/simulation_ws/install/deepracer_simulation/lib/deepracer_simulation/run_rollout_rl_agent.sh: line 8: 1569 Illegal instruction (core dumped) python3 -m markov.rollout_worker ================================================================================REQUIRED process [agent-9] has died! process has died [pid 1449, exit code 132, cmd /app/robomaker-deepracer/simulation_ws/install/deepracer_simulation/lib/deepracer_simulation/run_rollout_rl_agent.sh name:=agent log:=/root/.ros/log/cda39cbc-2f0b-11ea-a1a4-0242ac120004/agent-9.log]. log file: /root/.ros/log/cda39cbc-2f0b-11ea-a1a4-0242ac120004/agent-9*.log Initiating shutdown!
[ INFO] [1578153835.827480371]: Finished loading Gazebo ROS API Plugin. [ INFO] [1578153835.830352916]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting... [ INFO] [1578153836.270740797, 0.034000000]: waitForService: Service [/gazebo/set_physics_properties] is now available. [ INFO] [1578153836.349773497, 0.111000000]: Physics dynamic reconfigure ready. Traceback (most recent call last): .........
Then further down in the file this error
The VNC desktop is: b44e0933fcf2:0
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?
The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running:
One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
PORT=5900 [racecar/controller_manager-5] escalating to SIGTERM [gazebo-2] escalating to SIGTERM [WARN] [1578153853.995580, 1.688000]: Controller Spawner error while taking down controllers: transport error completing service call: receive_once[/racecar/controller_manager/switch_controller]: unexpected error [Errno 4] Interrupted system call [INFO] [1578153836.595853, 0.000000]: Controller Spawner: Waiting for service controller_manager/load_controller [INFO] [1578153837.804389, 0.536000]: Controller Spawner: Waiting for service controller_manager/switch_controller [INFO] [1578153837.806284, 0.538000]: Controller Spawner: Waiting for service controller_manager/unload_controller