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
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",
"lastBlock": "2680262203532249785",

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

nadrimajstor

Posts

Merits