Bible Pay

Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
Production Proposals / Re: Compensation for Jaap's work with BiblePay
« Last post by thesnat21 on September 20, 2018, 06:13:57 am »
Jaap,

New proposal should be a new thread so things don't get confused :)

32
So, just to make sure. Currently this proposal is now only for removal of the team-requirement. This will also involve blacklisting some teams (e.g. Gridcoin) and giving a penalty if you are not in team BiblePay (e.g. 50%).

So far, it's not clear which other teams will be excluded.  Hopefully this can be clarified before the proposal is finalized
33
So, just to make sure. Currently this proposal is now only for removal of the team-requirement. This will also involve blacklisting some teams (e.g. Gridcoin) and giving a penalty if you are not in team BiblePay (e.g. 50%).
34

Thats kind of cool; if you still have that node in that state, could you sudo apt-get install valgrind,  valgrind ./biblepay and see what line it breaks on?

If not we'll eventually figure it out, but you will probably have to reindex to get past it.

I seem to be back to normal on all nodes now.

I'll do my best to find that bug.  I know we fixed the major fork issue in this version, now we need a couple more minor things... checking.

Sorry, I already -reindexed it :(

But I've installed valgrind in case it ever happens again. Can't seem to get it working in all my noobness though... Could you tell me what specific command I should use?
35
After restarting the 85.29 node I got the same 'Segmentation fault' error that Togo got:

Code: [Select]
ERROR: Found block with no ancestor
2018-09-19 21:17:36 ERROR: Block has no ancestor.

2018-09-19 21:17:36 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-09-19 21:17:36 Misbehaving: 47.189.72.5:58842 (0 -> 3)
2018-09-19 21:17:36 ProcessNewBlock : ACCEPTED


Thats kind of cool; if you still have that node in that state, could you sudo apt-get install valgrind,  valgrind ./biblepay and see what line it breaks on?

If not we'll eventually figure it out, but you will probably have to reindex to get past it.

I seem to be back to normal on all nodes now.

I'll do my best to find that bug.  I know we fixed the major fork issue in this version, now we need a couple more minor things... checking.
36
Hmmm, my wallet crashed, v1.1.5.4b, I had upgraded, cleaned and reindexed
Code: [Select]
Segmentation fault (core dumped)
tail debug.log
Code: [Select]
ERROR: Block has no ancestor
Misbehaving: 84.29.208.33:62767
ERROR: invalid header received bd9004da***6d0fea
ERROR: Found block with no ancestor
ERROR: Block has no ancestor.
ERROR: ProcessNewBlock: AcceptBlock FAILED
Misbehaving: 84.29.208.33:62767

Im going to clean and reindex again

After restarting the 85.29 node I got the same 'Segmentation fault' error that Togo got:

Code: [Select]
ERROR: Found block with no ancestor
2018-09-19 21:17:36 ERROR: Block has no ancestor.

2018-09-19 21:17:36 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-09-19 21:17:36 Misbehaving: 47.189.72.5:58842 (0 -> 3)
2018-09-19 21:17:36 ProcessNewBlock : ACCEPTED
37
84.29 is running 1154.  I know that area of code, we crashed a couple times there in the past - there is even some code in there to try to prevent the crash.  Its really elusive because every time I hear this and try to valgrind it, there is no way to reproduce the exact situation again - I know it has something to do with having a lot of forks in your getchaintips.  I think one of the forks best block hashes is NULL to the wallet.  But we dont save NULL blocks in the map.  I did check Dash to see if they changed that but not yet.

That's one of my wallets :o

What is strange, is that that wallet is on the right block/chain, but it says it's not synced. I also have a Sanctuary on there, and I can't start it because it says it's not synched...
38
mnsync status
shows that Im synced now AssetID 999

getblockhash 67777
bd687ccb***0788387b2

Masternode is PRE_ENABLED

hashps: 0.135,
networkhashps: 178.888
39
Hmmm, my wallet crashed, v1.1.5.4b, I had upgraded, cleaned and reindexed
Code: [Select]
Segmentation fault (core dumped)
tail debug.log
Code: [Select]
ERROR: Block has no ancestor
Misbehaving: 84.29.208.33:62767
ERROR: invalid header received bd9004da***6d0fea
ERROR: Found block with no ancestor
ERROR: Block has no ancestor.
ERROR: ProcessNewBlock: AcceptBlock FAILED
Misbehaving: 84.29.208.33:62767

Im going to clean and reindex again

84.29 is running 1154.  I know that area of code, we crashed a couple times there in the past - there is even some code in there to try to prevent the crash.  Its really elusive because every time I hear this and try to valgrind it, there is no way to reproduce the exact situation again - I know it has something to do with having a lot of forks in your getchaintips.  I think one of the forks best block hashes is NULL to the wallet.  But we dont save NULL blocks in the map.  I did check Dash to see if they changed that but not yet.


40
Hmmm, my wallet crashed, v1.1.5.4b, I had upgraded, cleaned and reindexed
Code: [Select]
Segmentation fault (core dumped)
tail debug.log
Code: [Select]
ERROR: Block has no ancestor
Misbehaving: 84.29.208.33:62767
ERROR: invalid header received bd9004da***6d0fea
ERROR: Found block with no ancestor
ERROR: Block has no ancestor.
ERROR: ProcessNewBlock: AcceptBlock FAILED
Misbehaving: 84.29.208.33:62767

Im going to clean and reindex again
Pages: 1 2 3 [4] 5 6 7 8 9 10