search

osrf / subt

This repostory contains software for the virtual track of the DARPA SubT Challenge. Within this repository you will find Gazebo simulation assets, ROS interfaces, support scripts and plugins, and documentation needed to compete in the SubT Virtual Challenge.
Other
309 stars 97 forks source link

Having trouble with nvidia driver #96

Closed osrf-migration closed 5 years ago

osrf-migration commented 5 years ago

Original report (archived issue) by baila (Bitbucket: baila).

Hey all,

After trying to rectify the errors several times, I tried to do the whole docker setup from the beginning. I am at the stage of

docker run --runtime=nvidia --rm nvidia/cuda:9.0-base nvidia-smi

All the layers downloaded and extracted properly. But got the below error like,

baila@baila-PC:~$ docker run --runtime=nvidia --rm nvidia/cuda nvidia-smi
docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused "process_linux.go:413: running prestart hook 1 caused \"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/bin/nvidia-container-cli --load-kmods configure --ldconfig=@/sbin/ldconfig.real --device=all --compute --utility --require=cuda>=10.1 brand=tesla,driver>=384,driver<385 brand=tesla,driver>=396,driver<397 brand=tesla,driver>=410,driver<411 --pid=3101 /var/lib/docker/overlay2/eedc1522da24fb7971e5ce9676212a4ce2dbe1469edc5dfecd108a12406b1155/merged]\\nnvidia-container-cli: requirement error: unsatisfied condition: brand = tesla\\n\""": unknown.
baila@baila-PC:~$

I tried to follow the next steps of troubleshooting, seems

baila@baila-PC:~$ sudo apt-get install nvidia-384

[sudo] password for baila:

Reading package lists... Done

Building dependency tree

Reading state information... Done

nvidia-384 is already the newest version (390.116-0ubuntu0.18.04.1).

0 upgraded, 0 newly installed, 0 to remove and 25 not upgraded.

baila@baila-PC:~$

‌

Any help how to fix the problem? I have the below nvidia driver in use,

My questions are,

  1. Will it work?
  2. Can I continue further if the problem couldn’t be resolved?

Please help me, I am stuck badly.

osrf-migration commented 5 years ago

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

The following issue looks relevant: https://github.com/NVIDIA/nvidia-docker/issues/861

What nvidia card do you have?

And you have followed these instructions, correct?

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Yes, I have used that Docker link only. Last I tried,

docker run --runtime=nvidia --rm nvidia/cuda:9.0-base nvidia-smi

I will try with,

docker run --runtime=nvidia --rm nvidia/cuda:9.0-runtime nvidia-smi

as per suggested to the issue you have mentioned above.

‌

Thanks a lot for your response. I will post my findings once done.

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

I think the nvidia/cuda:9.0-runtime solved the problem, able to run it successfully,

baila@baila-PC:~$ docker run --runtime=nvidia --rm nvidia/cuda:9.0-runtime nvidia-smi
Unable to find image 'nvidia/cuda:9.0-runtime' locally
9.0-runtime: Pulling from nvidia/cuda
35b42117c431: Pull complete
ad9c569a8d98: Pull complete
293b44f45162: Pull complete
0c175077525d: Pull complete
695112388c71: Pull complete
a911faa54767: Pull complete
ae34ac42e04c: Pull complete
9894e655955e: Pull complete
Digest: sha256:2966b2527e916074231de9a9f549d51d3e671b907f44a779526fff49aaf091e4
Status: Downloaded newer image for nvidia/cuda:9.0-runtime
Wed Jul 3 17:13:26 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.116 Driver Version: 390.116 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GT 520M Off | a527ae8c41762a101acbf2474382f82acd977df2:01:00.0 N/A | N/A |
| N/A 45C P0 N/A / N/A | 142MiB / 964MiB | N/A Default |
+-------------------------------+----------------------+----------------------+
` +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | 0 Not Supported | +-----------------------------------------------------------------------------+ baila@baila-PC:~$`

