Documentation support for ARM64 #149
Conversation
|
Hello Techguyk, Have initiated the launch process with a newly created password after writing the below command: That said, it is giving me a snapshot validation error after allocating cache and file handles: Obviously has to do with the snapshot file. There is a snapshot file located in the node directory, as well as a config.yaml file. Is the snapshot file supposed to be a .yaml as well? Was going to open these binary feels to dig into it, will that potentially throw off the current node processes if I execute them in my terminal? Have solved this problem! This may have been an error while following your commands. That said, the snapshot file saves down into the theta_mainnet directory, which is separate from the go directory. In your repository you advise to launch from the theta_mainnet repository, which is why you have us save down the snapshot in that repository. However, you need to launch the node from the not the Figured this out by looking at your screenshots from the binary repository. Solution was as simple as copying the snapshot into the go/guardian_mainnet/node directory!! Copy and pasted through GUI. believe the command would be: Thoughts? |
|
@T3Crypto I found the same issue today and fixed it as well. Instead of copying the file to the other folder, I updated the command to point to the right file location instead. However when running ./thetacli query status comment I keep getting an error: "Failed to retrieve Blockchain status: Post http://localhost:16888/rpc dial tcp [::1]:16888: connect: connection refused. Not sure if I missed a step or there's a step that isn't documented |
Add documentation for ARM64, tested on a Raspberry Pi 4 4GB, using Raspberry OS 64 bits.
This guide is based on #1. Resolves #3, resolves thetatoken/theta-protocol-ledger#86.
The guide is only for 64 bit OS. I can't make it work for 32 bits.
Resource usage for Raspberry Pi 4 4GB:
Binaries in .zip files (big sizes):