lethax
Member
 Offline
Activity: 108
Merit: 10
|
 |
December 02, 2015, 07:37:34 AM |
|
Thanks for the reassurances  |
|
|
|
fredeq
Legendary
Offline
Activity: 1537
Merit: 1005
|
|
December 02, 2015, 11:06:41 AM |
|
I have finally made a successful update.
Reverted back to wallet state of 24th of November (before fork), deleted only peers.dat
Launched wallet 3.0.3 and it synced without problems.
Now sitting on 7 connections and staking.
Maybe it will help someone.
Sounds promising. Could you please post your conf file. I'm not sure if I have the right one. Thanks. I am not using any. Just fired 3.0.3 wallet on 24th of November files. (But deleted peers.dat) It may require a pre-fork copy of ambercoin appdata to work. |
|
|
|
|
johnnysof
|
|
December 02, 2015, 01:16:23 PM |
|
I have finally made a successful update.
Reverted back to wallet state of 24th of November (before fork), deleted only peers.dat
Launched wallet 3.0.3 and it synced without problems.
Now sitting on 7 connections and staking.
Maybe it will help someone.
Sounds promising. Could you please post your conf file. I'm not sure if I have the right one. Thanks. I am not using any. Just fired 3.0.3 wallet on 24th of November files. (But deleted peers.dat) It may require a pre-fork copy of ambercoin appdata to work. Thanks, will try without the conf. |
|
|
|
|
|
canman
|
|
December 02, 2015, 03:44:54 PM |
|
updated wallet to current version, but wallet always out of sync. can someone plz help thanks
|
|
|
|
|
|
antho281
|
|
December 02, 2015, 03:47:18 PM |
|
updated wallet to current version, but wallet always out of sync. can someone plz help thanks
Have you updated the Conf file? Add : addnode=ambercoin01.mooo.com addnode=ambercoin02.mooo.com addnode=ambercoin03.mooo.com Are you on Linux, Mac or Windows? Try launching with the parameter : --connect=ambercoin01.mooo.com |
|
|
|
|
|
Slydrule
|
|
December 02, 2015, 07:04:09 PM |
|
updated wallet to current version, but wallet always out of sync. can someone plz help thanks
When you say always out of sync you mean the sync process never completes? If so, close the wallet and restart it again. It should begin to sync again, assuming you are making connections with other nodes. If you are not connecting to any nodes then that is why you cannot sync your wallet. If you have no connections and you have the right configuration in your .conf file then it could be you have been banned from connecting because you wallet is on the wrong fork. The ban time is 24 hours. I had to close and restart my wallet several times before the synchronization completed but since then it has run fine for about 55 hours. |
|
|
|
|
verycoinsuchlist
Member
Offline
Activity: 89
Merit: 10
|
|
December 02, 2015, 08:29:02 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
|
Believe In Crypto Currency? Try To Actually Use It
|
|
|
|
antho281
|
|
December 02, 2015, 08:33:34 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! |
|
|
|
|
verycoinsuchlist
Member
Offline
Activity: 89
Merit: 10
|
|
December 02, 2015, 08:57:20 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! ...maybe we're looking at the wrong place, might be time to call an exorcist  ...or, considering it is AMBER, something like a seismologist or geologist |
Believe In Crypto Currency? Try To Actually Use It
|
|
|
|
antho281
|
|
December 02, 2015, 08:59:46 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! ...maybe we're looking at the wrong place, might be time to call an exorcist HAHA Got 3 wallets on 3 differents computers.. There're all connected togethers. This afternoon, one forked... But 2 were still on track! haha Give your exorcist my address! haha |
|
|
|
|
|
johnnysof
|
|
December 02, 2015, 09:01:51 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! I had the same issue yesterday. I'm not the expert on block chains, but something is very strange here. What did help on my site, at least for the last 10 hours (with 3-4 staked blocks) is below. I did not use any conf file. I have finally made a successful update.
Reverted back to wallet state of 24th of November (before fork), deleted only peers.dat
Launched wallet 3.0.3 and it synced without problems.
Now sitting on 7 connections and staking.
Maybe it will help someone.
|
|
|
|
|
|
antho281
|
|
December 02, 2015, 09:03:59 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! I had the same issue yesterday. I'm not the expert on block chains, but something is very strange here. What did help on my site, at least for the last 10 hours (with 3-4 staked blocks) is below. I did not use any conf file. I have finally made a successful update.
Reverted back to wallet state of 24th of November (before fork), deleted only peers.dat
Launched wallet 3.0.3 and it synced without problems.
Now sitting on 7 connections and staking.
Maybe it will help someone.
I'm gonna take a look on that! Thanks for sharing! |
|
|
|
|
|
Jayfek
|
|
December 02, 2015, 09:23:33 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! I'm investigating this kind of * too. Staking, solomining. Last transactions 17:37 GMT (solomine 0.50 AMBER) and 19:27 GMT (stake). There was no 3-party connections (very often checked by getpeerinfo too), only the 3 mooo-s: --ambercoin.conf-- server=1 listen=0 addnode=ambercoin01.mooo.com addnode=ambercoin02.mooo.com addnode=ambercoin03.mooo.com --/ambercoin.conf-- It can be big help if wallet logs instead of "disconnected" something like "disconnected. banned for forking/old wallet/[something] mismatch/etc." Or even "disconnected. banned (for xx hours)." can be very big help - walletowner can see that "problem with me", not the infrastructure. Second wallet, staking, not solomining, stays online and staking. So, solomining can make forking? Antho281 you solomining too? I have seen big rate of rejected blocks while solomining, different miners: 16%, 32%, 7% etc. My solomine wallet with solomining 280x has 1-core AMD Sempron (other miners connect here). Other miners and even local machine miner say often something like "...not providing work fast enough". Present fork may be some timing issue? BTW I have seen this kind of message always while solomining BTQ (quark) too. |
|
|
|
|
|
antho281
|
|
December 02, 2015, 09:34:48 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! I'm investigating this kind of * too. Staking, solomining. Last transactions 17:37 GMT (solomine 0.50 AMBER) and 19:27 GMT (stake). There was no 3-party connections (very often checked by getpeerinfo too), only the 3 mooo-s: --ambercoin.conf-- server=1 listen=0 addnode=ambercoin01.mooo.com addnode=ambercoin02.mooo.com addnode=ambercoin03.mooo.com --/ambercoin.conf-- It can be big help if wallet logs instead of "disconnected" something like "disconnected. banned for forking/old wallet/[something] mismatch/etc." Or even "disconnected. banned (for xx hours)." can be very big help - walletowner can see that "problem with me", not the infrastructure. Second wallet, staking, not solomining, stays online and staking. So, solomining can make forking? Antho281 you solomining too? I have seen big rate of rejected blocks while solomining, different miners: 16%, 32%, 7% etc. My solomine wallet with solomining 280x has 1-core AMD Sempron (other miners connect here). Other miners and even local machine miner say often something like "...not providing work fast enough". Present fork may be some timing issue? BTW I have seen this kind of message always while solomining BTQ (quark) too. I'm solomining with 3 GPU on a Wallet and Owning a pool (amber.thecryptoworld.org:8080) where I'm mining with about 12 GPU at the moment. The third wallet forked.. there's no mining on it What about your internet connection Jayfek? Sometimes, solomining ask a quicker connection than pool mining  |
|
|
|
|
|
Jayfek
|
|
December 02, 2015, 09:44:48 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! I'm investigating this kind of * too. Staking, solomining. Last transactions 17:37 GMT (solomine 0.50 AMBER) and 19:27 GMT (stake). There was no 3-party connections (very often checked by getpeerinfo too), only the 3 mooo-s: --ambercoin.conf-- server=1 listen=0 addnode=ambercoin01.mooo.com addnode=ambercoin02.mooo.com addnode=ambercoin03.mooo.com --/ambercoin.conf-- It can be big help if wallet logs instead of "disconnected" something like "disconnected. banned for forking/old wallet/[something] mismatch/etc." Or even "disconnected. banned (for xx hours)." can be very big help - walletowner can see that "problem with me", not the infrastructure. Second wallet, staking, not solomining, stays online and staking. So, solomining can make forking? Antho281 you solomining too? I have seen big rate of rejected blocks while solomining, different miners: 16%, 32%, 7% etc. My solomine wallet with solomining 280x has 1-core AMD Sempron (other miners connect here). Other miners and even local machine miner say often something like "...not providing work fast enough". Present fork may be some timing issue? BTW I have seen this kind of message always while solomining BTQ (quark) too. I'm solomining with 3 GPU on a Wallet and Owning a pool (amber.thecryptoworld.org:8080) where I'm mining with about 12 GPU at the moment. The third wallet forked.. there's no mining on it What about your internet connection Jayfek? Sometimes, solomining ask a quicker connection than pool mining Connection is 100/100 mbps fibre dedicated. There must be something, not just code Or... EDIT: This ban to me seems come from all 3 mooo-s |
|
|
|
|
|
Slydrule
|
|
December 02, 2015, 09:45:33 PM |
|
getblockbynumber 606621
"proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0"
Is this what everyone else is getting?
This matches the ssdpool block explorer.
|
|
|
|
|
|
antho281
|
|
December 02, 2015, 09:50:32 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! I'm investigating this kind of * too. Staking, solomining. Last transactions 17:37 GMT (solomine 0.50 AMBER) and 19:27 GMT (stake). There was no 3-party connections (very often checked by getpeerinfo too), only the 3 mooo-s: --ambercoin.conf-- server=1 listen=0 addnode=ambercoin01.mooo.com addnode=ambercoin02.mooo.com addnode=ambercoin03.mooo.com --/ambercoin.conf-- It can be big help if wallet logs instead of "disconnected" something like "disconnected. banned for forking/old wallet/[something] mismatch/etc." Or even "disconnected. banned (for xx hours)." can be very big help - walletowner can see that "problem with me", not the infrastructure. Second wallet, staking, not solomining, stays online and staking. So, solomining can make forking? Antho281 you solomining too? I have seen big rate of rejected blocks while solomining, different miners: 16%, 32%, 7% etc. My solomine wallet with solomining 280x has 1-core AMD Sempron (other miners connect here). Other miners and even local machine miner say often something like "...not providing work fast enough". Present fork may be some timing issue? BTW I have seen this kind of message always while solomining BTQ (quark) too. I'm solomining with 3 GPU on a Wallet and Owning a pool (amber.thecryptoworld.org:8080) where I'm mining with about 12 GPU at the moment. The third wallet forked.. there's no mining on it What about your internet connection Jayfek? Sometimes, solomining ask a quicker connection than pool mining Connection is 100/100 mbps fibre dedicated. There must be something, not just code Or... EDIT: This ban to me seems come from all 3 mooo-s We'll need to send you the exorcist too then.. haha getblockbynumber 606621
"proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0"
Is this what everyone else is getting?
This matches the ssdpool block explorer.
I'm in |
|
|
|
|
|
binmon
|
|
December 02, 2015, 10:08:07 PM |
|
getblockbynumber 606621
"proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0"
Is this what everyone else is getting?
This matches the ssdpool block explorer.
getblockbynumber 606621 "proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0" Matches mine. I also have the same hash for 606621 |
|
|
|
|
johnnysof
|
|
December 02, 2015, 10:21:03 PM |
|
hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !! I'm investigating this kind of * too. Staking, solomining. Last transactions 17:37 GMT (solomine 0.50 AMBER) and 19:27 GMT (stake). There was no 3-party connections (very often checked by getpeerinfo too), only the 3 mooo-s: --ambercoin.conf-- server=1 listen=0 addnode=ambercoin01.mooo.com addnode=ambercoin02.mooo.com addnode=ambercoin03.mooo.com --/ambercoin.conf-- It can be big help if wallet logs instead of "disconnected" something like "disconnected. banned for forking/old wallet/[something] mismatch/etc." Or even "disconnected. banned (for xx hours)." can be very big help - walletowner can see that "problem with me", not the infrastructure. Second wallet, staking, not solomining, stays online and staking. So, solomining can make forking? Antho281 you solomining too? I have seen big rate of rejected blocks while solomining, different miners: 16%, 32%, 7% etc. My solomine wallet with solomining 280x has 1-core AMD Sempron (other miners connect here). Other miners and even local machine miner say often something like "...not providing work fast enough". Present fork may be some timing issue? BTW I have seen this kind of message always while solomining BTQ (quark) too. I'm solomining with 3 GPU on a Wallet and Owning a pool (amber.thecryptoworld.org:8080) where I'm mining with about 12 GPU at the moment. The third wallet forked.. there's no mining on it What about your internet connection Jayfek? Sometimes, solomining ask a quicker connection than pool mining Connection is 100/100 mbps fibre dedicated. There must be something, not just code Or... EDIT: This ban to me seems come from all 3 mooo-s Hope this helps you: I never solo mined and had the same issues with the same conf above (without server=1). Got also banned by the server. After getting on the right chain I deleted the conf and started it again. Since 12h is seems to work fine (previously I got every 2-3 hours to another fork and need to resync from the backup). MAC OS. |
|
|
|
|
|
johnnysof
|
|
December 02, 2015, 10:23:00 PM |
|
getblockbynumber 606621
"proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0"
Is this what everyone else is getting?
This matches the ssdpool block explorer.
getblockbynumber 606621 "proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0" Matches mine. I also have the same hash for 606621 Also the same proofhash on my wallet. |
|
|
|
|
|
