pi-node / instructions

254 stars 154 forks source link

Possible availability bug in 0.4.4? #119

Open steeveee100 opened 3 years ago

steeveee100 commented 3 years ago

Hi. Since upgrading to the new Node software I notice it's not updating my availability every day like before. It's been stuck for the last few days! Any ideas?

remzicirit commented 3 years ago

Same here availability update has stopped since upgrading to 4.4 version

hi10bha commented 3 years ago

Same mine is stuck on “ your computer is starting the block chain and nothing happens please guide

nathusius commented 3 years ago

Hi. Since upgrading to the new Node software I notice it's not updating my availability every day like before. It's been stuck for the last few days! Any ideas?

My availability HAS updated since installing 0.4.4, but it definitely seems to be changing less often (installed node update 6 days ago, availability last updated 3 days ago!)

nathusius commented 3 years ago

Same mine is stuck on “ your computer is starting the block chain and nothing happens please guide @hi10bha Can you check if the "pi-consensus" container is running OK in Docker? Also take a look at some of the other recent Issues threads, you might find some ideas there!

ihatejam commented 3 years ago

@hi10bha I used the "Remove blockchain data" button after updating to 0,4.4. It started over at block one, where it paused for about 30 mins, after which it counted up to the current block in almost no time. (Removing the old data and starting over with the API service disabled will save you loads of disk space and possibly even processing resources - previous versions had the API service enabled by default)

hi10bha commented 3 years ago

Thanks, I'll check it out.

On Sun, 9 May 2021 at 16:02, ihatejam @.***> wrote:

@hi10bha https://github.com/hi10bha I used the "Remove blockchain data" button after updating to 0,4.4. It started over at block one, where it paused for about 30 mins, after which it counted up to the current block in almost no time. (Removing the old data and starting over with the API service disabled will save you loads of disk space and possibly even processing resources - previous versions had the API service enabled by default)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/119#issuecomment-835776811, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS6CQ63LJCROYEFCYCTW2FLTMZQDDANCNFSM44M6ICUA .

-- Everybody is born Right handed, Only gifted overcome it.

remzicirit commented 3 years ago

@hi10bha I used the "Remove blockchain data" button after updating to 0,4.4. It started over at block one, where it paused for about 30 mins, after which it counted up to the current block in almost no time. (Removing the old data and starting over with the API service disabled will save you loads of disk space and possibly even processing resources - previous versions had the API service enabled by default)

I did that availability went down not up going down is probably because I restarted docker service. At least I know it is working even though it is not right

ihatejam commented 3 years ago

@hi10bha is it still stuck on "your computer is starting the blockchain"? This is was what i was trying to help you overcome - not the availability part.

hi10bha commented 3 years ago

Yes, it is.

On Mon, 10 May 2021 at 02:06, ihatejam @.***> wrote:

@hi10bha https://github.com/hi10bha is it still stuck on "your computer is starting the blockchain"? This is was what i was trying to help you overcome - not the availability part.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/119#issuecomment-835882907, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS6CQ666EA4OEYLBKBCU3JLTM3W5HANCNFSM44M6ICUA .

-- Everybody is born Right handed, Only gifted overcome it.

nathusius commented 3 years ago

Hi. Since upgrading to the new Node software I notice it's not updating my availability every day like before. It's been stuck for the last few days! Any ideas?

My availability has updated again this morning, but it only seems to do that every 3~4 days, so definitely less frequent now!

steeveee100 commented 3 years ago

Thanks @nathusius I'm afraid the availability issue is now low on my priority list. After upgrading to 0.4.4 I took some advice to Remove my Blockchain data, thinking I would end up with a leaner system. Instead it seemed to muck everything up and I ended up with the dreaded continual "starting up the blockchain" message for 2 days, everything under consensus saying N/A!!

I tried reinstalling Docker and WSL 2 yesterday and nothing has changed. So I'm back looking for help! ( Some screenshots to follow soon)

steeveee100 commented 3 years ago

Screenshot 2021-05-11 155259 Screenshot 2021-05-11 155128 Screenshot 2021-05-11 155517 And here are my screenshots! All help really appreciated. ###

steeveee100 commented 3 years ago

Would love it if one of you guys with a properly working node could post a screenshot of your logfile as above. Just to compare.......

nathusius commented 3 years ago

