search

thetatoken / guardian-mainnet-guide

Guide for setting up the Guardian Node for the mainnet
https://docs.thetatoken.org/
147 stars 34 forks source link

Guardian node "performing health check" #67

Open noFUD opened 3 years ago

noFUD commented 3 years ago

My internet went down so I rebooted and restarted the node which was not working after the internet came back up. After restart of the node it loaded most of the way.. 85% or so then it shows.. Performing Health Check..

Never seen this before.. is it normal and how long can I expect it to be this way? Tried deleting the node and reinstalling it but still has the same Performing Health Check come up...

Screenshot (2)

ArmoredRage commented 3 years ago

A lot of us are having the same issue. Just loads snapshot to 100% then health check and starts the whole process over. Reinstalling, clearing DB, or anything else dosent seems to help.

noFUD commented 3 years ago

I thought about reinstalling windows and reinstalling the node since that is only what this computer is mainly used for. Hope the boys at Theta are working on a fix soon.

Hoyapooch commented 3 years ago

I am having the exact same issue. Any new news on this?

noFUD commented 3 years ago

posted on twitter and checking with some youtubers to see if they know anything. nothing new so far

On Sun, Mar 7, 2021 at 6:01 PM Hoyapooch notifications@github.com wrote:

I am having the exact same issue. Any new news on this?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/67#issuecomment-792409176, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKCSPBGUJCUEJO5XEIOSJLTCQVWPANCNFSM4YYOAHOQ .

noFUD commented 3 years ago

looking at guardianmonitor.io seems like over half the nodes are down ATM

On Sun, Mar 7, 2021 at 6:01 PM Hoyapooch notifications@github.com wrote:

I am having the exact same issue. Any new news on this?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/67#issuecomment-792409176, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKCSPBGUJCUEJO5XEIOSJLTCQVWPANCNFSM4YYOAHOQ .

Hoyapooch commented 3 years ago

I was running my node on standard. So I kicked it up to Platinum and reset peers. I'm at about 99.98% right now and am not seeing that performing health check warning.

I'll update if the node actually kicks in at 100%

noFUD commented 3 years ago

I'm at 99.99% as well now..

On Sun, Mar 7, 2021, 7:21 PM Hoyapooch notifications@github.com wrote:

I was running my node on standard. So I kicked it up to Platinum and reset peers. I'm at about 99.98% right now and am not seeing that performing health check warning.

I'll update if the node actually kicks in at 100%

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/67#issuecomment-792433282, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKCSPHG3N66DXZG757QHNTTCQ7EPANCNFSM4YYOAHOQ .

Hoyapooch commented 3 years ago

update: so not sure if it was coincidence, but resetting the peers and changing the level to platinum got my node up and running again

clutchnshift commented 3 years ago

I too started to get this on the evening of 05MAR21. I was not able to run the GN on the 6th and it was no-go today. At first, I thought it was because I reset my peers, just for S&Giggles. But before that, I noticed that my peers had dropped to 3 and the GN said Poor Connectivity to that count. I deleted the node database and when it came back up in about an hour, it was back to 12 peers with Good Connectivity. Before I went to bed, I was curious about resetting the peers, so I clicked on it and that was that. When I checked on the GN the next morning, it was not Synced.

I checked the log and found some errors, it was fine up until the Node Startup got to the Config File. From that point on it would continue to try and load the snapshot, but once it got to 85%, it would perform a health check and then start all over again, and continue to do so with no end.

I deleted the database, no help. I uninstalled the GN and reinstalled it, no help. I reset my router, no help. I then uninstalled the GN again and before reinstalling it I manually deleted the AppData for the Guardian Node, so that when the GN was reinstalled it would create a new folder with goodies, which it did. When I went to start the GN, it was like when I installed it for the first time, all the initial prompts, but still not Syncing to the Network and having Peer errors.

Looking back, it doesn't seem to be downloading the snapshot, it was skipping that step, just moving on to the loading of the snapshot.

At the moment, my GN is Syncing, holding at 99.95% (which is an improvement). I was glad (not really, but yes) to see that others were running into the same issue. I have it set to Platinum performance tier now, I still have to wait and see if it will fully Sync to the Network.

With som many having similar issues, my guess is that there was nothing wrong on our end. Wasn't this 2.2.4 version recently installed? 03MAR21? Maybe it's got bugs.

Here are some of the errors I was getting, once the snapshot was loaded (which caused the GN snapshot to reload):

[2021-03-07 16:01:40.165] [info] [2021-03-07 16:01:40] INFO [snapshot] Snapshot loaded successfully.

