Bible Pay

Read 17093 times

  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #165 on: December 28, 2018, 07:22:29 pm »
Ive had my testnet nodes down for 2 1/2 days - I just made an attempt at resyncing - anyone up to provide a blockhash?



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #166 on: December 28, 2018, 07:33:10 pm »
I'm the only one showing in the pool in testnet,  but I don't seem to be getting any rewards from the pool (just the mining rewards)

Yeah, if you are by yourself, your node is probably mining every block, and also paying you 100% of the tier payment block also.  You would have to pull up your txid and type 'getrawtransaction txid 1' to see it.





  • thesnat21
  • Administrator

    • 163


    • 15
    • March 28, 2018, 06:37:05 pm
    more
Re: Testnet - Test Proof of Giving
« Reply #167 on: December 28, 2018, 08:52:15 pm »
Ive had my testnet nodes down for 2 1/2 days - I just made an attempt at resyncing - anyone up to provide a blockhash?

I've not been able to get blocks for a while


  • sunk818
  • Full Member

    • 248


    • 7
    • April 24, 2018, 02:02:20 pm
Re: Testnet - Test Proof of Giving
« Reply #168 on: December 28, 2018, 10:51:35 pm »
Someone is running 1173 is that you Rob? I finally got peers. One test node seems to be okay but other two are just solo mining blocks with no peers


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #169 on: December 29, 2018, 10:50:28 am »
Someone is running 1173 is that you Rob? I finally got peers. One test node seems to be okay but other two are just solo mining blocks with no peers
Yeah, 1.1.7.3 is why Ive been MIA for 2 1/2 days, yes its me.  It does not have any POG changes in it however.

Anyway, I see the problem in general in testnet.  When we have less than 3 nodes with a consensus, the nodes arent trusting each other to download blocks.  The other problem is chainstate contains a few too many chain tip problems (IE some blocks appear to be marked as bad from all these upgrades).

What we need to do is restart with -reindex (but not by deleting the chainstate and the blocks) and let it resync - that clears all the boolean masks on each block and then we should trust each other again.

Let me post a blockhash, I just reindexed 3 and they seem to be syncing up properly now.



getblockhash 96825


cf0e35c7142f305cfa3ff8efc3740b74d42e550d4d66975fc1207762a73ac566




  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #170 on: December 29, 2018, 01:09:47 pm »
Im synced on all my nodes now (after -reindex worked), but dont see TheSnat or anyone else yet - you guys are probably on all different chains.

Once we all get on the same chain Ill check the logs after that point.



  • thesnat21
  • Administrator

    • 163


    • 15
    • March 28, 2018, 06:37:05 pm
    more
Re: Testnet - Test Proof of Giving
« Reply #171 on: December 29, 2018, 04:22:49 pm »
relaunched all my clients.

seem to be getting blocks, cool!


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #172 on: December 29, 2018, 06:14:37 pm »
I havent seen any crashing...

Just an FYI, a crash means the program actually ended (IE segfaulted).

If this happens please run it in valgrind.



  • thesnat21
  • Administrator

    • 163


    • 15
    • March 28, 2018, 06:37:05 pm
    more
Re: Testnet - Test Proof of Giving
« Reply #173 on: December 29, 2018, 07:01:10 pm »
I had 2 clients with hash of cd92bf4727388a839ef25c8dfc33879cebd034a7863fcfd32a5a09222a9d96c6 for your block.

trying the reindex


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #174 on: December 29, 2018, 07:13:45 pm »
I had 2 clients with hash of cd92bf4727388a839ef25c8dfc33879cebd034a7863fcfd32a5a09222a9d96c6 for your block.

trying the reindex

Yeah I saw that we had one fork; but I also saw looking at peers we had 5 not reindex and 5 indexed so its a crapshoot on what was going on - lets see if after you reindex we take another look and see if we can have a consistent 24 hours.

It should be apparent if pog diff stays relatively smooth (IE 20K+).  However I noticed on my two whale boxes, Im running out of tithe money (I have 25 tithes left at this diff level on each box).



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #175 on: December 29, 2018, 07:17:22 pm »
Yeah I saw that we had one fork; but I also saw looking at peers we had 5 not reindex and 5 indexed so its a crapshoot on what was going on - lets see if after you reindex we take another look and see if we can have a consistent 24 hours.

It should be apparent if pog diff stays relatively smooth (IE 20K+).  However I noticed on my two whale boxes, Im running out of tithe money (I have 25 tithes left at this diff level on each box).

Actually to elaborate when I first reindexed I had that hash, then my 3 nodes reorged and I did start getting Your hash (cd9) on all nodes.  Just to start this process over again, here is my new hash:


19:16:14

getblockhash 97175