@steeveee100 Here's my screen grabs, looks pretty similar, but I have a lines saying "spawned: postgresql" and the corresponding "success" - no idea why, sorry! The consensus container log shows two restarts: yesterday (Docker 3.3.1) and today after updating to latest Docker 3.3.3. Not sure that I can offer any advice, but let me know if you need any other info

containers

pi node

container log

steeveee100 commented 3 years ago

Thanks @nathusius. I’ll have a good look later!

On Tue, 11 May 2021 at 17:04, nathusius @.***> wrote:

@steeveee100 https://github.com/steeveee100 Here's my screen grabs, looks pretty similar, but I have a lines saying "spawned: postgresql" and the corresponding "success" - no idea why, sorry! The consensus container log shows two restarts: yesterday (Docker 3.3.1) and today after updating to latest Docker 3.3.3. Not sure that I can offer any advice, but let me know if you need any other info

[image: containers] https://user-images.githubusercontent.com/59148361/117847995-c4a78800-b27a-11eb-865e-bebae55ac269.png

[image: pi node] https://user-images.githubusercontent.com/59148361/117848037-ce30f000-b27a-11eb-87b5-dc2143456cf3.png

[image: container log] https://user-images.githubusercontent.com/59148361/117848058-d2f5a400-b27a-11eb-92c2-14922adb2a2d.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/119#issuecomment-838744658, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATVIU6MM2SFFLASZ7ACVCT3TNFIPFANCNFSM44M6ICUA .

hi10bha commented 3 years ago

Updated to new version of docker, quit the node start docker and start pi node . Worked fine absolutely. Now everything is synched.

Thanks everyone

On Tue, 11 May 2021 at 23:17, steeveee100 @.***> wrote:

Thanks @nathusius. I’ll have a good look later!

On Tue, 11 May 2021 at 17:04, nathusius @.***> wrote:

@steeveee100 https://github.com/steeveee100 Here's my screen grabs, looks pretty similar, but I have a lines saying "spawned: postgresql" and the corresponding "success" - no idea why, sorry! The consensus container log shows two restarts: yesterday (Docker 3.3.1) and today after updating to latest Docker 3.3.3. Not sure that I can offer any advice, but let me know if you need any other info

[image: containers] < https://user-images.githubusercontent.com/59148361/117847995-c4a78800-b27a-11eb-865e-bebae55ac269.png

[image: pi node] < https://user-images.githubusercontent.com/59148361/117848037-ce30f000-b27a-11eb-87b5-dc2143456cf3.png

[image: container log] < https://user-images.githubusercontent.com/59148361/117848058-d2f5a400-b27a-11eb-92c2-14922adb2a2d.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/pi-node/instructions/issues/119#issuecomment-838744658 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ATVIU6MM2SFFLASZ7ACVCT3TNFIPFANCNFSM44M6ICUA

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/119#issuecomment-838899975, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS6CQ634RTGLGEWFSWEKWFTTNFUU3ANCNFSM44M6ICUA .

-- Everybody is born Right handed, Only gifted overcome it.

steeveee100 commented 3 years ago

Hey guys! I took the plunge and hit the "Remove all blockchain data" button again this morning. And unexpectedly that kicked everything into action! Sat on Block 1 for at least an hour then rocketed up to full capacity. Yippeee!

gjstein101 commented 3 years ago

Thanks steevee100 - As last resort I also "remove all blockchain data" and everything started to work.

hellohp-Ping commented 3 years ago

I also have Pi Node availability issue. My Pi node runs 24/7, but availability seems stopped every 4-5 days, then it started with even lower availability number.

nathusius commented 3 years ago

Yes, it seems to be a general issue, though not really a big problem - just leave it running as you are and hope to get selected as a node soon, that's what I did! Availability figure updates have definitely slowed down and the numbers are suspect anyway - I am running the node 24/7 and last update was actually less than before. All the diagnostics (port checker, etc) are a bit flaky, so just ignore it!!

hellohp-Ping commented 3 years ago

Thanks !

On May 21, 2021, at 3:25 PM, nathusius @.***> wrote:

 Yes, it seems to be a general issue, though not really a big problem - just leave it running as you are and hope to get selected as a node soon, that's what I did! Availability figure updates have definitely slowed down and the numbers are suspect anyway - I am running the node 24/7 and last update was actually less than before. All the diagnostics (port checker, etc) are a bit flaky, so just ignore it!!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.