[2021-03-07 16:01:40.168] [error] [2021-03-07 16:01:40] WARN [p2p] Failed to retrieve previously persisted peers [2021-03-07 16:01:40.168] [info] [2021-03-07 16:01:40] INFO [p2p] Connecting to seed and persisted peers... [2021-03-07 16:01:40] WARN [p2p] Failed to retrieve previously persisted peers [2021-03-07 16:01:40] INFO [p2p] InboundPeerListener listen routine started, seedPeerOnly set to false

noFUD commented 3 years ago

Sounds like the same issues... I am synced most of the time but it lags every so often. I only have a maximum of 5 peers currently and lag often.. I have two GN'S running so hopefully between the two I can get a fairly consistent payout. I hope they can sort this out soon and push a corrected update.

On Sun, Mar 7, 2021, 11:18 PM clutchnshift notifications@github.com wrote:

I too started to get this on the evening of 05MAR21. I was not able to run the GN on the 6th and it was no-go today. At first, I thought it was because I reset my peers, just for S&Giggles. But before that, I noticed that my peers had dropped to 3 and the GN said Poor Connectivity to that count. I deleted the node database and when it came back up in about an hour, it was back to 12 peers with Good Connectivity. Before I went to bed, I was curious about resetting the peers, so I clicked on it and that was that. When I checked on the GN the next morning, it was not Synced.

I checked the log and found some errors, it was fine up until the Node Startup got to the Config File. From that point on it would continue to try and load the snapshot, but once it got to 85%, it would perform a health check and then start all over again, and continue to do so with no end.

I deleted the database, no help. I uninstalled the GN and reinstalled it, no help. I reset my router, no help. I then uninstalled the GN again and before reinstalling it I manually deleted the AppData for the Guardian Node, so that when the GN was reinstalled it would create a new folder with goodies, which it did. When I went to start the GN, it was like when I installed it for the first time, all the initial prompts, but still not Syncing to the Network and having Peer errors.

Looking back, it doesn't seem to be downloading the snapshot, it was skipping that step, just moving on to the loading of the snapshot.

At the moment, my GN is Syncing, holding at 99.95% (which is an improvement). I was glad (not really, but yes) to see that others were running into the same issue. I have it set to Platinum performance tier now, I still have to wait and see if it will fully Sync to the Network.

With som many having similar issues, my guess is that there was nothing wrong on our end. Wasn't this 2.2.4 version recently installed? 03MAR21? Maybe it's got bugs.

Here are some of the errors I was getting, once the snapshot was loaded (which caused the GN snapshot to reload):

[2021-03-07 16:01:40.165] [info] [2021-03-07 16:01:40] INFO [snapshot] Snapshot loaded successfully.

[2021-03-07 16:01:40.168] [error] [2021-03-07 16:01:40] WARN [p2p] Failed to retrieve previously persisted peers [2021-03-07 16:01:40.168] [info] [2021-03-07 16:01:40] INFO [p2p] Connecting to seed and persisted peers... [2021-03-07 16:01:40] WARN [p2p] Failed to retrieve previously persisted peers [2021-03-07 16:01:40] INFO [p2p] InboundPeerListener listen routine started, seedPeerOnly set to false

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/67#issuecomment-792531753, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKCSPDV73IFSVDZQQCYB5DTCR25FANCNFSM4YYOAHOQ .

sanspeur33 commented 3 years ago

Same issue here. Just keeps cycling. Look at network monitor, it really doesn't seem to be pulling database like it use to when you deleted the database, I would see the network max out, while pulling it down. Now it doesn't.

It was working great yesterday, till I accidently flipped the wrong breaker and it had to re-start. Gone from Bronze to 0. All tricks of, deleting database, and re-starting not working. What happens to stakes if you delete the node install completely? Not sure what steps to take. Linux box running Ubuntu.

clutchnshift commented 3 years ago

Looking at the new (re-installed) config.yaml file in my computer's (Windows 10 pro) AppData folder for my GN, it seems like they upped the peers to a minimum of 24 and maximum of 96 (because of selecting PLATINUM). My GN came up, but of course, since it's like a fresh install, I need to re-stake my THETA to the new GN. I'll let you know how it goes, but my GN has Synced, just needs to be re-staked so it can participate and earn TFUEL.

I didn't check out the GN's mid-level, but I supposed it too means a different range of peer to peer participation, somewhere between Platinum and Standard...18min/48max???

Platinum: minNumPeers: 24 maxNumPeers: 96

Standard: minNumPeers: 12 maxNumPeers: 24

noFUD commented 3 years ago

Thanks for the update .. I will be looking forward to the restake info about the peers... I am still getting between zero and 5 peers

On Mon, Mar 8, 2021, 8:32 AM clutchnshift notifications@github.com wrote:

Looking at the new (re-installed) config.yaml file in my computer's (Windows 10 pro) AppData folder for my GN, it seems like they upped the peers to a minimum of 24 and maximum of 96 (because of selecting PLATINUM). My GN came up, but of course, since it's like a fresh install, I need to re-stake my THETA to the new GN. I'll let you know how it goes, but my GN has Synced, just needs to be re-staked so it can participate and earn TFUEL.

