Closed czepluch closed 4 years ago
Before the PFS request, I see a You are not allowed to see their presence
error in the same log file:
{
"event": "Could not fetch user presence",
"logger": "raiden.network.transport.matrix.utils",
"level": "error",
"greenlet_name": "Greenlet<fn:_health_check_worker>",
"timestamp": "2020-04-02 09:36:09.616590",
"exception": "Traceback (most recent call last):\n File \"raiden/network/transport/matrix/utils.py\", line 442, in _fetch_user_presence\n File \"raiden/network/transport/matrix/client.py\", line 535, in get_user_presence\n File \"raiden/network/transport/matrix/client.py\", line 228, in get_presence\n File \"raiden/network/transport/matrix/client.py\", line 180, in _send\n File \"matrix_client/api.py\", line 691, in _send\nmatrix_client.errors.MatrixRequestError: 403: {\"errcode\":\"M_FORBIDDEN\",\"error\":\"You are not allowed to see their presence.\"}"
}
If there are problems with the matrix communication, this might cause the node to seem offline to the matrix server and thus to the PFS.
According to @fredo
Usually you are not allowed to see presence if you do not share a room with the other user
and
this happened due to the switch to a new broadcast room
So this was just a temporary problem and should not happen, again.
But this still happens today. Even after restarting the nodes. I would not consider this issue as fixed.
Does this still happen with old nodes which have been used before yesterday 12 pm ? @czepluch
Yes, the nodes were first spun up on April 1st with the new RC. Initially on t01, but then when it was down yesterday I changed to t02.
I started everything up with fresh nodes using this command to start Raiden:
./raiden-v0.200.0-rc3-linux-x86_64 --keystore-path /path/to/keystore --network-id 5 --eth-rpc-endpoint http://goerli-geth.dappnode:8545 --pathfinding-service-address=https://pfs.t02.testtransport.raiden.network --matrix-server=https://t02.testtransport.raiden.network --log-config "raiden:debug" --api-address localhost:500x --enable-monitoring
However, when trying to perform mediated transfers I still get the same error.
Logs: raiden_debug_logs.zip The file starting from 10:12:12 is the initiator The file starting from 10:10:46 is the mediator The file starting from 10:09:52 is the target
The problem occurred because the PFS did not restart and was still in the old broadcast room. It also missed the capacity updates by the nodes.
Restarting the PFS let it join to the new Broadcast Restarting the nodes send the update capacity to the PFS again
Problem definition
I fired up 3 nodes yesterday and closed them down for the night. Then started them again this morning, but using the https://t02.testtransport.raiden.network/ server instead of https://t01.testtransport.raiden.network/, since t01 is down. Now, when I am trying to do a mediated transfer I get the error below. Below error is from the node initiating the transfer. I've also attached full logs of all three nodes involved in the transfer.
Node1 (initiator): raiden-debug_2020-04-02T09:32:26.412060.log
Node2 (mediator): raiden-debug_2020-04-02T09:31:48.550199.log
Node3 (receiver): raiden-debug_2020-04-02T09:30:48.519095.log
Todos
t02.testtransport.raiden.network