Closed ederenn closed 4 years ago
Seems like some unfinished work introduced by #4618
@ederenn could you give me full log? Maybe there's something more required to reproduce it, because I can't.
golem.log.2020-03-17.log golem.log.2020-03-30.log golem.log.2020-03-31.log golem.log.2020-04-01.log
error should be at 31.03
No such error in those logs
I don't know yet where, but a missing step has something to do with a Task API task. Otherwise the "docker cpu environment" is never activated.
I found it! The important part is to stop and reconfigure golem, while it's computing (i.e. being a provider for) a Task API task.
fixed and merged to b0.23
Description
Golem Version: 0.22.1+dev124.gf5a985e
Golem-Messages version (leave empty if unsure): 3.15.0
Electron version (if used):
OS [e.g. Windows 10 Pro]: Ubuntu 18.04
Branch (if launched from source): b0.23
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 pausing golem thera are problems with switching on/off requesting only. In logs appears an error
Actual result:
In interface it seems like it is not possible to resume Golem
Steps To Reproduce
Short description of steps to reproduce the behavior: e.g.
Proposed Solution?
(Optional: What could be a solution for that issue)