I didn't check out the GN's mid-level, but I supposed it too means a different range of peer to peer participation, somewhere between Platinum and Standard...18min/48max???

Platinum: minNumPeers: 24 maxNumPeers: 96

Standard: minNumPeers: 12 maxNumPeers: 24

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/67#issuecomment-792880880, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKCSPHRPJDSURBQ3OMRYE3TCT327ANCNFSM4YYOAHOQ .

clutchnshift commented 3 years ago

Same issue here. Just keeps cycling. Look at network monitor, it really doesn't seem to be pulling database like it use to when you deleted the database, I would see the network max out, while pulling it down. Now it doesn't.

It was working great yesterday, till I accidently flipped the wrong breaker and it had to re-start. Gone from Bronze to 0. All tricks of, deleting database, and re-starting not working. What happens to stakes if you delete the node install completely? Not sure what steps to take. Linux box running Ubuntu.

Sanspeur33, when I deleted the GN, the THETA remained in that wallet. If I understand this correctly, anyone feel free to correct me, your THETA, when you stake it, will be assigned to the wallet for the GN (a public address).

So, your THETA will transfer to the wallet for the GN from where ever you have your originating THETA wallet. Say you have 1,000 THETA on the mainnet or app wallet, you stake it, it will transfer from the mainnet or app wallet to a new GN wallet on the mainnet. If you have your THETA in cold storage, the staked GN THETA will be in cold storage. If you uninstal completely (zero record of the GN on your computer), your GN wallet remains intact, but now you have to unstake and then transfer it back to your originating wallet (or where ever you want it to go). If you want to re-stake that same or a different amount of THETA, you are now starting from scratch with the GN (this part is where I am at right now...we'll see).

noFUD commented 3 years ago

Wonder if this will be fixed when the next update gets pushed thru on the 10th

On Mon, Mar 8, 2021, 11:18 AM clutchnshift notifications@github.com wrote:

Same issue here. Just keeps cycling. Look at network monitor, it really doesn't seem to be pulling database like it use to when you deleted the database, I would see the network max out, while pulling it down. Now it doesn't.

It was working great yesterday, till I accidently flipped the wrong breaker and it had to re-start. Gone from Bronze to 0. All tricks of, deleting database, and re-starting not working. What happens to stakes if you delete the node install completely? Not sure what steps to take. Linux box running Ubuntu.

Sanspeur33, when I deleted the GN, the THETA remained in that wallet. If I understand this correctly, anyone feel free to correct me, your THETA, when you stake it, will be assigned to the wallet for the GN (a public address).

So, your THETA will transfer to the wallet for the GN from where ever you have your originating THETA wallet. Say you have 1,000 THETA on the mainnet or app wallet, you stake it, it will transfer from the mainnet or app wallet to a new GN wallet on the mainnet. If you have your THETA in cold storage, the staked GN THETA will be in cold storage. If you uninstal completely (zero record of the GN on your computer), your GN wallet remains intact, but now you have to unstake and then transfer it back to your originating wallet (or where ever you want it to go). If you want to re-stake that same or a different amount of THETA, you are now starting from scratch with the GN (this part is where I am at right now...we'll see).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/67#issuecomment-793006810, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKCSPGJOG5QOYYOUVCU5RLTCUPJ3ANCNFSM4YYOAHOQ .

1spacegoat commented 3 years ago

anyone still have this issue? I did a node restart after windows update and all i get now is health check failed

1spacegoat commented 3 years ago

2.2.10

noFUD commented 3 years ago

since im moving im staked to gpool so when i get setted ill figure it out

On Sun, Mar 21, 2021 at 10:01 AM David Garry @.***> wrote:

@1spacegoat https://github.com/1spacegoat Have you been able to get through to them ?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/thetatoken/guardian-mainnet-guide/issues/67#issuecomment-803622711, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKCSPHZPLXLD2B7UD4EETTTEYQ5ZANCNFSM4YYOAHOQ .

clutchnshift commented 3 years ago

anyone still have this issue? I did a node restart after windows update and all i get now is health check failed

I have 2.2.10 now as well and if I run the GN for some time, then close it, when I restart it hours later it comes up almost instantly, or so it seems, but then it won’t sync in the background, it will state “health check failed” at the bottom window where it shows the GN’s work in progress. At that point I just Delete Node Database, and after a full restart (re-sync), it works fine. In short, in my experiences, every time you restart it (run it, then close out) you will likely have to do Delete Node Database.

ArmoredRage commented 3 years ago

Garitty7612 is a scammer. Dont click the link. Also dont trust anyone claiming to the support on telegram. They have moved to discord. Never give keys or phrases out support will never ask for them.