‌

But is it enough to proceed further?

osrf-migration commented 5 years ago

Original comment by Alfredo Bencomo (Bitbucket: bencomo).

osrf-migration commented 5 years ago

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

That looks okay. Can you try running simulation?

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Hey Nate Koenig (Nathan Koenig) ,

I did the complete docker install freshly. But still not able to spawn the robots. I ran ign launch -v 4 competition.ign robotName1:=X1 robotConfig1:=X2_SENSOR_CONFIG_1 robotName2:=X2 robotConfig2:=X2_SENSOR_CONFIG_1 right after installation. I got the below issues,

1.

Failed to create a bridge for topic [/model/X2/odometry] with ROS1 type [nav_msgs/Odometry] and Ignition Transport type [ignition.msgs.Odometry]
process[X1/ros1_ign_bridge_odom-3]: started with pid [268]
Failed to create a bridge for topic [/model/X1/odometry] with ROS1 type [nav_msgs/Odometry] and Ignition Transport type [ignition.msgs.Odometry]

‌

2.

Failed to create a bridge for topic [/world/tunnel_qual_ign/model/X2/link/base_link/sensor/camera_front/camera_info] with ROS1 type [sensor_msgs/CameraInfo] and Ignition Transport type [ignition.msgs.CameraInfo]
process[X1/ros1_ign_bridge_camera-6]: started with pid [346]
Failed to create a bridge for topic [/world/tunnel_qual_ign/model/X1/link/base_link/sensor/camera_front/camera_info] with ROS1 type [sensor_msgs/CameraInfo] and Ignition Transport type [ignition.msgs.CameraInfo]

3.

Failed to create a bridge for topic [/world/tunnel_qual_ign/model/X2/link/base_link/sensor/air_pressure/air_pressure] with ROS1 type [sensor_msgs/FluidPressure] and Ignition Transport type [ignition.msgs.FluidPressure]
Failed to create a bridge for topic [/world/tunnel_qual_ign/model/X1/link/base_link/sensor/air_pressure/air_pressure] with ROS1 type [sensor_msgs/FluidPressure] and Ignition Transport type [ignition.msgs.FluidPressure]

4.

[Dbg] [GazeboFactory.cc:140] Factory service call succeeded.
Topic [] is not valid.
[Err] [SensorFactory.cc:129] Sensor::Load failed for plugin [ignition-sensors2-camera]
[Err] [Sensors.cc:127] Failed to create sensor [X1::base_link::camera_front]
/usr/lib/ruby/ignition/cmdlaunch1.rb:202: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]

‌

5.

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

Aborted (core dumped)
developer@baila-PC:~/subt_ws$ [GUI] [Dbg] [Application.cc:130] Terminating application.
[GUI] [Dbg] [Scene3D.cc:469] Destroy scene [scene]

‌

The above 5 points are the several errors during the run. Please suggest what to do next to fix this.

osrf-migration commented 5 years ago

Original comment by Malcolm Stagg (Bitbucket: malcolmst7).

If it helps at all, I believe I may have hit this same issue. For me, the relevant stack trace seemed to be:

/usr/lib/ruby/ignition/cmdlaunch1.rb:202: [BUG] Segmentation fault at 0x00000000000002a8
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]

-- Control frame information -----------------------------------------------
c:0005 p:---- s:0044 e:000043 CFUNC  :call
c:0004 p:0017 s:0039 e:000038 METHOD /usr/lib/ruby/ignition/cmdlaunch1.rb:202
c:0003 p:0446 s:0033 e:000032 METHOD /usr/lib/ruby/ignition/cmdlaunch1.rb:202
c:0002 p:0628 s:0019 E:002208 EVAL   /usr/bin/ign:267 [FINISH]
c:0001 p:0000 s:0003 E:000360 (none) [FINISH]

