Current Client Version: v0.10.4.0

Author Topic: SXC wallet doesn't sync after upgrade  (Read 266 times)

Mr.Eddy

  • Fresh Meat
  • ****
  • Posts: 3
  • Karma: +0/-0
SXC wallet doesn't sync after upgrade
« on: August 18, 2017, 10:23:22 pm »
Hi,

I've recently compiled the new wallet (Sexcoin Core version v0.10.4.1-0e3c677 (64-bit)) in my Ubuntu 16.04.3 LTS machine and it gets stuck trying to synchronize with the network. I've used the bootstrap.dat as described in the github page and it worked fine with the first blocks but now i can only see the following in the debug.log


2017-08-18 22:16:01 ProcessMessage(headers, 162003 bytes) FAILED peer=7
2017-08-18 22:16:01 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-18 22:16:01 ERROR: invalid header received
2017-08-18 22:16:01 ProcessMessage(headers, 162003 bytes) FAILED peer=5
2017-08-18 22:16:01 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-18 22:16:01 ERROR: invalid header received
2017-08-18 22:16:01 ProcessMessage(headers, 162003 bytes) FAILED peer=6
2017-08-18 22:16:02 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-18 22:16:02 ERROR: invalid header received
2017-08-18 22:16:02 ProcessMessage(headers, 162003 bytes) FAILED peer=3


Any clues how to fix this ?. Thanks

Nerull

  • Slutcard Project
  • Pole Dancer
  • ***
  • Posts: 37
  • Karma: +3/-0
Re: SXC wallet doesn't sync after upgrade
« Reply #1 on: August 19, 2017, 04:59:20 am »
when lava gets on he can prolly give a better answer but i would first check to make sure the bootstrap checksum is ok (http://wiki.sexcoin.info/index.php/Bootstrap.dat). After saving wallet.dat try to rebuild and sync again with bootstrap. If that doesnt work try again letting it network sync until someone can give you a better answer. Sorry i cant be of much help

One last thing, start up the wallet then after its loaded up close it down then copy the bootstrap over.

lavajumper

  • Administrator
  • Porn Star
  • *****
  • Posts: 241
  • Karma: +9/-0
Re: SXC wallet doesn't sync after upgrade
« Reply #2 on: August 19, 2017, 04:03:56 pm »
This is an odd failure.

What's the date on your bootstrap file?
Did you have any issues building the client?
Are you running the daemon or the GUI client?

To get more information, run with the '-debug' option.




Mr.Eddy

  • Fresh Meat
  • ****
  • Posts: 3
  • Karma: +0/-0
Re: SXC wallet doesn't sync after upgrade
« Reply #3 on: August 19, 2017, 09:45:00 pm »
Hey guys,

Thanks for the prompt reply. I've removed everything in my ~/.sexcoin directory, copied over my backup wallet.dat and the bootstrap.dat and i still receive the same error in the logs.

Regarding the bootstrap.dat file date and checksum :

pablo@testbench:~$ sha256sum bootstrap.dat.gz
ea680573dea3ccc195877e825885c892ed76e3561a75de5d5c6fbefd4d814ec1  bootstrap.dat.gz
pablo@testbench:~$ ls -ld bootstrap.dat.gz
-rw-rw---- 1 pablo pablo 722097389 Jul  1 23:28 bootstrap.dat.gz

Regarding the compilation i did have some issues, somehow it detected that I'm using LibreSSL which I'm not and refused to compile, i managed to fix this by using an older version of libssl (libssl-dev_1.0.2g-1ubuntu4.8_amd64.deb).

I'm running the wallet using "sexcoin-qt -dbcache=2048 -debug", in the logs i get the following :

2017-08-19 21:25:07 Added 5 addresses from 62.152.54.44: 9 tried, 3753 new
2017-08-19 21:25:09 received: pong (8 bytes) peer=2
2017-08-19 21:25:09 received: addr (421 bytes) peer=2
2017-08-19 21:25:09 received: inv (37 bytes) peer=2
2017-08-19 21:25:09 got inv: block 503610c3c6d28fccd51e79265350a29b51091487780937be868027e6ab266994  new 2
2017-08-19 21:25:09 sending: getheaders (1093 bytes) peer=2
2017-08-19 21:25:09 getheaders (2179682) 503610c3c6d28fccd51e79265350a29b51091487780937be868027e6ab266994 to peer=2
2017-08-19 21:25:10 received: addr (24603 bytes) peer=7
2017-08-19 21:25:10 Added 20 addresses from 2a01:e34:ef8b:c700:834:b36:7473:8287: 9 tried, 3752 new
2017-08-19 21:25:11 received: headers (162003 bytes) peer=2
2017-08-19 21:25:11 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:25:11 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:25:11 ProcessMessage(headers, 162003 bytes) FAILED peer=2
2017-08-19 21:25:14 received: addr (5851 bytes) peer=6
2017-08-19 21:26:16 received: inv (37 bytes) peer=2
2017-08-19 21:26:16 got inv: block 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa  new 2
2017-08-19 21:26:16 sending: getheaders (1093 bytes) peer=2
2017-08-19 21:26:16 getheaders (2179682) 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa to peer=2
2017-08-19 21:26:16 received: inv (37 bytes) peer=1
2017-08-19 21:26:16 got inv: block 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa  new 1
2017-08-19 21:26:16 sending: getheaders (1093 bytes) peer=1
2017-08-19 21:26:16 getheaders (2179682) 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa to peer=1
2017-08-19 21:26:16 received: inv (37 bytes) peer=8
2017-08-19 21:26:16 got inv: block 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa  new 8
2017-08-19 21:26:16 sending: getheaders (1093 bytes) peer=8
2017-08-19 21:26:16 getheaders (2179682) 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa to peer=8
2017-08-19 21:26:16 received: inv (37 bytes) peer=3
2017-08-19 21:26:16 got inv: block 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa  new 3
2017-08-19 21:26:16 sending: getheaders (1093 bytes) peer=3
2017-08-19 21:26:16 getheaders (2179682) 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa to peer=3
2017-08-19 21:26:16 received: inv (37 bytes) peer=5
2017-08-19 21:26:16 got inv: block 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa  new 5
2017-08-19 21:26:16 sending: getheaders (1093 bytes) peer=5
2017-08-19 21:26:16 getheaders (2179682) 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa to peer=5
2017-08-19 21:26:16 received: headers (162003 bytes) peer=1
2017-08-19 21:26:16 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:26:16 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:26:16 ProcessMessage(headers, 162003 bytes) FAILED peer=1
2017-08-19 21:26:16 received: inv (37 bytes) peer=4
2017-08-19 21:26:16 got inv: block 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa  new 4
2017-08-19 21:26:16 sending: getheaders (1093 bytes) peer=4
2017-08-19 21:26:16 getheaders (2179682) 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa to peer=4
2017-08-19 21:26:16 received: inv (37 bytes) peer=6
2017-08-19 21:26:16 got inv: block 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa  new 6
2017-08-19 21:26:16 sending: getheaders (1093 bytes) peer=6
2017-08-19 21:26:16 getheaders (2179682) 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa to peer=6
2017-08-19 21:26:16 received: headers (162003 bytes) peer=2
2017-08-19 21:26:16 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:26:16 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:26:16 ProcessMessage(headers, 162003 bytes) FAILED peer=2
2017-08-19 21:26:16 received: headers (162003 bytes) peer=3
2017-08-19 21:26:16 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:26:16 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:26:16 ProcessMessage(headers, 162003 bytes) FAILED peer=3
2017-08-19 21:26:16 received: headers (162003 bytes) peer=8
2017-08-19 21:26:16 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:26:16 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:26:16 ProcessMessage(headers, 162003 bytes) FAILED peer=8
2017-08-19 21:26:17 received: headers (162003 bytes) peer=5
2017-08-19 21:26:17 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:26:17 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:26:17 ProcessMessage(headers, 162003 bytes) FAILED peer=5
2017-08-19 21:26:17 received: inv (37 bytes) peer=7
2017-08-19 21:26:17 got inv: block 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa  new 7
2017-08-19 21:26:17 sending: getheaders (1093 bytes) peer=7
2017-08-19 21:26:17 getheaders (2179682) 38375fd30adfb3de400e1a5d1f28fbafb622dd93c0a1e23116518d663d3f3eaa to peer=7
2017-08-19 21:26:17 received: headers (162003 bytes) peer=6
2017-08-19 21:26:17 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:26:17 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:26:17 ProcessMessage(headers, 162003 bytes) FAILED peer=6
2017-08-19 21:26:18 received: headers (162003 bytes) peer=4
2017-08-19 21:26:18 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:26:18 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:26:18 ProcessMessage(headers, 162003 bytes) FAILED peer=4
2017-08-19 21:26:18 received: headers (162003 bytes) peer=7
2017-08-19 21:26:18 ERROR: AcceptBlockHeader : block is marked invalid
2017-08-19 21:26:18 Invalid header: (version 1)ERROR: invalid header received
2017-08-19 21:26:18 ProcessMessage(headers, 162003 bytes) FAILED peer=7
2017-08-19 21:26:41 GUI: requestShutdown : Requesting shutdown
2017-08-19 21:26:41 GUI: shutdown : Running Shutdown in thread



lavajumper

  • Administrator
  • Porn Star
  • *****
  • Posts: 241
  • Karma: +9/-0
Re: SXC wallet doesn't sync after upgrade
« Reply #4 on: August 20, 2017, 05:21:37 pm »
We've seen a similar problem on Arch Linux, and have been having a difficult time chasing it down.

There is a ppa for openSSL, which might be the issue (but only a guess at the moment). Take a look at these instructions:

https://sexcoinforum.com/index.php?topic=170.msg898#msg898

This is what I have used to build on ubu16. It would be good to get some confirmation if you don't mind mucking about in it.
I'll start running some tests on one of my 16 machines and see if I can reproduce the error.

Also, Do you have something like this somewhere in your debug.log file:

Code: [Select]
Load block from disk: 0.74ms [28.24s]

EDIT: There is not a ppa for openSSL... my bad.
« Last Edit: August 20, 2017, 05:43:16 pm by lavajumper »

lavajumper

  • Administrator
  • Porn Star
  • *****
  • Posts: 241
  • Karma: +9/-0
Re: SXC wallet doesn't sync after upgrade
« Reply #5 on: August 20, 2017, 10:55:18 pm »
Also, can you paste the last log entry that starts with "UpdateTip."

Did you at some point install an openssl > version 1.0.2g ? On my 16, Ubuntu's default version is 1.0.2g.

could you post the output of:
Code: [Select]
sudo lsb_release -a

What is the block height at the time you start seeing the failure?

« Last Edit: August 20, 2017, 11:11:12 pm by lavajumper »

Mr.Eddy

  • Fresh Meat
  • ****
  • Posts: 3
  • Karma: +0/-0
Re: SXC wallet doesn't sync after upgrade
« Reply #6 on: August 22, 2017, 03:00:30 pm »
Hi Guys,

I managed to fix the problem. Somehow when my original wallet.dat and bootstrap.dat were present i had this problem so I've tried once again but only using the bootstrap.dat and waiting for the sync to be complete. After that i deleted the newly generated wallet.dat and copied over the real one and problem fixed :)

Thanks again for all the help.

lavajumper

  • Administrator
  • Porn Star
  • *****
  • Posts: 241
  • Karma: +9/-0
Re: SXC wallet doesn't sync after upgrade
« Reply #7 on: September 28, 2017, 02:05:07 am »
Could you clarify "uploaded a new version"?

You're looking like ban-bait right now.

Timelord2067

  • #WhoviansAU
  • Porn Star
  • **
  • Posts: 203
  • Karma: +7/-0
  • Piss is the new Cum
    • Science Fiction, Fantasy and Horror (and) Conventions Forum #SFFHCF
Re: SXC wallet doesn't sync after upgrade
« Reply #8 on: September 28, 2017, 04:30:25 am »
Could you clarify "uploaded a new version"?

You're looking like ban-bait right now.

I'm certain I baned someone else recently who typed that same thing in - PS look at the two UID's prior to your post, the first two numbers of their IP are identical

*edit* seems like I didn't...
« Last Edit: September 28, 2017, 04:32:34 am by Timelord2067 »
BTC 1SExsxcbXWkuRbhLhKG1w8KgXp1eY1GbN | SXC SEXYKUp7CYWKLWr54UtBKVnfjoN13Ybpha | http://tinyurl.com/CryptopiaSexCoin