-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Invoking export-blocks leads to "essential task failed" error messages #10583
Comments
Yeah I have seen similar things. This seems to be correlated with starting only half of the node and also dropping some stuff that isn't needed. |
Faced to the same issue when exporting blocks. Is there any updates on this issue? |
This also happens when benchmarking sets up a client. |
Hello, was someone able to resolve this issue? CC: @bkchr |
I think a few things just need to be kept in memory rather than being dropped, but I didn't bother to dig into it yet as it is harmless. |
Yes, as I said above this is because we drop some things that we start as essential task. This will then lead to this log message. And yes, these messages are not problematic. |
@bkchr In our case, there is failed error message and no block being exported.... root@localhost:~# sudo ./polkadot export-blocks --chain kusama --from 20 --to 4000 --base-path /chains_data 2022-12-27 10:31:54 👶 Creating empty BABE epoch changes on what appears to be first startup. root@localhost:~# ls -l |
When invoking
export-block
command there are error messages about "essential task failed". However, it does not seem to be an issue for exporting blocks since they do get exported. So it's just bad messaging.The text was updated successfully, but these errors were encountered: