599444
proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Ok, that's why I get? CrzyBilly, do you want to check this block's proofhash again please? |
|
|
|
delete database folder too
No more error, but with only using your blk0001.dat, it started syncing right from the beginning. 596,xxx blocks remaining... What's really weird is that, like TWN said, my 599444 block doesn't match, but 599496 does? How is that possible? Doesn't match what you guys have: getblockbynumber 599444 "proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4" Later block matches??? getblockbynumber 599496 "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d" matches You and Dev had a different proofhash for 599444. "height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
599496 matches though |
|
|
|
delete database folder too
No more error, but with only using your blk0001.dat, it started syncing right from the beginning. 596,xxx blocks remaining... What's really weird is that, like TWN said, my 599444 block doesn't match, but 599496 does? How is that possible? Doesn't match what you guys have: getblockbynumber 599444 "proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4" Later block matches??? getblockbynumber 599496 "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d" matches |
|
|
|
Same error, but without the txleveldb directory, the DB.LOG file shortened to:
Unacceptable log file C:\Users\User\AppData\Roaming\AmberCoin\database\log.0000000003: unsupported log version 19
Invalid log file: log.0000000003: Invalid argument
PANIC: Invalid argument
process-private: unable to find environment
delete database folder yet? |
|
|
|
Thanks. Downloading now. While I was waiting, I tried resyncing again with the correct DB from Nov 27th.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", 221 KB/s - 276 MB of 324 MB, 4 mins left I'm going to use your CONF file too. (I had renamed mine, so it didn't have one.) Hmmm...not sure if I can remove something to fix this?  that would be, because I recompiled it with the latest db and ssl... delete the txleveldb Same error, but without the txleveldb directory, the DB.LOG file shortened to: Unacceptable log file C:\Users\User\AppData\Roaming\AmberCoin\database\log.0000000003: unsupported log version 19 Invalid log file: log.0000000003: Invalid argument PANIC: Invalid argument process-private: unable to find environment delete database folder too |
|
|
|
What is the correct block we should be on?
"height" : 599541, "proofhash" : "00000000060d1b4b5bd89dc0325b41f953338049e531d3754cb2fa939e19508a" |
|
|
|
Thanks. Downloading now. While I was waiting, I tried resyncing again with the correct DB from Nov 27th.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", 221 KB/s - 276 MB of 324 MB, 4 mins left I'm going to use your CONF file too. (I had renamed mine, so it didn't have one.) Hmmm...not sure if I can remove something to fix this? that would be, because I recompiled it with the latest db and ssl... delete the txleveldb |
|
|
|
Thanks. Downloading now. While I was waiting, I tried resyncing again with the correct DB from Nov 27th.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", it can't be wrong... ambercoin01 is the only node I accept  Trying to help everyone else out get on the correct chain Where should be ambercoin01 added? in the conf file with "addnode"? This is a good config setting you can use rpcallowip=127.0.0.1 rpcallow=localhost rpcport=31981 listen=1 daemon=1 (remove this line if you don't solo mine) server=1 (remove this line if you don't solo mine) gen=0 addnode=ambercoin01.mooo.com |
|
|
|
Thanks. Downloading now. While I was waiting, I tried resyncing again with the correct DB from Nov 27th.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", it can't be wrong... ambercoin01 is the only node I accept Trying to help everyone else out get on the correct chain |
|
|
|
Thanks. Downloading now. While I was waiting, I tried resyncing again with the correct DB from Nov 27th.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", |
|
|
|
"height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
This really gets a mess. Previous post from dev for block 598473 seems to be ok. getblockbynumber 598473 "proofhash" : "000008d1c209665b7427e9f412a3e991b9d97224c228d4afbdbd4ad4d794b1ef" the last one for block 599444 is completely wrong again: getblockbynumber 599444 "proofhash" : "000bfe9a9c34a3649c9f8a93618c18861835c2e7db7ba355bd06fc16afd98961" What is wrong and why I lose the right chain all the time? I just resync the wallet from scratch yesterday. the honest answer... because dev hasn't banned the people on the wrong chain What do you mean?!? Any advise how to fix that? The only real way to fix this, is to have ambercoin01.mooo.com start banning connections. I agree. But as I have posted I cannot connected to ambercoin01.moo0.com. I get 0 connections and my wallet never syncs. Maybe this node is overloaded and cannot support any more connections or there is some limit on the connections it will accept but whatever it is, if people cannot connect it is not a solution. Also, you must set listen to 0 (listen=0) in your wallet .conf file or it will listen for other connections and accept them. So you could wind up connecting to a bad node again and then off to a fork. At least I believe that's how it works. NO NO NO don't set that to 0... set it to 1 so that it can connect to ambercoin01 rpcallowip=127.0.0.1 rpcallow=localhost rpcport=31981 listen=1 daemon=1 server=1 gen=0 addnode=ambercoin01.mooo.com is my conf |
|
|
|
What do you mean?
They get banned by adding a "checkpoint=*******" line into AmberCoin.conf
Can you tell us what ***** should be? No. You shouldn'd add anything! It is long line with a key. It should be only on ambercoin01.mooo.com It works as a checkpointing server. so you are banning people, because some people are still coming a crossed as a banscore of 0 |
|
|
|
"height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
This really gets a mess. Previous post from dev for block 598473 seems to be ok. getblockbynumber 598473 "proofhash" : "000008d1c209665b7427e9f412a3e991b9d97224c228d4afbdbd4ad4d794b1ef" the last one for block 599444 is completely wrong again: getblockbynumber 599444 "proofhash" : "000bfe9a9c34a3649c9f8a93618c18861835c2e7db7ba355bd06fc16afd98961" What is wrong and why I lose the right chain all the time? I just resync the wallet from scratch yesterday. the honest answer... because dev hasn't banned the people on the wrong chain What do you mean?!? Any advise how to fix that? The only real way to fix this, is to have ambercoin01.mooo.com start banning connections. |
|
|
|
13:27:59

