4. But when retrieve with dealbot's command: dealbot queue-retrieval -e http://127.0.0.1:8764 --cid bafk2bzacecqsqfyk5g5esrhln3ctvsljk5sdg2vyhaeo5ahtosqb5lgobpvcs
It failed with error:
2022-02-18T03:49:54.295+0800 INFO engine engine/engine.go:263 successfully acquired task {"taskID": "7d461a52-2b82-4aac-8867-5176d017977c"}
2022-02-18T03:49:54.295+0800 INFO engine engine/engine.go:269 worker running task {"taskID": "7d461a52-2b82-4aac-8867-5176d017977c", "run_count": 1}
2022-02-18T03:49:54.308+0800 ERROR engine engine/engine.go:307 retrieval task returned error {"taskID": "7d461a52-2b82-4aac-8867-5176d017977c", "err": "failed to load miner actor: GetActor called on undefined address"}
I'm using the same cid for 2 commands.
Should I use a different cid for dealbot queue-retrieval ?
Or there is something else wrong?
I'm testing storage & retrieval of dealbot, on devnet.
What I've done
1. Installed
dealbot v0.0.43
andlotus-v1.13.2
devnet.2. Created deal via:
dealbot queue-storage -e http://127.0.0.1:8764 -s 1KB -m t01000
in dealbot daemon's log, get deal's data cid:
run
lotus-miner sectors list
, could see sector isProving
:3. retrieve via lotus's command:
lotus client retrieve bafk2bzacecqsqfyk5g5esrhln3ctvsljk5sdg2vyhaeo5ahtosqb5lgobpvcs output
succeed with output:Problem
4. But when retrieve with dealbot's command:
dealbot queue-retrieval -e http://127.0.0.1:8764 --cid bafk2bzacecqsqfyk5g5esrhln3ctvsljk5sdg2vyhaeo5ahtosqb5lgobpvcs
It failed with error:
I'm using the same cid for 2 commands. Should I use a different cid for
dealbot queue-retrieval
? Or there is something else wrong?Thanks.
@Update
Refer: