-
Notifications
You must be signed in to change notification settings - Fork 276
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
Comments
I suspect that your a) Force your or b) Remove the leftover files from your previous Ignition Citadel installation. E.g.: |
Wow, it actually worked, thank you! So it seems |
I'll close the issue but feel free to reopen if needed. |
Another reason why this can happen is if the publishers are run with |
I logged an improvement request in gazebosim/gz-transport#218 . |
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:
Terminal 2:
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:
Terminal 2:
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 withIGN_VERBOSE=1
, but nothing weird would be shown. I tried callingign topic -e
via strace, and I saw a lot of successfulsetsockopt
,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 exceptlo
, 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.The text was updated successfully, but these errors were encountered: