noob101
Newbie
Offline
Activity: 41
Merit: 0
|
|
December 17, 2017, 03:00:36 PM |
|
Hi guys, Just a quick note. Please update the announcement on pool 2 to reflect correct block, seeing as we are past 21550 already. Keep up the good work. Still rooting for you.
|
|
|
|
daemonko
Newbie
Offline
Activity: 56
Merit: 0
|
|
December 17, 2017, 03:03:59 PM |
|
guys, i'm loosing my patience here, two mandatory updates in one day, come on...
- now, i updated 6 machines to the latest version (1.0.6.7), starting biblepayd shows CPU 0.0%, biblepay-cli getmininginfo shows pool mining = false. wtf? any ideas what to do? please help. previous udpates worked ok. i'm on pool2.
- there is no windows version for 1.0.6.7? will it come out soon?
- and btw, withdrawing from minersofmen does not work (invalid account error...) any hints here? i tried to email them, got no response...
|
|
|
|
crnewbie
Newbie
Offline
Activity: 17
Merit: 0
|
|
December 17, 2017, 03:13:10 PM |
|
guys, i'm loosing my patience here, two mandatory updates in one day, come on...
- now, i updated 6 machines to the latest version (1.0.6.7), starting biblepayd shows CPU 0.0%, biblepay-cli getmininginfo shows pool mining = false. wtf? any ideas what to do? please help. previous udpates worked ok. i'm on pool2.
- there is no windows version for 1.0.6.7? will it come out soon?
- and btw, withdrawing from minersofmen does not work (invalid account error...) any hints here? i tried to email them, got no response...
It seems that transition will not be that smooth. I think there are some more issues and who knows if pools are updated. I expect few more updates until things get fixed properly. I guess now we need to stay patient, pray and wait for further instructions from devs.
|
|
|
|
tiras
|
|
December 17, 2017, 03:17:07 PM |
|
guys, i'm loosing my patience here, two mandatory updates in one day, come on...
- now, i updated 6 machines to the latest version (1.0.6.7), starting biblepayd shows CPU 0.0%, biblepay-cli getmininginfo shows pool mining = false. wtf? any ideas what to do? please help. previous udpates worked ok. i'm on pool2.
- there is no windows version for 1.0.6.7? will it come out soon?
- and btw, withdrawing from minersofmen does not work (invalid account error...) any hints here? i tried to email them, got no response...
It seems that transition will not be that smooth. I think there are some more issues and who knows if pools are updated. I expect few more updates until things get fixed properly. I guess now we need to stay patient, pray and wait for further instructions from devs. right, flaming in this thread won't help much.
|
|
|
|
|
noob101
Newbie
Offline
Activity: 41
Merit: 0
|
|
December 17, 2017, 03:18:59 PM |
|
guys, i'm loosing my patience here, two mandatory updates in one day, come on...
- now, i updated 6 machines to the latest version (1.0.6.7), starting biblepayd shows CPU 0.0%, biblepay-cli getmininginfo shows pool mining = false. wtf? any ideas what to do? please help. previous udpates worked ok. i'm on pool2.
- there is no windows version for 1.0.6.7? will it come out soon?
- and btw, withdrawing from minersofmen does not work (invalid account error...) any hints here? i tried to email them, got no response...
Hi there, I know for big miners like you time=money, but please bear with us. I understand your frustration, and bible_pay(dev) and his team are working their rear ends off to solve these issues. With regards to miners of men, the owners handle is nsummy. He is an independent who is kindly hosting a pool to assist the coin. Again I apologize for any inconvenience. You have to agree though, it is not common to find a dev willing to submit solutions so quickly if a problem shows up. All the best in your endeavors.
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
December 17, 2017, 03:28:24 PM |
|
When looking at the masternode winners output from debug, it shows "21551": "B547NvFM2TUeCKxEGcxCxpt8as42pyS4po:10", "21552": "BDkocGarpfSBMuT15p9dQzsAfNqsgb2UHh:10", "21553": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:9", "21554": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:9", "21555": "B8se8LxzDo9AKmSB9fnY38gbc3ubedRZxJ:10", "21556": "B8se8LxzDo9AKmSB9fnY38gbc3ubedRZxJ:9", "21557": "BSrFn8zpC48AykVANWcjVEve5tzn8NQNRE:9", "21558": "BSrFn8zpC48AykVANWcjVEve5tzn8NQNRE:10", "21559": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:10", Noticed block 21553 and 554 both went to the same payee, same with the 55/56 and 57/58. Only one MN in the list has each of these addresses. Am I misreading that, or is there something more to understand? That should be OK if one controller has multiple masternodes; lets verify 100 payments after we get back up. So after you upgrade your linux box, the last few blocks in the chain are bad because the tithe was paid at that height. Go ahead and click OK to let it rebuild the block index. Alex and I are working on this now to ensure we resync up to 21551. This upgrade only talks to other nodes of the same protocol version, hence the reason it is not going smoothly. We are working it out now. Please wait two more hours for the windows update.
|
|
|
|
tiras
|
|
December 17, 2017, 03:32:00 PM |
|
When looking at the masternode winners output from debug, it shows "21551": "B547NvFM2TUeCKxEGcxCxpt8as42pyS4po:10", "21552": "BDkocGarpfSBMuT15p9dQzsAfNqsgb2UHh:10", "21553": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:9", "21554": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:9", "21555": "B8se8LxzDo9AKmSB9fnY38gbc3ubedRZxJ:10", "21556": "B8se8LxzDo9AKmSB9fnY38gbc3ubedRZxJ:9", "21557": "BSrFn8zpC48AykVANWcjVEve5tzn8NQNRE:9", "21558": "BSrFn8zpC48AykVANWcjVEve5tzn8NQNRE:10", "21559": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:10", Noticed block 21553 and 554 both went to the same payee, same with the 55/56 and 57/58. Only one MN in the list has each of these addresses. Am I misreading that, or is there something more to understand? That should be OK if one controller has multiple masternodes; lets verify 100 payments after we get back up. So after you upgrade your linux box, the last few blocks in the chain are bad because the tithe was paid at that height. Go ahead and click OK to let it rebuild the block index. Alex and I are working on this now to ensure we resync up to 21551. This upgrade only talks to other nodes of the same protocol version, hence the reason it is not going smoothly. We are working it out now. Please wait two more hours for the windows update. ROb , how long should it take to rebuild the block DB ? I've been running it for more than an hour with no luck . stopped it . can you post an IP of the node with a healthy rebuilt DB so we can force connection and resync ?
|
|
|
|
webster22
Newbie
Offline
Activity: 56
Merit: 0
|
|
December 17, 2017, 03:35:00 PM |
|
Morning everyone. Looks like another day of challenges. Keep at it Rob and team.
Question -
I am installing the latest (1.6.7). Are there any other things I must do. I am reading that blockchains must be rebuilt. Is this true for everyone?
Some can post all steps they took after install?
|
|
|
|
seeksilence1
Newbie
Offline
Activity: 86
Merit: 0
|
|
December 17, 2017, 03:39:50 PM |
|
I could not sync the blockchain. What step should I do? Just leave wallet and conf in the folder? Any change needs to be done to masternode.conf?
|
|
|
|
togoshigekata
|
|
December 17, 2017, 03:44:43 PM |
|
BiblePay - 1.0.6.7 Mandatory Upgrade
- Disable tithe blocks at #21550 - Ensure Sanctuary payments can go live at #21551 - Increment mandatory protocol version to 70911 - Sanctuary payments went live at block #21551 - Superblocks start at block #30001 - Proposals and Budgets went live at block #21551
** This is the linux release. Please upgrade now and lets get the chain rolling on the right fork.
Windows will be available in 4 hours. **
Oh unfortunately we need to update every single node in our system, the pool, the masternodes, everything . it's asking to rebuild block DB after the update .
I deleted blocks,chainstate and database dirs and restarted the daemon but it still seems not syncing.
updated,rebuild,deled chains,block, .db without sync next machine stuck on 21548 block with reindexing
So after you upgrade your linux box, the last few blocks in the chain are bad because the tithe was paid at that height.
Go ahead and click OK to let it rebuild the block index.
Alex and I are working on this now to ensure we resync up to 21551. This upgrade only talks to other nodes of the same protocol version, hence the reason it is not going smoothly.
We are working it out now.
Please wait two more hours for the windows update.
ROb , how long should it take to rebuild the block DB ?
I've been running it for more than an hour with no luck . stopped it .
can you post an IP of the node with a healthy rebuilt DB so we can force connection and resync ?
=============== For the block database issue, we just type in yes? Do we need to run any of these commands? rm blocks -R rm chainstate -R
rm banlist.dat rm fee_estimates.dat rm governance.dat rm mncache.dat rm mnpayments.dat rm netfulfilled.dat rm peers.dat
./biblepayd -daemon -reindex
I tried the rm blocks and rm chainstate command and then a reindex and Im stuck at block 0 hehe
|
|
|
|
webster22
Newbie
Offline
Activity: 56
Merit: 0
|
|
December 17, 2017, 03:45:08 PM |
|
Rob -
I tried to withdraw some coins from pool overnight. Got confirmation email and clicked on it.
But nothing coming. Are they lost due to the update?
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
December 17, 2017, 03:47:44 PM |
|
Rob -
I tried to withdraw some coins from pool overnight. Got confirmation email and clicked on it.
But nothing coming. Are they lost due to the update?
Lets wait until the pool is on 1067 and synced, then we can look at the actual guid. Nothing is lost in the blockchain, No, not lost, ever. Only coins mined on a fork are lost. Or coins deposited to an exchange on a fork.
|
|
|
|
webster22
Newbie
Offline
Activity: 56
Merit: 0
|
|
December 17, 2017, 04:03:56 PM |
|
Rob -
I tried to withdraw some coins from pool overnight. Got confirmation email and clicked on it.
But nothing coming. Are they lost due to the update?
Lets wait until the pool is on 1067 and synced, then we can look at the actual guid. Nothing is lost in the blockchain, No, not lost, ever. Only coins mined on a fork are lost. Or coins deposited to an exchange on a fork.Oh this got my attention. How can you tell this? Concept of fungibility is designed in bitcoins. (1 bitcoin = Any other bitcoin). How can you tell what is fork vs no fork coin? How will exchange know?
|
|
|
|
tiras
|
|
December 17, 2017, 04:13:21 PM |
|
Rob -
I tried to withdraw some coins from pool overnight. Got confirmation email and clicked on it.
But nothing coming. Are they lost due to the update?
Lets wait until the pool is on 1067 and synced, then we can look at the actual guid. Nothing is lost in the blockchain, No, not lost, ever. Only coins mined on a fork are lost. Or coins deposited to an exchange on a fork.Oh this got my attention. How can you tell this? Concept of fungibility is designed in bitcoins. (1 bitcoin = Any other bitcoin). How can you tell what is fork vs no fork coin? How will exchange know? I may be wrong but exchange should be on the same blockchain as you are . otherwise you TX will never be confirmed on their side .
|
|
|
|
slovakia
|
|
December 17, 2017, 04:14:16 PM |
|
tiras right
|
|
|
|
thraq
Newbie
Offline
Activity: 4
Merit: 0
|
|
December 17, 2017, 04:17:20 PM |
|
Is there a problem with the chain? I stuck at 21559. Downloaded the newest client for Win64, tried to reindex, deleted whole blocks on my harddrive,changed addnodes,... Still stuck at 21559.
Any ideas?
|
|
|
|
slovakia
|
|
December 17, 2017, 04:18:50 PM |
|
thraq check topics 1-2 pages back
|
|
|
|
thraq
Newbie
Offline
Activity: 4
Merit: 0
|
|
December 17, 2017, 04:24:30 PM |
|
thraq check topics 1-2 pages back I didn't find an official information wether on webpage or first message in this thread. This was because i asked. Thougt there is only a Problem with the Masternodes, but looks like this struggles the whole network... Ist there an eta time when everything works again? Thanks.
|
|
|
|
seasonw
|
|
December 17, 2017, 04:40:41 PM |
|
I removed all data and re-sync again but stucked at blocks 20000. Anyone faced same issue?
|
|
|
|
|