Lock expires constantly in BF1 scenario

Dominik1999 commented 5 years ago

Issue checklist

To help us more easily debug your issue please check the boxes for which requirements for safe usage or Raiden were followed:

[x] The Ethereum node was always up to date with the chain tip and never stopped running.
[x] No Ethereum transaction was sent for the account that Raiden manages by another app.
[x] The Ethereum account used by Raiden always had sufficient ETH.
[x] The Raiden DB that exists by default at ~/.raiden was never altered or deleted.
[x] The Raiden node was never restarted. If yes please provide more info.
[x] The Ethereum node was not switched while Raiden was running.
[x] The Raiden REST API is protected from public access.

-->

Problem Definition

The nightly scenario runs of the bf1 scenario fail with {\"errors\": \"Payment couldn't be completed because: lock expired\"}"}

Here are the logs

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

uname -a
command -v solc && solc --version
command -v geth && geth version
command -v parity && parity --version
command -v raiden && raiden version
[ -d .git ] && git rev-parse HEAD

hackaugusto commented 5 years ago

node3: 0xFa206b6Cf9EAc08dD15E13c7F54174C31C895246 failed task: TransferTask from: 3 to: 0 amount: 1000000000000000 lock_timeout: 30 node3: SendLockedTransfer recipient: 0x7a5c66E108F7Aa1E45272B81AC0f951501D44140

running grep RetryQueue | jq .event | sort -u gives:

"Partner not reachable. Skipping."
"Retrying message"

So the problem seems to be with the presence of the nodes.

Note: The routes were given by the PFS.

Dominik1999 commented 5 years ago

@err508 this seems to be same problem you are working on

hackaugusto commented 5 years ago

I'm closing this since my PR was merged and the problem from the issue was fixed. The presence still has to be fixed for the scenario to pass

raiden-network / raiden

Lock expires constantly in BF1 scenario #5159

Issue checklist

Problem Definition

System Description