Stuck at 549722

[mhps]

https://bcblockexplorer.com/ is stuck at 549722 and my raspi is stuck at 549661. it gets new blocks and orphans them. 6 connections. peers are up to date at 55xxxx.

[cryptog]

Mine is fine at 553040 .

[mhps]

I copied bl*.dat databse/*.log from a sync’ed node to the Pi and now teh Pi is stuck at 552059.
debug.log has many of these even after cleared up datafeed and vote:

received block 5e98d5a67ded4eeef41693aadf57aa7e574f29fbc54c089abb6f664b8d3e9b33
ERROR: AddToBlockIndex() : Invalid vote
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
r

[Cybnate]

Not seeing these errors is my debug.log. So it is likely to be RaPi specific or something with your votes config maybe?

[mhps]

I have been subscribing from a feed. fter seeing the error i have cleaned up but still get error

   ./bcexchanged getvote
    {
        "versionvote" : "5.0",
        "custodians" : [
        ],
        "parkrates" : [
        ],
        "motions" : [
        ],
        "fees" : {
        },
        "reputations" : [
        ],
        "signerreward" : {
            "count" : null,
            "amount" : null
        },
        "assets" : [
        ]
    }
    
./bcexchanged getdatafeed
    {
        "url" : "",
        "signatureurl" : "",
        "signatureaddress" : "",
        "parts" : "custodians,parkrates,motions,fees,reputations,signerreward,signerreward,assets"
    }

Any idea? @sigmike

[Cybnate]

I’m seeing that signerreward occurs twice in your getdatafeed output. Looks odd.

[sigmike]

received block 5e98d5a67ded4eeef41693aadf57aa7e574f29fbc54c089abb6f664b8d3e9b33
ERROR: AddToBlockIndex() : Invalid vote

This block’s vote is very similar to the previous one (at height 552251). Is this the first block you received after you started the node? What’s the block height of your node? Are you sure you run version 5.0? That would be the behavior of a 4.x client.

[mhps]

signerreward occurs twice i

wow i didn’t see it. I cleared feed by setdatafeed "" which according to help setdatafeed should

setdatafeed <url> [<signature url> <address>] [<parts>]
Change the vote data feed. Set <url> to an empty string to disable.

So setdatafeed "" doesn’t clean up all fields in voting parameters.

I manually set the parts string to the default (no repeated ones) and it does not solve the problem.

What’s the block height of your node? Are you sure you run version 5.0? That would be the behavior of a 4.x client.

It’s 5.0.1

 ./bcexchanged getinfo
{
    "version" : "v5.0.1-beta",
    "protocolversion" : "5.0",
    "walletversion" : 1,
    "walletunit" : "8",
    "balance" : xx,
    "newmint" : 0.0,
    "stake" : xx,
    "parked" : 0.0,
    "blocks" : 552059,
    "moneysupply" : 187121.8448,
    "connections" : 6,
    "proxy" : "",
    "ip" : "xxx",
    "difficulty" : 0.0004359,
    "testnet" : false,
    "keypoololdest" : 1437027284,
    "keypoolsize" : 101,
    "paytxfee" : 0.01,
    "unlocked_until" : 0,
    "errors" : "Info: Minting suspended due to locked portfolio."
}

[sigmike]

This block’s vote is very similar to the previous one (at height 552251).

Actually this vote includes a downvote, unlike the previous one.

[mhps]

there is a 4.0 and a stuck 5.0 in the peers.

i have leave for several hours.

 ./bcexchanged getpeerinfo
[
    {
        "addr" : "91.64.162.69:2239",
        "services" : "00000001",
        "lastsend" : 1469612907,
        "lastrecv" : 1469612907,
        "conntime" : 1469610985,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 553434,
        "banscore" : 0
    },
    {
        "addr" : "108.61.192.179:2239",
        "services" : "00000001",
        "lastsend" : 1469612907,
        "lastrecv" : 1469612907,
        "conntime" : 1469610986,
        "version" : 4000000,
        "subver" : "/Siglee:4.0.0/B&C Exchange:4.0.0(v4.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 553434,
        "banscore" : 0
    },
    {
        "addr" : "120.24.210.125:2239",
        "services" : "00000001",
        "lastsend" : 1469612787,
        "lastrecv" : 1469612787,
        "conntime" : 1469610990,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 553434,
        "banscore" : 0
    },
    {
        "addr" : "62.210.15.44:2239",
        "services" : "00000001",
        "lastsend" : 1469612667,
        "lastrecv" : 1469612776,
        "conntime" : 1469611013,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 553434,
        "banscore" : 0
    },
    {
        "addr" : "178.32.217.85:2239",
        "services" : "00000001",
        "lastsend" : 1469612187,
        "lastrecv" : 1469612774,
        "conntime" : 1469611070,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 553436,
        "banscore" : 0
    },
    {
        "addr" : "107.170.243.142:2239",
        "services" : "00000001",
        "lastsend" : 1469611234,
        "lastrecv" : 1469611235,
        "conntime" : 1469611234,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 551626,
        "banscore" : 0
    }
]

[Cybnate]

Interesting, I have the exact same 6 peers. Feels abandoned. The B&C blockexplorer reported 30+ but unfortunately is stuck now.

[sigmike]

Actually this vote includes a downvote, unlike the previous one.

It may be a serialization problem of negative values on the raspberry pi. I’ll have access to one later today and I’ll look into that.

[GreatScott]

Confirming that my RPi on 5.0.1 is stuck also:

    "blocks" : 549557,
    "moneysupply" : 187095.4548,
    "connections" : 6,

[
    {
        "addr" : "107.170.243.142:2239",
        "services" : "00000001",
        "lastsend" : 1469619232,
        "lastrecv" : 1469619232,
        "conntime" : 1469547192,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 551626,
        "banscore" : 0
    },
    {
        "addr" : "178.32.217.85:2239",
        "services" : "00000001",
        "lastsend" : 1469620460,
        "lastrecv" : 1469620497,
        "conntime" : 1469547193,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 552243,
        "banscore" : 0
    },
    {
        "addr" : "91.64.162.69:2239",
        "services" : "00000001",
        "lastsend" : 1469620497,
        "lastrecv" : 1469620497,
        "conntime" : 1469547194,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 552243,
        "banscore" : 0
    },
    {
        "addr" : "62.210.15.44:2239",
        "services" : "00000001",
        "lastsend" : 1469620380,
        "lastrecv" : 1469620410,
        "conntime" : 1469547195,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 552243,
        "banscore" : 0
    },
    {
        "addr" : "120.24.210.125:2239",
        "services" : "00000001",
        "lastsend" : 1469620410,
        "lastrecv" : 1469620498,
        "conntime" : 1469601147,
        "version" : 5000000,
        "subver" : "/Siglee:5.0.1/B&C Exchange:5.0.1(v5.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 553274,
        "banscore" : 0
    },
    {
        "addr" : "108.61.192.179:2239",
        "services" : "00000001",
        "lastsend" : 1469620461,
        "lastrecv" : 1469620497,
        "conntime" : 1469611943,
        "version" : 4000000,
        "subver" : "/Siglee:4.0.0/B&C Exchange:4.0.0(v4.0.1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 553453,
        "banscore" : 0
    }
]

Ubuntu BC installation is current

[mhps]

My Rasp-pi worked well until several days ago.

[GreatScott]

Maybe the 7 of us should keep minting, and change the name to B&C Classic?

[mhps]

Be careful what you wish,

[Sabreiib]

I discarded my Raspberry after SD card not working and returned to desktop with linux, but the connection is 6 not 8.

[mhps]

I discarded my Raspberry after SD card not working and returned to desktop with linux, but the connection is 6 not 8.

seems to fail in ~2-3 months (Sandisk TF card). I have has twice. I see the wallet is flushed every a few blocks received. Can I hack the code somewhere so that flushing is done once 10 blocks? @sigmike

[Sabreiib]

Discard rubbish hardward, Raspberry CPU, SD drive are terrible poor, even my old iphone has several times performance of it.

I am curious about the ios jailbreak, don’t know whether GCC is still workable on iphone.

[sigmike]

I see the wallet is flushed every a few blocks received. Can I hack the code somewhere so that flushing is done once 10 blocks?

By reading the code it looks like the wallet is flushed when the wallet is updated (for example when a related transaction is received), not when blocks are received. So if you’re minting and not doing anything else it should only flush when you find a block.

There’s already some code that prevents flushing if it was already done less than 2 seconds ago. An easy way to make it happen less frequently would be to increase that number. If you’re only minting this should be harmless since everything you do is recorded on the blockchain or orphaned. But if you actually use your wallet this is probably not a good idea.