search

pi-node / instructions

259 stars 185 forks source link

Since update of docker and pi node app to 0.4.11 impossible to get pi node to work for more than a few minuttes #378

Open DocTRM opened 2 months ago

DocTRM commented 2 months ago

Hi I ve upgraded to PI node 0.4.11 and lates docker version after that followed all instructions to open the ports 31400-31409 but without success. Only possible to reboot the laptop, after each reboot Node app runs nicely for a few minuttes and syncs etc to latest block but after perhaps 10 min the docker pi-consensus stoppes bhy it self and pi node stops running. After stopping nothing seems to affect pi node and it reports all ports closed (31400-31409) . Than rebooting and the cycle repeats Anyone any idea on whats going on?

MingYanWu commented 2 months ago

pi-consensus-stub Container error https://github.com/pi-node/instructions/issues/367 You can follow this article to reset it

DocTRM commented 2 months ago

pi-consensus-stub Container error #367 You can follow this article to reset it

Thanks for your comment referring to this thead , i couldnt download whale ver 4.19 but 4.24 as oldest version available , tried all above even disabling completely the firewall, still cant get open ports nor the PI node app to run correctly as stated earlier it starts ok with new boot but after syncing upto current block it disconnects some how and im back to zero, quiet annoying as this came with latest updates of whale and pi node app....

DocTRM commented 2 months ago

Still no success, as the PI- Node prog does not accept anything else then starting the Pi-Consensus container by itself and runs for a short while thereafter again the Pi-Consensus stub vicious cycle until one actually stops the pi node app completely and restarts it for a new cycle with a very short period where pi-node app actually has synced and is running. Its definitively a huge bug in pi-node app ver 0.4.11 which i hope the developers can address shortly, thanks

DXInfinity commented 2 months ago

This lasts for two months at least.. devs don't care. P.S. Experiencing exactly the same issue. I could make it working and synchronized by starting container by Pi App and then killing it (so it won't kill container) but no node bonus in this case and it makes no sense to run container without app.

ziyouniaoseo commented 2 months ago

Delete or stop the 'upgrade-pi node app container' so that it can run normally.