Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Undefined symbol: rcutils_log_internal #388

Closed
tommy-erko opened this issue Sep 30, 2022 · 2 comments
Closed

Undefined symbol: rcutils_log_internal #388

tommy-erko opened this issue Sep 30, 2022 · 2 comments

Comments

@tommy-erko
Copy link

Hi, following the ROS2 Rolling update yesterday (including update of ros-rolling-rcutils: 5.2.0-1 → 6.0.0-1), we started to have an issue with Gazebo not being able to find a logging utility from this repository. The error affects both old Gazebo "Classic" and new Gazebo (originally Ignition). We have an up-to-date version of both simulators corresponding to the new ros-rolling version.

Error logs:
Ignition Gazebo:
[create-2] /opt/ros/rolling/lib/ros_ign_gazebo/create: symbol lookup error: /opt/ros/rolling/lib/ros_ign_gazebo/create: undefined symbol: rcutils_log_internal
Gazebo Classic:
[gzserver-1] gzserver: symbol lookup error: /opt/ros/rolling/lib/libgazebo_ros_imu_sensor.so: undefined symbol: rcutils_log_internal

The result of the error is that none of the Gazebo versions is able to start.

Through a quick scan of the released commits in this repo, I suspects the error might have occured here.

@clalancette
Copy link
Contributor

Through a quick scan of the released commits in this repo, I suspects the error might have occured here.

Yes, that is certainly where that symbol was introduced.

That said, everything in Rolling should have been rebuilt so it could find that symbol, so I'm not sure why that is occurring. Here, if I just run /opt/ros/rolling/lib/ros_ign_gazebo/create, things seem to work for me.

Can you give me a self-contained example of the problem you are having?

@tommy-erko
Copy link
Author

Hi, it was proably a false alarm, we really weren't able to run our simulation in old Gazebo and Ignition Gazebo was falling inside Docker. But since saturday, it all runs perfectly. I suppose the new packages did not download/install properly at first. I will therefore close this, there is no error:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants