cryptiumlabs / backerei

Automated reward payment & account management for Tezos bakers.
https://cryptium.ch/networks/tezos
GNU General Public License v3.0
49 stars 11 forks source link

After the code update is complete, I have encountered this problem with accessing the node 404 #38

Closed focusshell closed 5 years ago

focusshell commented 5 years ago

image #

cwgoes commented 5 years ago

Is your node storing historical data? backerei needs to query data from specific blocks.

The 404 response code is returned by the Tezos node, it has nothing to do with backerei.

focusshell commented 5 years ago

I did not perform cp replication when updating the node, is it related to this?

cwgoes commented 5 years ago

I am not sure what you mean by "cp replication", but you will probably need a full historical data archive to use backerei (a state snapshot alone may be insufficient).

focusshell commented 5 years ago

But now the data has been updated, how can I get historical data?

focusshell commented 5 years ago

After Athen update, the data structure change such that the size of the ledger is only 6G, not sure if the historical data still kept. I think the upgrade already prun the historical data. Do you guys have such issue after Athen upgrade? really appreciate your prompt reply.

focusshell commented 5 years ago

Ok, let me rephrase my question. After Athen upgrade, I did't use CP command to back up the historical data, I assume that as such the ledger database was prun to 6G. Do I have to keep the historical data to run Backerei? I think an important aspect of the Athen upgrade is that we can prun the ledger and save storage space, so if I have to run Backerei, now I still have to keep all the historical ledger (which is about 200G), is my understanding correct? if this is the case, how can i recover the prun out historical data? really appreciate your prompt reply.

cwgoes commented 5 years ago

You need the historical data, not in its entirety but at least for the past half-dozen cycles or so.

I don't know the precise commands to restore it, I suggest asking on the Tezos developer chat.

gaia commented 5 years ago

@focusshell you can check what's the oldest block your node has via ./tezos-admin-client show current checkpoint note the number in Checkpoint level:

then get the Block Hash Backerei is trying to query, in your case BliRTVLD..... and plug it into tzscan. the Level number tzscan displays for this block hash should be higher than your node's Checkpoint level:. If it is lower, backerei can't work.

gaia commented 5 years ago

@cwgoes would it be possible to have backerei use rpc.tezrpc.me instead of the local node?

cwgoes commented 5 years ago

I don't recommend using an external node, since the data returned cannot be verified, but backerei will support it - just change the host and port in ~/.backerei.yaml accordingly.

You will still need a local client binary to sign transactions.

cwgoes commented 5 years ago

Closing since it seems like the original question has been answered.

gaia commented 5 years ago

In .backerei.yaml I have

host: rpc.tezrpc.me
port: 443

but the request still goes out as Secure = False

image

So the response is a 400 The plain HTTP request was sent to HTTPS port