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

error message: "error sending response: Host unreachable" even if the service call behaved as exepected #562

Open
paoloelle opened this issue Dec 9, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@paoloelle
Copy link

paoloelle commented Dec 9, 2024

Environment

  • OS Version: Ubuntu 22.04
  • Source or binary build? Binary Gazebo Fortress

Description

  • Expected behavior: Some message that tells me if the service call behaved as expected even if an error occurred in sending the response to the service
  • Actual behavior:
    I'm just implementing a simple scenario where I have a robot and a couple of simple objects that need to be moved in the arena with a certain frequency. I have a bash script that allows me to do that. The problem that I'm facing is that, even if the robot and the objects are moved as expected, I keep seeing the message [ruby $(which ign) gazebo-1] NodeShared::RecvSrvRequest() error sending response: Host unreachable when the timeout for the service is triggered (Service call timed out).

I guess the issue can be related to #243.

Steps to reproduce

  1. Run a simple simulation with some objects
  2. Change the position of the objects continuously

Output

This is the output that I get when the timeout for the service call expires (even if the object is moved to the new position as expected):

  • [ruby $(which ign) gazebo-1] NodeShared::RecvSrvRequest() error sending response: Host unreachable
  • Service call timed out
@paoloelle paoloelle added the bug Something isn't working label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Inbox
Development

No branches or pull requests

1 participant