guardian-mainnet-guide
guardian-mainnet-guide copied to clipboard
thetatoken
Failed to get blockchain status - Guardian Node
Followed the guide to run a guardian node on Google Cloud Marketplace.
When entering command thetacli query status
Get the following: Failed to get blockchain status: Post http://localhost:16888/rpc: dial tcp 127.0.0.1:16888: connect: connection refused
Why is this happening?
Thought I'd comment on this, after an hour I finally got a proper response.
But every now and again when I enter thetacli query status I get the same error.
Is my node not connecting to the blockchain correctly or something?
I used the official VM image
eu-west-2 region seems to be working, it's still trying to sync, will update when done
The query command works.
But it's been 36 hours and it's still syncing. Is that normal?
The query commands only work after the snapshot is loaded, typically after 5-6 minutes.
On the marketplace node, please upgrade the theta and thetacli binary to the latest, delete the db folder and the snapshot file under the config folder, and restart the node:
killall -9 theta
wget -O `which theta` `curl -k 'https://mainnet-data.thetatoken.org/binary?os=linux&name=theta'`
wget -O `which thetacli` `curl -k 'https://mainnet-data.thetatoken.org/binary?os=linux&name=thetacli'`
rm -rf /theta/db
wget -O /theta/snapshot `curl -k https://mainnet-data.thetatoken.org/snapshot`
wget -O /theta/config.yaml `curl -k 'https://mainnet-data.thetatoken.org/config?is_guardian=true
python3 /bin/theta_launcher.py /theta/ qwertyuiop
Or you can run the node on a Linux/Ubuntu box: https://docs.thetatoken.org/docs/running-a-guardian-node-through-command-line
Thanks!
Or you can run the node on a Linux/Ubuntu box: https://docs.thetatoken.org/docs/running-a-guardian-node-through-command-line
I'm having better luck following this
I'll update if I can sync and stake theta
Thanks!
I've tried running a guardian node through the command line on a Ubuntu Server hosted on Google Cloud. It's been trying to sync for over 2 hours now
I'm not sure what I'm doing wrong, the official google cloud image for the theta guardian doesn't seem to work for me
Having the same issue. Followed all the steps from https://github.com/thetatoken/guardian-mainnet-guide/blob/master/docs/CLI.md#running-a-guardian-node-through-command-line
I can see the node is syncing (or at least I think it is) as my screen is flooded with:
INFO[0849] Commit to data store, height: 8950109, rootHash: 0x74e2f759a73a0abc026d360de49bafde2a1c78ff2c3c5af4aa0972a368f6d8db prefix=ledger
but, if I open another session to query, i get this: ./thetacli query status Failed to get blockchain status: Post http://localhost:16888/rpc: dial tcp 127.0.0.1:16888: connect: connection refused
Having the same issue - do I need to explicitly open up a port? Running Ubuntu 20.04.1 LTS - I don't have UFW running, I have a few ports open for other things which I can list with nmap localhost. Shouldn't have to open a port as I'm checking from within the same session on the same server...
Failed to get blockchain status: Post http://localhost:16888/rpc: dial tcp [::1]:16888: connect: connection refused
Feel like I've missed something simple...
I'm using the following commands (on my Ubuntu 20.04 LTS Terminal):
-
Navigate to TGN directory: cd ~/theta_mainnet cd bin/
-
Launch TGN ./theta start --config=../guardian_mainnet/node
-
To check status: In fresh Terminal: ./thetacli query status
All seems to be working fine except still syncing after 24 hours - even though I have synced before - had to reboot my pc.
Duncan
On another tack: Can any of you guys advise as to how I can find the "Holder Summary" of the Guardian Node - to use for staking purposes (my Theta Wallet asks for it when trying to stake). Many thanks, Duncan
Ah, turned out it just needed time. Query works and we're all sync'd up. I'm pretty new to theta staking so can't help you on the Holder Summary mate ;)
From the https://www.thetatoken.org/docs/Running-a-Guardian-Node-on-the-Google-Cloud-Marketplace.pdf you can see it says run 'thetacli query guardian' to get the summary. You can then use that summary code in the box in your Theta wallet app under the staking menu, with 1000 Theta tokens being the minimum stake.
On Wed, Jan 27, 2021, at 8:39 PM, Douglas1949 wrote:
Thanks skippa - perhaps some other kind soul might be able to. ;)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/40#issuecomment-768161048, or unsubscribe https://github.com/notifications/unsubscribe-auth/AR6L3MBJN3R6V54NYO43Z4DS37NLXANCNFSM4V2OPTRA.
Many thanks 👍
On Wed, 27 Jan 2021, 09:50 rwhwr, [email protected] wrote:
From the https://www.thetatoken.org/docs/Running-a-Guardian-Node-on-the-Google-Cloud-Marketplace.pdf you can see it says run 'thetacli query guardian' to get the summary. You can then use that summary code in the box in your Theta wallet app under the staking menu, with 1000 Theta tokens being the minimum stake.
On Wed, Jan 27, 2021, at 8:39 PM, Douglas1949 wrote:
Thanks skippa - perhaps some other kind soul might be able to. ;)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/thetatoken/guardian-mainnet-guide/issues/40#issuecomment-768161048>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AR6L3MBJN3R6V54NYO43Z4DS37NLXANCNFSM4V2OPTRA .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/40#issuecomment-768167402, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACMAIC5W4MQTPIRNAKOENHLS37OVRANCNFSM4V2OPTRA .
eu-west-2 region seems to be working, it's still trying to sync, will update when done
I have also deployed the standard build for guardian node from google cloud marketplace. I've been syncing for 8 hours now and something doesn't seem right. Have you gotten to the bottom of what needs to be done to sync the guardian from google cloud vm...
I've been syncing for 4 days !
On Tue, 2 Feb 2021, 23:08 texmason, [email protected] wrote:
eu-west-2 region seems to be working, it's still trying to sync, will update when done
I have also deployed the standard build for guardian node from google cloud marketplace. I've been syncing for 8 hours now and something doesn't seem right. Have you gotten to the bottom of what needs to be done to sync the guardian from google cloud vm...
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/40#issuecomment-772077363, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACMAIC4SOC7FTG2MUU7INI3S5CAVPANCNFSM4V2OPTRA .
The query commands only work after the snapshot is loaded, typically after 5-6 minutes.
On the marketplace node, please upgrade the
thetaandthetaclibinary to the latest, delete thedbfolder and thesnapshotfile under the config folder, and restart the node:killall -9 theta wget -O `which theta` `curl -k 'https://mainnet-data.thetatoken.org/binary?os=linux&name=theta'` wget -O `which thetacli` `curl -k 'https://mainnet-data.thetatoken.org/binary?os=linux&name=thetacli'` rm -rf /theta/db wget -O /theta/snapshot `curl -k https://mainnet-data.thetatoken.org/snapshot` wget -O /theta/config.yaml `curl -k 'https://mainnet-data.thetatoken.org/config?is_guardian=true python3 /bin/theta_launcher.py /theta/ qwertyuiopOr you can run the node on a Linux/Ubuntu box: https://docs.thetatoken.org/docs/running-a-guardian-node-through-command-line
Thanks!
Trying to upgrade Theta and Thetacli getting Access denied error. Running Google-Guardian node
Thank you for your help
i too am getting this issue: Failed to get blockchain status: Post http://localhost:16888/rpc: dial tcp 127.0.0.1:16888: connect: connection refused
been 4 days now.... using Ubuntu 20.04 Server, followed the CLI instructions exactly. I was working previously until about 4 days ago. ive tried wiping files and reinstalling, still no luck. If anyone has a solution please let me know! thanks
alright my node came right, i basiclly ran the cli setup again after deleting my db folder. and after a while of syncing im back online.
@phyx1u5, now that you are syncing, were you successful in staking with the guardian node?
I have a clean install of Debian Buster:
Linux web1 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux
Followed the steps from Running a guardian node through command line running in tmux.
I'm getting a continuous stream of logs on the guardian window that looks like this:
[2021-05-09 17:16:19] DEBUG [store] Persisted trie from memory databasenodes451size46.52 kBtime12.181015msgcnodes0gcsize0.00 Bgctime0slivenodes1livesize0.00 B
[2021-05-09 17:16:19] DEBUG [ledger] Commit to data store, height: 10275320, rootHash: 0x32a9c15bb61b228d80d608a0e4565222f9b2e8de7cf9954079e693207cde198b
[2021-05-09 17:16:19] DEBUG [store] Persisted trie from memory databasenodes14size1.36 kBtime419.123µsgcnodes0gcsize0.00 Bgctime0slivenodes1livesize0.00 B
[2021-05-09 17:16:19] DEBUG [ledger] Commit to data store, height: 10275320, rootHash: 0xec2c005419ca1964443be0831f69280c0d75aa7d10415728ad50601b2c8517d3
[2021-05-09 17:16:19] DEBUG [store] Persisted trie from memory databasenodes84size8.48 kBtime2.37047msgcnodes0gcsize0.00 Bgctime0slivenodes1livesize0.00 B
[2021-05-09 17:16:19] DEBUG [ledger] Commit to data store, height: 10275320, rootHash: 0x9cd803b3e040902a6eb93caf80f3e7eab31ece5c45a886a351529f2e4aa1f91a
[2021-05-09 17:16:19] DEBUG [store] Persisted trie from memory databasenodes9size837.00 Btime278.799µsgcnodes0gcsize0.00 Bgctime0slivenodes1livesize0.00 B
[2021-05-09 17:16:19] DEBUG [ledger] Commit to data store, height: 10275320, rootHash: 0x17f16ec2711d28ccc57029c4d40b453902b0de4c6c74315803e5f014d0bfc6d0
[2021-05-09 17:16:19] DEBUG [store] Persisted trie from memory databasenodes646size66.12 kBtime19.11237msgcnodes0gcsize0.00 Bgctime0slivenodes1livesize0.00 B
[2021-05-09 17:16:19] DEBUG [ledger] Commit to data store, height: 10275320, rootHash: 0xaf3787190bc369417e5951b9f6811b0ed40bb752d9987e06c128aa67bed414c2
Checking listening ports I get:
@web1:~/theta_mainnet/bin$ sudo ss -tulpn | grep LISTEN
[sudo] password for grant:
tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=519,fd=3))
tcp LISTEN 0 128 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=525,fd=6),("nginx",pid=524,fd=6),("nginx",pid=523,fd=6),("nginx",pid=522,fd=6),("nginx",pid=521,fd=6))
tcp LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=519,fd=4))
tcp LISTEN 0 128 *:50001 *:* users:(("theta",pid=920,fd=22))
So the theta application is not opening a socket on the local instance. I don't really know if it is still syncing or not because I can't query the status.
This is what I get when running the status query:
@web1:~/theta_mainnet/bin$ ./thetacli query status
Failed to get blockchain status: Post http://localhost:16888/rpc: dial tcp [::1]:16888: connect: connection refused
I'll leave it and keep trying.
The RPC server only starts after the snapshot has been imported. These days the snapshot size has grown much bigger so the importation takes time. We are working on improving the snapshot import/export. Hopefully can make it more efficient soon. Thanks.
OK, thanks @Rebeccawal01 and @jieyilong. As a follow-up, the node fails after some time. This failure is probably not related to this issue.