getpeerinfo
13:27:59

[
{
"addr" : "ambercoin01.mooo.com",
"services" : "00000001",
"lastsend" : 1448821612,
"lastrecv" : 1448821612,
"conntime" : 1448821559,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 599461,
"banscore" : 0
}
]
Thx, I'll try using your DB.
http://www.mediafire.com/download/26ibd56699yedhq/amber.zip |
|
|
|
"height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
This really gets a mess. Previous post from dev for block 598473 seems to be ok. getblockbynumber 598473 "proofhash" : "000008d1c209665b7427e9f412a3e991b9d97224c228d4afbdbd4ad4d794b1ef" the last one for block 599444 is completely wrong again: getblockbynumber 599444 "proofhash" : "000bfe9a9c34a3649c9f8a93618c18861835c2e7db7ba355bd06fc16afd98961" What is wrong and why I lose the right chain all the time? I just resync the wallet from scratch yesterday. the honest answer... because dev hasn't banned the people on the wrong chain |
|
|
|
"height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
Well, I resynced with the firewall restriction. Only had one connection. Used "AmberCoin-Qt.exe -connect=ambercoin01.mooo.com" Hash doesn't match.  getblockbynumber 599444 "proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4" what's the connection? getpeerinfo let me help... I'll upload my db |
|
|
|
What should I do if my proofhash does not match? TQ.
delete everything in the ambercoin folder (if you are on windows appdata\roaming\ambercoin) EXCEPT wallet.dat, download the database that dev provided a few pages back and start the wallet with the command AmberCoin-Qt.exe -connect=ambercoin01.mooo.com |
|
|
|
Trying to sync again.
I don't understand firewalls very well, but I tried putting in a restriction. Not sure if it's right or not...
For my four AmberCoin-QT inbound rules, I have restricted the remote address to 108.61.173.201 (ambercoin01.mooo.com).
Resyncing now...
that should work |
|
|
|
"height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
 "height" : 599444, "proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469", |
|
|
|
Would you mind posting a block hash we can check?
"height" : 599378, "proofhash" : " 000000026242e58a968a0e7787ce9467b0acd11f562c3e56bdbb16f38c96855e" I'm off... getblockbynumber 599378 "proofhash" : "0001193641a3c6f5462fb90d56b3259f08edcffc16e874df972b07daabca6c62" *EDIT - Yeah, looking questionable now. I've had 3 POS rewards with confirmations in as many minutes. Now downloading last blockchain Dev provided, and will use "AmberCoin-Qt.exe -connect=ambercoin01.mooo.com" AmberCoin-qt.exe -server -connect=ambercoin01.mooo.com that's my shortcut to ambercoin. Not sure what "-server" does, but I got stuck on the last 12 blocks trying to re-sync, so I closed the wallet and restarted it with the server option as well. It finished syncing and now my hash matchs yours. getblockbynumber 599378 "proofhash" : " 000000026242e58a968a0e7787ce9467b0acd11f562c3e56bdbb16f38c96855e" Thx. -server allows you to solo mine |
|
|
|
|
Show Posts
