Services calls [/shadow_caster_material_name] and [/shadow_caster_render_back_faces] timed out, making Gazebo and ROS launchers unusable #3173
Comments
|
I ran into this issue on one of my machines as well. Latest galactic sync, though I am still on Gazebo 11.9 and I experience the exact same behavior when starting gazebo without anything loaded. |
ljaniec
changed the title
|
it sounds like ignition transport services are not working properly, and this causes gazebo to fail to load? Do you see anything in |
|
Gazebo starts with Terminal log: |
Gazebo is loading up and you can see the scene and even use it, though the services are not available. You can also reproduce this by just running the empty world using Edit: On my second machine this seems to happen randomly, especially when calling gzclient and gzserver seperately. Sometimes they load, sometimes they time out but I don't see a pattern. I am always killing all gzclient and gzserver processes before running again. |
|
When starting and I tried to reinstall my NVidia drivers too - I got the latest recommended and at least I got shadows working (previously everything was much darker than normal). I haven't found anything more than some issues of the problems with Ogre3d about this kind of services timing out...
There is my |
|
I have found something unusual and weird, which maybe could help a bit there - I can use VirtualBox with Ubuntu 20.04 and ROS2 Galactic (binaries from Debian packages) with Gazebo without these errors of timed out services... What is the source of this really weird situation? What do I have to change in my setup for everything to work? Will building Gazebo from source help? It's last thing I haven't tried yet... EDIT: I have done it and it didn't help - I still got the same service calls timed out: |
|
@relffok @scpeters https://githubhot.com/repo/lopsided98/nix-ros-overlay/issues/161
and
and
|
|
I got some more warnings, maybe they will help: After 1 TurtleBot3 Waffle is added to the empty world and clicking Window > Plot, I can generate this errors: There are also no ROS2 topics coming from the robot, only: |
|
There was an update to the Gazebo 11 and by struck of luck I have found out what was maybe not the problem, but at least a solution - I had to reset my Firewall settings in Ubuntu 20.04 because even If this is acceptable solution to this problem, I think this issue could be closed. |
|
@ljaniec Disconnect from the internet and no more errors. |
|
can you try setting |
|
I cannot reproduce this error in a meaningful way right now to check it, sorry. I will close this issue with these steps written down for future users |
This comment was marked as abuse.
This comment was marked as abuse.
Setup: Ubuntu 20.04, ROS 2 Galactic, Gazebo (11.10.1-1~focal)
With the update to the
gazebo11(ver 11.10.1) in the last ROS 2 Galactic sync my launch files and Gazebo overall stopped working correctly (services are timed out).After starting
gazebo --verboseI got:Part of the terminal logs after using my simulation launch file:
But I could put the robot manually in the world, with this output:
Reverting to the old version of Gazebo packages didn't help, but I am not sure if I did it correctly too (maybe I have missed some dependent ROS packages). I have used:
Launcher still won't work even after that.
The text was updated successfully, but these errors were encountered: