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

ignite relayer fails to transmit packets across multiple paths #3203

Closed
ratankaliani opened this issue Nov 29, 2022 · 6 comments · Fixed by #3210
Closed

ignite relayer fails to transmit packets across multiple paths #3203

ratankaliani opened this issue Nov 29, 2022 · 6 comments · Fixed by #3210
Assignees
Labels
report type:error Something isn't working

Comments

@ratankaliani
Copy link

ratankaliani commented Nov 29, 2022

Describing Bug

I'm currently having difficulty setting up a relayer locally that handles packets transmitted over multiple paths to 2+ ignite chains.

I have 3 chains: Earth, Mars & Horus and configure connections from Earth -> Mars and Earth -> Horus by running
ignite relayer configure -a commands with the same source-rpc (Earth) and two different target-rpc's (Mars, Horus).

The relayer is only relaying and ack'ing tx's sent from the first path & not the second. Any tips on how to set up the relayer such that it is able to receive & send from more than one path?

Simulating Bug

  1. Start 3 ignite chains: Earth, Mars & Horus
  2. Configure relayer connections from Earth <-> Mars and Earth <-> Horus
  3. Send packet from Earth -> Mars (transmits & ack's succesfully)
  • planetd tx blog send-ibc-post blog channel-0 "Earth->Mars" "Hello Mars, I'm Alice from Earth" --from alice --chain-id earth --home ~/.earth
  1. Send packet from Earth -> Horus (does not get transmitted)
  • planetd tx blog send-ibc-post blog channel-1 "Earth->Horus" "Hello Horus, I'm Alice from Earth" --from alice --chain-id earth --home ~/.earth

Output of Relayer

After running both commands, output of relayer is shown below. Relayer is only transmitting packets over the first path!

image

What version are you using?
v0.25.2

@ratankaliani ratankaliani added the type:error Something isn't working label Nov 29, 2022
@ratankaliani
Copy link
Author

cc @jeronimoalbi Any updates on this?

@jeronimoalbi
Copy link
Member

@ratankaliani I just replicated the issue locally.

Transaction data seems to be right for the case that is not working so I'm assuming the issue might be related to the relayer. Have in mind that the relayer implementation used in the CLI is aimed to help during development but it's not intended to be used in some cases like production environments for example.

In the meantime I would encourage you to run a relayer using Hermes or go relayer.

@jeronimoalbi
Copy link
Member

Thank you for reporting the issue @ratankaliani 👍

@ratankaliani
Copy link
Author

Thanks for resolving!

@ratankaliani
Copy link
Author

Also @jeronimoalbi is there an ETA on the next release?

@jeronimoalbi
Copy link
Member

Also @jeronimoalbi is there an ETA on the next release?

@ratankaliani I'm not aware of a date for the next release but I believe it should come soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
report type:error Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants