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

Payment Transfer gets stuck Abruptly #2922

Closed
agatsoh opened this issue Oct 30, 2018 · 2 comments
Closed

Payment Transfer gets stuck Abruptly #2922

agatsoh opened this issue Oct 30, 2018 · 2 comments
Assignees
Labels
State / Investigating For issues that are currently being looked into before labeling further

Comments

@agatsoh
Copy link
Contributor

agatsoh commented Oct 30, 2018

Problem Definition

I(0xf0DAca3B7Cb562059D89bD5d8291a482b20f9D52) open channel with a partner (0x2A7D58e62C829b0321563A6D1dDd7c209eE657C3) The partner sends 51 transfers. They all go through. I try to send to send 51 transfer back the last transfer gets stuck. After that i try to make a payment through the Web UI, and my node is killed with an error or an exception. Even partner is unable to perform any further operations on his end.

After this I opened channel with other partners and deposited made transfers with other partners and they worked.

My logs
node-f0DAca.log

Dominiks logs
https://gist.github.com/Dominik1999/307e61b25f014c4b17808a43cd8467fd

Supplementary logs of the errors that raiden recorded in the /tmp folder while giving an exception and exiting
raiden-exception-2018-10-29T15-44qcdf0j7x.txt
raiden-exception-2018-10-29T15-50kytb9vfq.txt
raiden-exception-2018-10-29T15-3833_omyjs.txt

Issue checklist

Read through Requirements for safe usage mentioned in our documentation and make sure your usage follows the requirements.

  1. Is your Ethereum node syncing and up to date with the blockchain?
    Yes using infura hence it must be uptodate

  2. Are you using the same Ethereum account with anything other than the Raiden node? Or are you running multiple Raiden nodes with the same Ethereum account?
    No single raiden node only meant for testing

  3. Does your Ethereum account used by Raiden have sufficient ETH?
    Yes I had 0.19 eth after all the transactions it still reflects 0.1856 eth on testnet

  4. Did you alter or delete the local DB that exists by default at ~/.raiden?
    No

  5. Did you stop / restart your raiden node while having open channels and/or pending transfers? if so, please provide further information.
    My node was getting killed with an exception each time I initiate payments with the affected channel.

  6. Did you stop / restart your Ethereum node while Raiden was running?
    Many times

  7. Did you switch from one Ethereum node to another? example: switching from a local Ethereum node to an Infura one.
    No same infura node, internally if infura assigns different nodes each time you connect with it then we need to check with implementation details of infura.

  8. Is Raiden REST API protected from public access?
    yes it is on localhost

System Description

Here add a detailed description of your system, e.g. output of the following script:

uname -a
Linux krishna-pc 4.18.12-arch1-1-ARCH #1 SMP PREEMPT Thu Oct 4 01:01:27 UTC 2018 x86_64 GNU/Linux
command -v solc && solc --version
/usr/bin/solc
solc, the solidity compiler commandline interface
Version: 0.4.25+commit.59dbf8f1.Linux.g++
command -v geth && geth version
/usr/bin/geth
Geth
Version: 1.8.16-stable
Git Commit: 477eb0933b9529f7deeccc233cc815fe34a8ea56
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.11
Operating System: linux
GOPATH=
GOROOT=/home/travis/.gimme/versions/go1.11.linux.amd64

command -v raiden && raiden version
raiden-v0.15.1.dev6+g14cba904-linux
@christianbrb christianbrb added the State / Investigating For issues that are currently being looked into before labeling further label Oct 30, 2018
@ulope
Copy link
Collaborator

ulope commented Nov 5, 2018

Possibly related to or duplicate of #2779

@christianbrb
Copy link
Contributor

Duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
State / Investigating For issues that are currently being looked into before labeling further
Projects
None yet
Development

No branches or pull requests

3 participants