resource handshake timeout on b0.23 still appears

[ederenn]

Description

Golem Version: GOLEM Version: 0.22.1+dev104.g9a13476

Golem-Messages version (leave empty if unsure): 3.15.0

Electron version (if used):

OS [e.g. Windows 10 Pro]: Any

Branch (if launched from source):

Mainnet/Testnet: mainnet

Priority label is set to the lowest by default. To setup higher priority please change the label P0 label is set for Severity-Critical/Effort-easy P1 label is set for Severity-Critical/Effort-hard P2 label is set for Severity-Low/ Effort-easy P3 label is set for Severity-Low/Effort-hard

Description of the issue:

After requesting a task two providing nodes were banned after receiving resource handshake timeout. This issue has been recently fixed https://github.com/golemfactory/golem/issues/5105 but handshake timeout still appears.

INFO     [golem.task.server.resources        ] Resource handshake timeout. node=fc42bebd..e377b8cd 
INFO     [golem.task.acl                     ] Banned node. node_id=fc42bebd..e377b8cd, timeout=7200s, persist=False 
INFO     [golem.client                       ] Updating mask for task 'd40dc9ae-6203-11ea-8dea-6c15fa96c125' Mask size: 0 

Actual result:

provides are banned

Steps To Reproduce

Short description of steps to reproduce the behavior: e.g.

1. Connect to several nodes, at least 3 or 4 providers
2. Request a small task. In my case handshake timeout had happened in tasks:

• helicopter.blend, samples and resolution from file, 1 frame, 1 subtask, 30 min for task, 30 min for subtasks, bid 0.1
• helicopter.blend, resolution: 400x400, samples from file, 2 frames, 4 subtasks, 10 min for task, 5 min for subtask, bid 0.1

3. Wait for task to finish
4. check golemcli acl list if any node was banned
5. Check in logs for handshake timeout

Logs and any additional context

requested task id: 1 frame 1 subtask task: d40dc9ae-6203-11ea-8dea-6c15fa96c125 2 frames 4 subtasks task: 7f827e9c-620b-11ea-bb60-6c15fa96c125

task 7f827e9c-620b-11ea-bb60-6c15fa96c125 on debug (debug is in the middle of uploaded file!) task d40dc9ae-6203-11ea-8dea-6c15fa96c125 in regular logs

full log: requestor: https://drive.google.com/open?id=1JTKOk3x6dlfsqQ9_E0kfEJTDMODTgKzU banned provider: https://drive.google.com/open?id=1TEfARSbUZe1O8hgg_MXc7UTxss-RLaa5

Proposed Solution?

(Optional: What could be a solution for that issue)

[maaktweluit]

could be related to golemfactory/simple-transfer#22