-- Ruby level backtrace information ----------------------------------------
/usr/bin/ign:267:in `<main>'
/usr/lib/ruby/ignition/cmdlaunch1.rb:202:in `execute'
/usr/lib/ruby/ignition/cmdlaunch1.rb:202:in `run'
/usr/lib/ruby/ignition/cmdlaunch1.rb:202:in `call'

-- Machine register context ------------------------------------------------
 RIP: 0x00007fb86c777940 RBP: 0x00007fb848050f90 RSP: 0x00007fb86eea3150
 RAX: 0x0000000000000000 RBX: 0x00007fb848078580 RCX: 0x0000000000000040
 RDX: 0x0000000000000000 RDI: 0x00007fb848078580 RSI: 0x00007fb848050f90
  R8: 0x0000000000000004  R9: 0x0000000000000000 R10: 0x000000000000003d
 R11: 0x00007fb86c7ff820 R12: 0x00007fb848078210 R13: 0x00007fb848078580
 R14: 0x00007fb84801c3a0 R15: 0x00007fb86eea33b0 EFL: 0x0000000000010246

-- C level backtrace information -------------------------------------------
/usr/lib/x86_64-linux-gnu/libruby-2.5.so.2.5(0x7fb8bea77965) [0x7fb8bea77965]
/usr/lib/x86_64-linux-gnu/libruby-2.5.so.2.5(0x7fb8bea77b9c) [0x7fb8bea77b9c]
/usr/lib/x86_64-linux-gnu/libruby-2.5.so.2.5(0x7fb8be941884) [0x7fb8be941884]
/usr/lib/x86_64-linux-gnu/libruby-2.5.so.2.5(0x7fb8bea079a2) [0x7fb8bea079a2]
/lib/x86_64-linux-gnu/libc.so.6(0x7fb8be507f20) [0x7fb8be507f20]
/usr/lib/x86_64-linux-gnu/libOgreMain.so.2.1.0(_ZN4Ogre15ConstBufferPool19_changeRenderSystemEPNS_12RenderSystemE+0x60) [0x7fb86c777940]
/usr/lib/x86_64-linux-gnu/libOgreHlmsUnlit.so.2.1.0(_ZN4Ogre9HlmsUnlit19_changeRenderSystemEPNS_12RenderSystemE+0x3a) [0x7fb86c19f1aa]
/usr/lib/x86_64-linux-gnu/libOgreMain.so.2.1.0(_ZN4Ogre11HlmsManager12registerHlmsEPNS_4HlmsEb+0x59) [0x7fb86c7ff879]
...

This was on a machine where I had the Nvidia drivers installed but without OpenGL support. Reinstalling the drivers with OpenGL support enabled resolved the issue for me on that machine.

However, I have another machine where I am unable to install the Nvidia drivers with OpenGL support due to a login loop/black screen issue (and I am kind of stuck with using one specific driver version due to some other unrelated dependencies on that machine), and I haven’t found a solution yet that works on that machine.

…

osrf-migration commented 5 years ago

Original comment by Malcolm Stagg (Bitbucket: malcolmst7).

BTW, you can check your OpenGL renderer to see if this might be the same problem, using:

glxinfo | grep -e "OpenGL vendor" -e "OpenGL renderer"

Both of these machines have both an Nvidia GPU and Intel integrated graphics. The machine that still has a problem displays:

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2)

The machine where the problem is resolved displays:

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1080/PCIe/SSE2
osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Malcolm Stagg (malcolmst7) , I think I have the drivers,

‌

baila@baila-PC:~/subt_docker$ glxinfo | grep -e "OpenGL vendor" -e "OpenGL renderer"
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 520M/PCIe/SSE2
baila@baila-PC:~/subt_docker$

‌

Any clue further?

osrf-migration commented 5 years ago

Original comment by Malcolm Stagg (Bitbucket: malcolmst7).

