[ANN] Noirbits TAKEOVER ! Update v2.2.5.0 - fixes sync issue

[stbgefltc]

Lol, pay me and ill fix it or at least have a look and tell you what's wrong

500 NRB if you find the issue before I do. Winner will be settled by pull request time on Noirbits repository (or commit time of fix).

[rovchris]

Not sure what this peer is doing - looks like it could be causing issues though

{
"addr" : "72.78.100.7:55884",
"services" : "00000001",
"lastsend" : 1376409243,
"lastrecv" : 1376409243,
"conntime" : 1376407441,
"version" : 60001,
"subver" : "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}

[barwizi]

a temporary fix, would be to limit the client to a few, only the good nodes until an update that completely cuts them off is pushed.

The issue has nothing to do with a rogue node. Even when syncing with known, proper nodes, the issue arises.

if you are certain. good luck on your competition, would be nice if this was run on testnet using cpu's for interested people. That way it can be used to test out new ideas and updates with a lot of peers involved before it goes mainstream.

[kalgecin]

a temporary fix, would be to limit the client to a few, only the good nodes until an update that completely cuts them off is pushed.

The issue has nothing to do with a rogue node. Even when syncing with known, proper nodes, the issue arises.

if you are certain. good luck on your competition, would be nice if this was run on testnet using cpu's for interested people. That way it can be used to test out new ideas and updates with a lot of peers involved before it goes mainstream.

competition? testnet for testing new ideas? huh?

[jasinlee]

Ok looks like its on the git, anyone able to compile it for windows too?

[MobGod]

Ok looks like its on the git, anyone able to compile it for windows too?

what do you mean on the git want me to try this again i didn't have a problem with the compile i had the problem with the chain getting stuck

[kalgecin]

Ok looks like its on the git, anyone able to compile it for windows too?

what do you mean on the git want me to try this again i didn't have a problem with the compile i had the problem with the chain getting stuck

I've fixed that

[MobGod]

Ok looks like its on the git, anyone able to compile it for windows too?

what do you mean on the git want me to try this again i didn't have a problem with the compile i had the problem with the chain getting stuck

I've fixed that

stuck again

./Noirbitsd getinfo
{
    "version" : 2020300,
    "protocolversion" : 60002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 29069,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 1.48791009,
    "testnet" : false,
    "keypoololdest" : 1376244053,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,

[kalgecin]

hmm.... can you provide last 100 lines of debug.log please?

[MobGod]

hmm.... can you provide last 100 lines of debug.log please?

When I get home yes I will

[kalgecin]

hmm.... can you provide last 100 lines of debug.log please?

When I get home yes I will

did you try to clear the blockchain?

[kalgecin]

also try restarting the client, so that it gets new peers. some people didn't update yet :-(

[kalgecin]

addnode 212.92.177.74

[stbgefltc]

Thanks Kalgecin for your work, looks like the competition is over . Clients v.2.2.3.0 should not have synchronization issues anymore, if you get stuck synchronizing, try restarting your client, it does sometimes help, if not, check your debug.log file, there's useful info in there.

I'm off to work, and was away last evening, so compiled Windows binaries will be available soon, but not until I get home.

[stbgefltc]

a temporary fix, would be to limit the client to a few, only the good nodes until an update that completely cuts them off is pushed.

The issue has nothing to do with a rogue node. Even when syncing with known, proper nodes, the issue arises.

if you are certain. good luck on your competition, would be nice if this was run on testnet using cpu's for interested people. That way it can be used to test out new ideas and updates with a lot of peers involved before it goes mainstream.

Isn't that the whole idea of testnet ? 

[oatmo]

Can someone post 2.2.3.0 to mega, it's only got 2.2.2.0..

Oatmo

[barwizi]

a temporary fix, would be to limit the client to a few, only the good nodes until an update that completely cuts them off is pushed.

The issue has nothing to do with a rogue node. Even when syncing with known, proper nodes, the issue arises.

if you are certain. good luck on your competition, would be nice if this was run on testnet using cpu's for interested people. That way it can be used to test out new ideas and updates with a lot of peers involved before it goes mainstream.

Isn't that the whole idea of testnet ? 

i mean having a permanent running testnet.

[stbgefltc]

Can someone post 2.2.3.0 to mega, it's only got 2.2.2.0..

Oatmo

When I get home from work I will, unless someone's willing to compile for Windows until then. I don't have a mingw stack at work, so it'll have to wait, sorry

[stbgefltc]

Ok looks like its on the git, anyone able to compile it for windows too?

what do you mean on the git want me to try this again i didn't have a problem with the compile i had the problem with the chain getting stuck

I've fixed that

stuck again

./Noirbitsd getinfo
{
    "version" : 2020300,
    "protocolversion" : 60002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 29069,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 1.48791009,
    "testnet" : false,
    "keypoololdest" : 1376244053,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,

Did you manage to sync in the end ?

[Aaed]

Client 2.2.2 seem to sync quite well for me.