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

ign topic -l empty in ignition-blueprint on one computer #294

Closed
peci1 opened this issue Aug 14, 2020 · 5 comments
Closed

ign topic -l empty in ignition-blueprint on one computer #294

peci1 opened this issue Aug 14, 2020 · 5 comments

Comments

@peci1
Copy link
Contributor

peci1 commented Aug 14, 2020

We have one desktop computer with clean install of Ubuntu 18.04.4 and NVidia GTX 1060 GPU. On this particular desktop, ignition topics of gazebo do not work. I've no idea why, because on other machines it does.

Terminal 1:

$ ign gazebo

Terminal 2:

$ ign topic -l
$

Clearly, the ign topic command doesn't see any published topics. On other machines it does.

But if I try ign-transport directly, it works:

Terminal 1:

$ while true; do ign topic -t /foo -m   ignition.msgs.StringMsg -p 'data:"Custom data"'; done

Terminal 2:

$ ign topic -e -t /foo
data: "Custom data"

data: "Custom data"

data: "Custom data"

data: "Custom data"

^C$

Do you have an idea how to debug this computer? I've tried running in both terminals with IGN_PARTITION=foo, but the result was the same. I tried launching with IGN_VERBOSE=1, but nothing weird would be shown. I tried calling ign topic -e via strace, and I saw a lot of successful setsockopt, IP_ADD_MEMBERSHIP etc, followed by writing \1\0\0\0\0\0\0\0\0 into the socket, and then a timed-out poll. I tried turning off all network interfaces except lo, but no change. We tried reinstalling the computer - no help.

We've also accidentally installed ignition-citadel, and there the communication worked. But we need blueprint for the SubT challenge. Once I uninstalled citadel (apt remove ignition-citadel && apt autoremove), the communication in blueprint is broken again.

@peci1 peci1 changed the title ign topic -l empty in ignition-blueprint ign topic -l empty in ignition-blueprint on one computer Aug 14, 2020
@caguero
Copy link
Contributor

caguero commented Aug 14, 2020

I suspect that your ign commands are using a different version of Ignition Transport than Ignition Gazebo. You can check with ign topic --versions. If that's the case, you could either:

a) Force your ign topic to use the same version as Ignition Gazebo. E.g.: ign topic -l --force-version 7.5.0.

or

b) Remove the leftover files from your previous Ignition Citadel installation. E.g.: sudo rm /usr/share/ignition/transport8.yaml

@peci1
Copy link
Contributor Author

peci1 commented Aug 14, 2020

Wow, it actually worked, thank you! So it seems ignition-citadel did not uninstall itself correctly. But I tried to replicate it on another computer (install and uninstall citadel) and the leftover file was not left there.

@caguero
Copy link
Contributor

caguero commented Aug 14, 2020

I'll close the issue but feel free to reopen if needed.

@caguero caguero closed this as completed Aug 14, 2020
@peci1
Copy link
Contributor Author

peci1 commented Feb 2, 2021

Another reason why this can happen is if the publishers are run with IGN_TRANSPORT_TOPIC_STATISTICS=1 and the list command is run with this variable set to zero (or the other way round). As is the case after osrf/subt#742 in SubT simulator. This took me about an hour to figure out :( Isn't there really a way to provide better user experience, at least in case the result of ign topic -l is empty?

@peci1
Copy link
Contributor Author

peci1 commented Feb 2, 2021

I logged an improvement request in gazebosim/gz-transport#218 .

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