Hmm sorry, sounds like a different issue maybe. Out of curiosity, does the ignition window stay open or close for you (it closes immediately in my case), and do you see a stack trace like I was seeing? Mine was printed pretty soon after the ign launch.

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

The window remains there also the tunnels are coming there. But no robot and that core dumped.

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Hey Nate Koenig (Nathan Koenig) , any clue to resolve this issue? I am completely blocked with my setup. :(

osrf-migration commented 5 years ago

Original comment by Alfredo Bencomo (Bitbucket: bencomo).

baila (baila) The Docker files were recently updated to install the new required ros-melodic-ros1-ign bridge (PR #183). You need it for the CameraInfo and others to work. You can either get the latest one or run the command below inside your docker container. Then, try running simulation again.

sudo apt-get install -y ros-melodic-ros1-ign && sudo apt-get clean

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Sure, I will check that and post the update. I remember of doing install of ros-melodic-ros1-ign package earlier, it showed me no such package available. Is there any such issue?

osrf-migration commented 5 years ago

Original comment by Alfredo Bencomo (Bitbucket: bencomo).

You should be able to install it now.

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Hi Alfredo Bencomo (bencomo) , I tried the installation, found the below issue,

‌

baila@baila-PC:~/subt_docker$ ./run.bash subt
xauth: /tmp/.docker.xauth not writable, changes will be ignored
xauth: (argv):1: unable to read any entries from file "(stdin)"
chmod: changing permissions of '/tmp/.docker.xauth': Operation not permitted
developer@baila-PC:~/subt_ws$ sudo apt-get install -y ros-melodic-ros1-ign && sudo apt-get clean
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ros-melodic-ros1-ign

Updated then,
developer@baila-PC:~/subt_ws$ sudo apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://packages.osrfoundation.org/gazebo/ubuntu-stable bionic InRelease [4267 B]
Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:4 http://packages.ros.org/ros/ubuntu bionic InRelease [4669 B]
Get:5 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:6 http://packages.osrfoundation.org/gazebo/ubuntu-stable bionic/main amd64 Packages [44.2 kB]
Get:7 http://packages.ros.org/ros/ubuntu bionic/main amd64 Packages [503 kB]
Get:8 http://security.ubuntu.com/ubuntu bionic-security/universe i386 Packages [712 kB]
Get:9 http://packages.osrfoundation.org/gazebo/ubuntu-stable bionic/main i386 Packages [41.7 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [723 kB]
Get:12 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages [432 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1239 kB]
Ign:14 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages
Get:15 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [576 kB]
Get:14 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [721 kB]
Ign:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [1218 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [884 kB]
Fetched 7356 kB in 5min 9s (23.8 kB/s)
Reading package lists... Done

Tried installation again,
developer@baila-PC:~/subt_ws$ sudo apt-get install -y ros-melodic-ros1-ign && sudo apt-get clean
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
ros-melodic-ros1-ign-bridge ros-melodic-ros1-ign-gazebo-demos ros-melodic-ros1-ign-point-cloud
The following NEW packages will be installed:
ros-melodic-ros1-ign ros-melodic-ros1-ign-bridge ros-melodic-ros1-ign-gazebo-demos ros-melodic-ros1-ign-point-cloud
0 upgraded, 4 newly installed, 0 to remove and 122 not upgraded.
Need to get 216 kB of archives.
After this operation, 1619 kB of additional disk space will be used.
Get:1 http://packages.osrfoundation.org/gazebo/ubuntu-stable bionic/main amd64 ros-melodic-ros1-ign-bridge amd64 0.3.1-1bionic [147 kB]
Get:2 http://packages.osrfoundation.org/gazebo/ubuntu-stable bionic/main amd64 ros-melodic-ros1-ign-point-cloud amd64 0.3.1-1bionic [56.9 kB]
Get:3 http://packages.osrfoundation.org/gazebo/ubuntu-stable bionic/main amd64 ros-melodic-ros1-ign-gazebo-demos amd64 0.3.1-1bionic [9280 B]
Get:4 http://packages.osrfoundation.org/gazebo/ubuntu-stable bionic/main amd64 ros-melodic-ros1-ign amd64 0.3.1-1bionic [2168 B]
Fetched 216 kB in 59s (3667 B/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package ros-melodic-ros1-ign-bridge.
(Reading database ... 118780 files and directories currently installed.)
Preparing to unpack .../ros-melodic-ros1-ign-bridge_0.3.1-1bionic_amd64.deb ...
Unpacking ros-melodic-ros1-ign-bridge (0.3.1-1bionic) ...
dpkg: error processing archive /var/cache/apt/archives/ros-melodic-ros1-ign-bridge_0.3.1-1bionic_amd64.deb (--unpack):
trying to overwrite '/opt/ros/melodic/lib/pkgconfig/ros1_ign_bridge.pc', which is also in package ros1-ign-bridge 0.2.2-1~bionic
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package ros-melodic-ros1-ign-point-cloud.
Preparing to unpack .../ros-melodic-ros1-ign-point-cloud_0.3.1-1bionic_amd64.deb ...
Unpacking ros-melodic-ros1-ign-point-cloud (0.3.1-1bionic) ...
Selecting previously unselected package ros-melodic-ros1-ign-gazebo-demos.
Preparing to unpack .../ros-melodic-ros1-ign-gazebo-demos_0.3.1-1bionic_amd64.deb ...
Unpacking ros-melodic-ros1-ign-gazebo-demos (0.3.1-1bionic) ...
Selecting previously unselected package ros-melodic-ros1-ign.
Preparing to unpack .../ros-melodic-ros1-ign_0.3.1-1bionic_amd64.deb ...
Unpacking ros-melodic-ros1-ign (0.3.1-1bionic) ...
Errors were encountered while processing:
/var/cache/apt/archives/ros-melodic-ros1-ign-bridge_0.3.1-1bionic_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
developer@baila-PC:~/subt_ws$

‌

Any clue?

osrf-migration commented 5 years ago

Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero).

Hello:

I think that the problem with the package installation is here:

Unpacking ros-melodic-ros1-ign-bridge (0.3.1-1bionic) ...
dpkg: error processing archive /var/cache/apt/archives/ros-melodic-ros1-ign-bridge_0.3.1-1bionic_amd64.deb (--unpack):
trying to overwrite '/opt/ros/melodic/lib/pkgconfig/ros1_ign_bridge.pc', which is also in package ros1-ign-bridge 0.2.2-1~bionic
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

The bridge was previously packaged as ros1-ign-bridge but changed the name to ros-melodic-ros1-ign-bridge in the last release and the upgrade is not being handled automatically. I can patch the packaging to do it properly but meanwhile a workaround could be to use:

sudo dpkg -r ros1-ign-bridge && apt-get install -f

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Thanks Jose Luis Rivero (Jose Luis Rivero) , your solution solved my issue. So I am able to run the simulation. But encountered new error,

developer@baila-PC:~/subt_ws$ ign launch -v 4 competition.ign robotName1:=X1 robotConfig1:=X2_SENSOR_CONFIG_1
[Dbg] [Manager.cc:406] Forked a process for [ros] command[roslaunchsubt_roscompetition_init.launchworld_name:=tunnel_qual_ignvehicle_topics:=0]
[Dbg] [Manager.cc:406] Forked a process for [x2_description] command[roslaunch--waitsubt_rosx2_description.launchworld_name:=tunnel_qual_ignname:=X1]
[Dbg] [Manager.cc:406] Forked a process for [x2_ros_ign_bridge] command[roslaunch--waitsubt_rosvehicle_topics.launchworld_name:=tunnel_qual_ignname:=X1]
.

.

.

process[ros1_ign_bridge_baila_PC_499_3030296628978868002-2]: started with pid [567]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[ros1_ign_bridge_baila_PC_499_3030296628978868002-2] process has died [pid 567, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /world/tunnel_qual_ign/clock@rosgraph_msgs/Clock@ignition.msgs.Clock /world/tunnel_qual_ign/clock:=/clock __name:=ros1_ign_bridge_baila_PC_499_3030296628978868002 __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/ros1_ign_bridge_baila_PC_499_3030296628978868002-2.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/ros1_ign_bridge_baila_PC_499_3030296628978868002-2*.log
started roslaunch server [http://baila-PC:44581/](http://baila-PC:44581/)

SUMMARY

PARAMETERS

NODES

ROS_MASTER_URI=http://localhost:11311

No processes to monitor
shutting down processing monitor...
... shutting down processing monitor complete
process[X1/ros1_ign_bridge_imu-1]: started with pid [580]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_imu-1] process has died [pid 580, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /world/tunnel_qual_ign/model/X1/link/base_link/sensor/imu_sensor/imu@sensor_msgs/Imu@ignition.msgs.IMU /world/tunnel_qual_ign/model/X1/link/base_link/sensor/imu_sensor/imu:=imu/data __name:=ros1_ign_bridge_imu __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_imu-1.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_imu-1*.log
[Dbg] [Manager.cc:295] Received signal[17]
[Dbg] [Manager.cc:312] Death of process[500] with name[x2_description].
process[tf_world_static-3]: started with pid [584]
process[X1/ros1_ign_bridge_pose-2]: started with pid [603]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_pose-2] process has died [pid 603, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /model/X1/pose@geometry_msgs/TransformStamped@ignition.msgs.Pose /model/X1/pose:=pose __name:=ros1_ign_bridge_pose __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_pose-2.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_pose-2*.log
process[X1/ros1_ign_bridge_odom-3]: started with pid [609]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_odom-3] process has died [pid 609, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /model/X1/odometry@nav_msgs/Odometry@ignition.msgs.Odometry /model/X1/odometry:=odom __name:=ros1_ign_bridge_odom __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_odom-3.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_odom-3*.log
process[X1/ros1_ign_bridge_actuators-4]: started with pid [610]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_actuators-4] process has died [pid 610, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /model/X1/command/motor_speed@mav_msgs/Actuators@ignition.msgs.Actuators /model/X1/command/motor_speed:=command/motor_speed __name:=ros1_ign_bridge_actuators __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_actuators-4.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_actuators-4*.log
process[X1/ros1_ign_bridge_twist-5]: started with pid [611]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_twist-5] process has died [pid 611, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /model/X1/cmd_vel_relay@geometry_msgs/Twist@ignition.msgs.Twist /model/X1/cmd_vel_relay:=cmd_vel __name:=ros1_ign_bridge_twist __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_twist-5.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_twist-5*.log
process[X1/ros1_ign_bridge_camera-6]: started with pid [612]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_camera-6] process has died [pid 612, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /world/tunnel_qual_ign/model/X1/link/base_link/sensor/camera_front/image@sensor_msgs/Image@ignition.msgs.Image /world/tunnel_qual_ign/model/X1/link/base_link/sensor/camera_front/camera_info@sensor_msgs/CameraInfo@ignition.msgs.CameraInfo /world/tunnel_qual_ign/model/X1/link/base_link/sensor/camera_front/image:=front/image_raw /world/tunnel_qual_ign/model/X1/link/base_link/sensor/camera_front/camera_info:=front/camera_info __name:=ros1_ign_bridge_camera __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_camera-6.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_camera-6*.log
process[X1/ros1_ign_bridge_gpu_lidar-7]: started with pid [613]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_gpu_lidar-7] process has died [pid 613, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /world/tunnel_qual_ign/model/X1/link/base_link/sensor/front_laser/scan@sensor_msgs/LaserScan@ignition.msgs.LaserScan /world/tunnel_qual_ign/model/X1/link/base_link/sensor/front_laser/scan:=front_scan __name:=ros1_ign_bridge_gpu_lidar __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_gpu_lidar-7.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_gpu_lidar-7*.log
process[X1/ros1_ign_bridge_magnetometer-8]: started with pid [614]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_magnetometer-8] process has died [pid 614, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /world/tunnel_qual_ign/model/X1/link/base_link/sensor/magnetometer/magnetometer@sensor_msgs/MagneticField@ignition.msgs.Magnetometer /world/tunnel_qual_ign/model/X1/link/base_link/sensor/magnetometer/magnetometer:=magnetic_field __name:=ros1_ign_bridge_magnetometer __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_magnetometer-8.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_magnetometer-8*.log
process[X1/ros1_ign_bridge_fluid_pressure-9]: started with pid [615]
/opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: symbol lookup error: /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge: undefined symbol: _ZN8ignition4msgs8Odometry17default_instance_E
[X1/ros1_ign_bridge_fluid_pressure-9] process has died [pid 615, exit code 127, cmd /opt/ros/melodic/lib/ros1_ign_bridge/parameter_bridge /world/tunnel_qual_ign/model/X1/link/base_link/sensor/air_pressure/air_pressure@sensor_msgs/FluidPressure@ignition.msgs.FluidPressure /world/tunnel_qual_ign/model/X1/link/base_link/sensor/air_pressure/air_pressure:=air_pressure __name:=ros1_ign_bridge_fluid_pressure __log:=/home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_fluid_pressure-9.log].
log file: /home/developer/.ros/log/54eb537c-a19f-11e9-a985-68a3c4a1e180/X1-ros1_ign_bridge_fluid_pressure-9*.log
process[X1/pose_tf_broadcaster-10]: started with pid [616]

I have highlighted some of the lines. Those lines came in red and simulation came blank.

Alfredo Bencomo (bencomo) , Nate Koenig (Nathan Koenig)

osrf-migration commented 5 years ago

Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero).

The undefined symbol message is probably coming from an out of date version of ignition packages, particularly the msgs4 package. I would recommend to run:

sudo apt-get update && sudo apt-get upgrade
# to be sure
sudo apt-get install libignition-msgs4-dev
osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Jose Luis Rivero (Jose Luis Rivero) , I am getting the below error only while running,

‌

developer@baila-PC:~/subt_ws$ ign launch -v 4 competition.ign robotName1:=X1 robotConfig1:=X2_SENSOR_CONFIG_1

‌

ROS_MASTER_URI=http://localhost:11311

ERROR: cannot launch node of type [ros_melodic_ros1_ign_bridge/parameter_bridge]: ros_melodic_ros1_ign_bridge
ROS path [0]=/opt/ros/melodic/share/ros
ROS path [1]=/home/developer/subt_ws/install/share
ROS path [2]=/opt/ros/melodic/share
started roslaunch server http://baila-PC:44873/

‌

Also it is coming up with blank screen.

osrf-migration commented 5 years ago

Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero).

seems like it can not locate the `parameter_bridge` script. Please be sure that you have the ros-melodic-ros1-ign-bridge package installed. If you have it, resource the setup.bash for melodic: source /opt/ros/melodic/setup.bash. Hopefully that should fix it.

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Yes, i did that…it fixed the previous error…but still I am getting blank screen. Any clue?

osrf-migration commented 5 years ago

Original comment by baila (Bitbucket: baila).

Finally!! I am able to see the robots using,

Thanks a lot for your help. I think this issue can be closed.

ign launch virtual_stix.ign robotName1:=X1 robotConfig1:=X1_SENSOR_CONFIG_1

osrf-migration commented 5 years ago

Original comment by Alfredo Bencomo (Bitbucket: bencomo).

osrf-migration commented 5 years ago

Original comment by Alfredo Bencomo (Bitbucket: bencomo).