19:16:14

bd0a9e17647121f030d406e05458894ef595127a64340b8d2defb05f82c3eab3


Pog Diff is around 20K.



  • thesnat21
  • Administrator

    • 163


    • 15
    • March 28, 2018, 06:37:05 pm
    more
Re: Testnet - Test Proof of Giving
« Reply #176 on: December 29, 2018, 07:31:04 pm »
Actually to elaborate when I first reindexed I had that hash, then my 3 nodes reorged and I did start getting Your hash (cd9) on all nodes.  Just to start this process over again, here is my new hash:


19:16:14

getblockhash 97175


19:16:14

bd0a9e17647121f030d406e05458894ef595127a64340b8d2defb05f82c3eab3


Pog Diff is around 20K.

Got that hash on the block explorer machine..

The other 2 crashed,  this is debug log from one, will grab the other if it does.  (this is during the reindex)

Code: [Select]
2018-12-30 01:25:47  Finished Loading Block Index 1546133147.000000 LoadBlockIndexDB: hashBestChain=698ac2d570dd63a89758c396681ca3ae8cab5f14323384d28959a55fcd878922 height=54303 date=2018-09-01 20:09:11 progress=0.163178
2018-12-30 01:25:47 init message: Verifying blocks...
2018-12-30 01:25:47 Verifying last 288 blocks at level 3
2018-12-30 01:25:48 No coin database inconsistencies in last 289 blocks (352 transactions)
2018-12-30 01:25:48  block index           13065ms
2018-12-30 01:25:48 init message: Loading wallet...
2018-12-30 01:25:48 nKeysLeftSinceAutoBackup: 1000
2018-12-30 01:25:48 nFileVersion = 1010702
2018-12-30 01:25:48 Keys: 2135 plaintext, 0 encrypted, 2135 w/ metadata, 2135 total
2018-12-30 01:25:49  wallet                  328ms
2018-12-30 01:25:49 init message: Activating best chain...
2018-12-30 01:25:49 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=0, nPos=25459402), Context CONNECTTIP
2018-12-30 01:25:49 *** Failed to read block



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #177 on: December 30, 2018, 12:37:25 am »
Got that hash on the block explorer machine..

The other 2 crashed,  this is debug log from one, will grab the other if it does.  (this is during the reindex)

Code: [Select]
2018-12-30 01:25:47  Finished Loading Block Index 1546133147.000000 LoadBlockIndexDB: hashBestChain=698ac2d570dd63a89758c396681ca3ae8cab5f14323384d28959a55fcd878922 height=54303 date=2018-09-01 20:09:11 progress=0.163178
2018-12-30 01:25:47 init message: Verifying blocks...
2018-12-30 01:25:47 Verifying last 288 blocks at level 3
2018-12-30 01:25:48 No coin database inconsistencies in last 289 blocks (352 transactions)
2018-12-30 01:25:48  block index           13065ms
2018-12-30 01:25:48 init message: Loading wallet...
2018-12-30 01:25:48 nKeysLeftSinceAutoBackup: 1000
2018-12-30 01:25:48 nFileVersion = 1010702
2018-12-30 01:25:48 Keys: 2135 plaintext, 0 encrypted, 2135 w/ metadata, 2135 total
2018-12-30 01:25:49  wallet                  328ms
2018-12-30 01:25:49 init message: Activating best chain...
2018-12-30 01:25:49 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=0, nPos=25459402), Context CONNECTTIP
2018-12-30 01:25:49 *** Failed to read block


Size too large means the block index is > 32 mb, meaning the block file is corrupted.  In this case you must kill the files and re-sync the chain.

This is a normal assert they put in for a corruption sanity check.


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #178 on: December 30, 2018, 10:46:10 am »
Good news, on my dev node running Pog I finally encountered a crash.  Btw, even though I was not running valgrind and the log is not useful, if you ever see a message printed on the console during the crash, that is useful.

In this case it was "An exception of UniValue was thrown and terminate called". 

Im running it in valgrind now - lets hope this is the same thing Sun reported.

If anyone else has crashed please run in valgrind - lets find the line #.



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet - Test Proof of Giving
« Reply #179 on: December 30, 2018, 12:17:29 pm »
Good news, on my dev node running Pog I finally encountered a crash.  Btw, even though I was not running valgrind and the log is not useful, if you ever see a message printed on the console during the crash, that is useful.

In this case it was "An exception of UniValue was thrown and terminate called". 

Im running it in valgrind now - lets hope this is the same thing Sun reported.

If anyone else has crashed please run in valgrind - lets find the line #.

TheSnat found it first in valgrind.  The great news is this appears to be the same error (during mining) affecting all 3 of us.

The fix is completed and the new version is being compiled now...