padre999
Newbie
Offline
Activity: 23
Merit: 0
|
|
December 18, 2013, 12:01:52 PM |
|
just synced as well, did addnode 103.11.49.151 add in the meantime. not sure if it was that or patience !?
|
|
|
|
trankil
|
|
December 18, 2013, 12:02:48 PM |
|
tryed that? still on 607
Okay, our new fork should be up to 608 now -and difficulty is now -"difficulty" : 0.00000188, block 609 difficulty 185
|
|
|
|
stas
|
|
December 18, 2013, 12:02:53 PM |
|
added everything I could , no synch yet
|
|
|
|
ryen123
|
|
December 18, 2013, 12:04:12 PM |
|
just synced as well, did addnode 103.11.49.151 add in the meantime. not sure if it was that or patience !?
103.11.49.151 is my pc. I was already on the new chain so its up to date. Now still 609.
|
|
|
|
montecristo83
Member
Offline
Activity: 112
Merit: 10
|
|
December 18, 2013, 12:06:35 PM |
|
"blocks" : 609, "difficulty" : 0.00002268,
Is that correct?
|
|
|
|
ryen123
|
|
December 18, 2013, 12:08:55 PM |
|
"blocks" : 609, "difficulty" : 0.00002268,
Is that correct?
blocks" : 609 difficulty" : 0.00000185 This is the correct one.
|
|
|
|
ijuststarted
Newbie
Offline
Activity: 37
Merit: 0
|
|
December 18, 2013, 12:09:24 PM |
|
"blocks" : 609, "difficulty" : 0.00002268,
Is that correct?
same here, brother
|
|
|
|
skwinx
Member
Offline
Activity: 100
Merit: 10
|
|
December 18, 2013, 12:12:41 PM |
|
"blocks" : 609, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 0.00000185,
|
|
|
|
ChekaZ
Legendary
Offline
Activity: 1884
Merit: 1005
|
|
December 18, 2013, 12:29:49 PM |
|
Iam on block 609
{ "blocks" : 609, "currentblocksize" : 2279, "currentblocktx" : 4, "difficulty" : 0.00000185, "errors" : "", "genproclimit" : -1, "hashespermin" : 40.20245300, "pooledtx" : 4, "testnet" : false }
|
BTC: 1Ges1taJ69W7eEMbQLcmNGnUZenBkCnn45 FTC: 6sxjM96KMZ7t4AmDTUKDZdq82Nj931VQvY
|
|
|
montecristo83
Member
Offline
Activity: 112
Merit: 10
|
|
December 18, 2013, 12:34:56 PM |
|
"blocks" : 609, "difficulty" : 0.00002268,
Is that correct?
blocks" : 609 difficulty" : 0.00000185 This is the correct one. Thanks. On desktop #1 I'm on the correct fork, but on desktop #2 I'm on the wrong one. Both are using the same operating system (W7 x64) and both have the latest client version ("version" : 85400,). They also have the same nodes in the config file. How can I get on the right fork on desktop #2? This problem is also occurring on my linux VPS's.
|
|
|
|
aorith
Member
Offline
Activity: 84
Merit: 10
|
|
December 18, 2013, 12:35:41 PM |
|
stuck at block 607 too
|
BTC: 1Pc2BrecisYLZ2FSFEgCn16ogTHjopqEey LTC: LM1XBHF8Ccv2vdgh3kqCqPaGkWGhzRMxjw NXT: 3946500435546198781
|
|
|
voteformeg
Legendary
Offline
Activity: 1932
Merit: 1005
|
|
December 18, 2013, 12:36:49 PM |
|
i comp on 609 , other stil 608 , think patience is the key
|
|
|
|
stuartcharles
Newbie
Offline
Activity: 51
Merit: 0
|
|
December 18, 2013, 12:39:09 PM |
|
Frustrating... hows your nerves Freetrade? Hold it together we are all backing you
|
|
|
|
ryen123
|
|
December 18, 2013, 12:43:14 PM |
|
"blocks" : 609, "difficulty" : 0.00002268,
Is that correct?
blocks" : 609 difficulty" : 0.00000185 This is the correct one. Thanks. On desktop #1 I'm on the correct fork, but on desktop #2 I'm on the wrong one. Both are using the same operating system (W7 x64) and both have the latest client version ("version" : 85400,). They also have the same nodes in the config file. How can I get on the right fork on desktop #2? This problem is also occurring on my linux VPS's. I'm not too sure about this but you could restart the wallet with the -reindex to check the blockchain. See if it helps.
|
|
|
|
cragv
|
|
December 18, 2013, 12:47:16 PM |
|
Frustrating... hows your nerves Freetrade? Hold it together we are all backing you
Seconded. Have been following the thread since the beginning and mining, updating and testing. I finally created an account just for this thread!
|
|
|
|
FreeTrade (OP)
Legendary
Offline
Activity: 1470
Merit: 1030
|
|
December 18, 2013, 12:48:05 PM |
|
Frustrating... hows your nerves Freetrade? Hold it together we are all backing you
Thanks Stuart. This is my third coin launch so I'm more calm about these hiccups now than I was on my first outing. I'm hopeful we've got the basic parameters right now, so I can start giving more time to the stability issues noted.
|
RepNet is a reputational social network blockchain for uncensored Twitter/Reddit style discussion. 10% Interest On All Balances. 100% Distributed to Users and Developers.
|
|
|
padre999
Newbie
Offline
Activity: 23
Merit: 0
|
|
December 18, 2013, 12:52:02 PM |
|
"blocks" : 609, "difficulty" : 0.00002268,
Is that correct?
blocks" : 609 difficulty" : 0.00000185 This is the correct one. Thanks. On desktop #1 I'm on the correct fork, but on desktop #2 I'm on the wrong one. Both are using the same operating system (W7 x64) and both have the latest client version ("version" : 85400,). They also have the same nodes in the config file. How can I get on the right fork on desktop #2? This problem is also occurring on my linux VPS's. I'm not too sure about this but you could restart the wallet with the -reindex to check the blockchain. See if it helps. On my second machine that was stuck at 608 I did the following: - made sure I have the latest wallet running: v0.8.54.0-unk-beta - closed the wallet - deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! ) - restarted the wallet - did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add" - waited until blockchain was downloaded from scratch all synced now ... but wondering now why block 609 takes so long...
|
|
|
|
FreeTrade (OP)
Legendary
Offline
Activity: 1470
Merit: 1030
|
|
December 18, 2013, 12:57:33 PM |
|
On my second machine that was stuck at 608 I did the following: - made sure I have the latest wallet running: v0.8.54.0-unk-beta - closed the wallet - deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! ) - restarted the wallet - did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add" - waited until blockchain was downloaded from scratch all synced now Thanks - you might get away with just deleting peers.dat - this will force your client to re-evaluate the nodes on the network.
|
RepNet is a reputational social network blockchain for uncensored Twitter/Reddit style discussion. 10% Interest On All Balances. 100% Distributed to Users and Developers.
|
|
|
montecristo83
Member
Offline
Activity: 112
Merit: 10
|
|
December 18, 2013, 01:00:35 PM Last edit: December 18, 2013, 03:06:17 PM by montecristo83 |
|
"blocks" : 609, "difficulty" : 0.00002268,
Is that correct?
blocks" : 609 difficulty" : 0.00000185 This is the correct one. Thanks. On desktop #1 I'm on the correct fork, but on desktop #2 I'm on the wrong one. Both are using the same operating system (W7 x64) and both have the latest client version ("version" : 85400,). They also have the same nodes in the config file. How can I get on the right fork on desktop #2? This problem is also occurring on my linux VPS's. I'm not too sure about this but you could restart the wallet with the -reindex to check the blockchain. See if it helps. On my second machine that was stuck at 608 I did the following: - made sure I have the latest wallet running: v0.8.54.0-unk-beta - closed the wallet - deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! ) - restarted the wallet - did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add" - waited until blockchain was downloaded from scratch all synced now ... but wondering now why block 609 takes so long... Thanks to the both of you. I'm trying -reindex on the linux instances and will delete the mentioned folder (- wallet.dat) if it fails. I already deleted everything except wallet.dat on my W7 desktop, and am waiting for it to sync. Will update once it does. Update: Success! I'm on the right fork on the desktop (blocks 610, difficulty 0.00000178). Still waiting for the linux instances to "reindex". If that fails I'll try deleting 'peers.dat' as FreeTrade suggested. Update #2: Success! Linux instances are now on the correct fork. After waiting 1 hour for "reindex" to do its thing, I decided to try method #2 instead. At first I tried to simply delete 'peers.dat', but I still got stuck on the old fork. So I went ahead and deleted everything from the .memorycoin folder (except wallet.dat) which did the trick!
|
|
|
|
padre999
Newbie
Offline
Activity: 23
Merit: 0
|
|
December 18, 2013, 01:10:06 PM |
|
On my second machine that was stuck at 608 I did the following: - made sure I have the latest wallet running: v0.8.54.0-unk-beta - closed the wallet - deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! ) - restarted the wallet - did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add" - waited until blockchain was downloaded from scratch all synced now Thanks - you might get away with just deleting peers.dat - this will force your client to re-evaluate the nodes on the network. Thanks! I guess this is the more sophisticated version of what I did Same thing happening again though. Out of sync. Current blocks 609. Estimated blocks 610.
Will try deleting peers.dat now and see if it does the trick. But it gets a bit tedious doing this for every block. Is that due to too many outdated nodes?Oooppps... patience did it again
|
|
|
|
|