Quote from: ferment on January 05, 2014, 02:15:07 PM

Quote from: nadrimajstor on January 05, 2014, 04:09:36 AM

Quote from: ferment on January 04, 2014, 02:35:47 PM

Quote from: nadrimajstor on January 04, 2014, 01:14:04 PM

Quote from: nadrimajstor on January 04, 2014, 01:53:49 AM

Its been more than a day that public nodes respond with:

Code:

for N in {1..100}; do curl --silent "http://node$N.nxtbase.com:7874/nxt?requestType=getState" | python -m json.tool | grep '"lastBlock"'; done

Other nodes that accept public request returns, what appears to be a valid lastBlock...
However, all public node*.nxtbase.com nodes, for days, still returns same lastBlock 2680262203532249785. Undecided

I'm working on this. They seem to have gotten stuck after the upgrade yesterday.

Still stuck... Cry

Thanks for checking. I'm installing 0.5.0. It seems they still are stuck at 0 and won't receive the blockchain. Should be able to go through it this afternoon once our guests leave.

Found a bug in my *.nxt caching strategy. Nodes are all catching up now and deployed with 0.5.0.