Topic: [TEST RELEASE] Cryptonite binary for linux (NEW: Qt and Windows builds) - page 15. (Read 19307 times)

boooo!

no wait,
yea! Been out of town on a much needed vacation... now its almost kill the English day so works out well.

Sorry we've been so quiet the last few days, we're taking a short break from development but we should get back to it in a few days. Still a bit of work to be done but we're much closer to our goal now.

I have been busy the last couple of days but will have time this weekend to do more testing.

Ok, so if I understand you correctly, I can delete my data dir and restart and it will sort itself out?


Like you need the help sir.

So the deal is. If your block count is ever more than 1000 away from the header count it won't be able to sync. Partly because of a bug where it won't even try, partly because other nodes may not even have the missing data. However the warning goes off if the point you originally synced is more than 1000 from the current tip which is almost always true. Currently we don't have an option to do the resyncing without deleting the folder. Bitfreak thinks it should even be done automatically. I think resync is kind of a drastic thing to do without at least talking to the user about it.

If this is the worst problem you are having we are probably doing pretty well. It's mostly a matter of developing better UI for when it is synced etc.

you call it embarrassment i call it opportunity to poke fun at you 

ok Billo is right, there is something wrong:

getmininginfo:

"blocks" : 13957,
    "currentblocksize" : 143520,
    "currentblocktx" : 999,
    "difficulty" : 1.00000000,
    "errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications",
    "genproclimit" : 1,
    "networkhashps" : 59634,
    "pooledtx" : 1002,
    "testnet" : true,
    "generate" : true,
    "hashespersec" : 30957


then i am also seeing this:
Accept block header
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 14086 16725 16725 17725 0
OS 13958 NS 13958
Update: 13958 17725 16725 17725 1
Accepted block 13958
Accept block header
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 14086 16725 16725 17725 0
OS 13958 NS 13958
Update: 13958 17725 16725 17725 1
Accepted block 13958
Accept block header
Update: 17726 16726 16726 17726 0
Update: 16726 16726 16726 17726 0
Update: 17726 16726 16726 17726 0
Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!
Accept block header
Update: 17726 16726 16726 17726 0
Update: 16726 16726 16726 17726 0
Update: 13958 17726 16726 17726 1
Update: 14086 16726 16726 17726 0
OS 13958 NS 13958
Update: 17726 17726 16726 17726 1
Accepted block 17726
Accept block header
Update: 17727 16727 16727 17727 0
Update: 16727 16727 16727 17727 0
Update: 17727 16727 16727 17727 0
Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!
Accept block header
Update: 17727 16727 16727 17727 0
Update: 16727 16727 16727 17727 0
Update: 13958 17727 16727 17727 1
Update: 14086 16727 16727 17727 0
OS 13958 NS 13958
Update: 17727 17727 16727 17727 1
Accepted block 17727

except my block count is not increasing in my getinfo... im getting headers, but not processing blocks.

[edit] and ffs have I done anything but embarrass myself in this thread? lol

Billo, look above and you will find the answer (to life the universe and everything). Peace my brother

my client seems stuck @ block 14022.

Log looks clean but I noticed this in the console output:


Does this mean I need to delete the blockchain and start over?

@mrvegad don't worry about that. just a warning that doesn't print out at the right time yet.

@cawson no IPO's or anything. trying for a fair launch

the coin will ipo or not？

Output error:Warning: saved state too old. Fast forward sync may not be possible. Run Resync!

log file https://mega.co.nz/#!Vpc21baJ!JO71UzypRkpNf2ikAgqk_ejWyVisNnoy4s6yttdlHLk

I am having problems with blocks. Will post log and more info when i get off work.

I didn't monitor it much this weekend but this morning it seemed like the client had froze up. I tried a getinfo and nothing happened before I had to leave for work soooo maybe?

does this mean you haven't managed to break it yet?

mzWZMszmtp2oScRxvSKCZ8ZSCNFQNZqMzY

mvLpTpus6gKcLRMvs72qUnvjXaoUAebxaV

There is a serious bug in orphan resolution. Good news is that I can reproduce it easily right now. I'll fix it later tonight, until then primary node is offline and experiment halted.

[Edit] I actually fixed something for once. No more disappearing blocks and orphans working well. d9204e91683f871ab8f9c638427fa71a  Let the games begin when you get a chance. Thanks all.

I asked catia about the "Ready for committal" thing and he said it only shows that on the first time. As for that error in the log, it looks like it might just be someone sending you a transaction your already have or something, but we'll have to wait for catia to take a look at it to be sure though. I assume getinfo and other commands are still working for you?