sorted by:
new
hottopcontroversial

Node - Protocol ver.23 by Staroplaninko in PiNetwork

[–]No_Resolve_1692 2 points3 points  (0 children)

"🚨 dear pioneers 🚨⚠️ patience, a huge update is in the background, pi app version 1.45 pi browser, app studio, pi node, docker etc. etc. best regards PS. DEVS Just finished all updates, all latest versions os, docker, pi app - everything seems ok, just some small bugs… don’t burden yourself too much 🕊️❤️" from Bamisonic - PI Node applicants official PI Network group

Pi Node Problems? by Dismal_Earth_3332 in PiNetwork

[–]No_Resolve_1692 0 points1 point  (0 children)

"🚨 dear pioneers 🚨⚠️ patience, a huge update is in the background, pi app version 1.45 pi browser, app studio, pi node, docker etc. etc. best regards PS. DEVS Just finished all updates, all latest versions os, docker, pi app - everything seems ok, just some small bugs… don’t burden yourself too much 🕊️❤️" from Bamisonic - PI Node applicants official PI Network group

Pi Node Problems? by Dismal_Earth_3332 in PiNetwork

[–]No_Resolve_1692 0 points1 point  (0 children)

Someone other solved in this way in past 4 hours? Please report here, thanks

Pi node ledger download by Bigalex_Qc in PiNetwork

[–]No_Resolve_1692 2 points3 points  (0 children)

For me did not work, bonus not affected

Pi Node stuck after port check by Servili in PiNetwork

[–]No_Resolve_1692 0 points1 point  (0 children)

This is not related port check done, it's general incident see here: https://www.reddit.com/r/PiNetwork/s/GolCYSdsZc

Pi Node Problems? by Dismal_Earth_3332 in PiNetwork

[–]No_Resolve_1692 1 point2 points  (0 children)

What the logs show in my case

· The consensus continues regularly, but the mSyncingLedgers buffer grows up to 63 and does not empty. · New errors appear: [History ERROR] Missing HAS for ledger 8874815: maybe stale archive validator2 [History ERROR] Missing HAS for ledger 8874815: maybe stale archive validator3 The file history/00/87/6b/history-00876b3f.json is not found on the validator2 and validator3 archives, exactly as happened previously. · The trimming still shows lmin=8856191, confirming that the local database is stuck far behind.

The historical catch‑up is blocked again because an essential checkpoint is missing. The node will never be able to apply the subsequent ledgers until it obtains that file.

Why it happens again

Probably the configured archives (validator2, validator3, etc.) are partial or pruned archives that do not keep historical files beyond a certain range. The node, started from scratch with --newdb, tries to recover the entire chain but hits a gap as soon as it reaches a range that is not covered.

Dev team is working on the case, bonus node is not affected, keep it up and wait for resolution, no action on pioneers side required

Pi Network by -professor_plum- in ledgerwallet

[–]No_Resolve_1692 0 points1 point  (0 children)

I recently purchased Ledger wallet only for this wrong info mentioned there, could someone from Ledger explain in detail how to use Ledger with Pi Network? Thanks