Author Topic: synchronization stopped  (Read 7115 times)

fsb4000

  • Newbie
  • *
  • Posts: 19
    • View Profile
synchronization stopped
« on: September 28, 2014, 06:15:09 AM »
The last lines of debug.log
Code: [Select]
SetBestChain: new best=73b3da530b41113b6858  height=370750  work=267949056399051104910479
GameStateCache: storing for block @370750 73b3da530b41113b6858aa0f2e84cf2c8708f88f1ad529feae0f3abcd57ba4bb
GameStateCache: removing block with lowest height 370740
NotifyTransactionChanged ec64e5f258c2d2fec57bd86cee1dc3de422e95999a22633871b11aec942d8268 status=1
ProcessBlock: ACCEPTED @370750 73b3da530b41113b6858 with SHA-256
ResendWalletTransactions()
updateWallet ec64e5f258c2d2fec57bd86cee1dc3de422e95999a22633871b11aec942d8268 1
   inWallet=0 inModel=0 Index=0-0 showTransaction=0 derivedStatus=1
getblocks -1 to 00000000000000000000 limit 500
09/28/14 01:03:22 Flushing wallet.dat
Flushed wallet.dat 26ms
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
IRC got join
AddAddress(202.152.202.152:8398)
IRC got new address: 202.152.202.152:8398
accepted connection 202.152.202.152:53640
Added time data, samples 47, offset -5 (+0 minutes)
-418  -234  -192  -173  -173  -56  -28  -23  -16  -13  -10  -10  -5  -4  -3  -2  -2  +0  +2  +2  +2  +4  +4  +4  +5  +5  +5  +5  +6  +6  +6  +6  +6  +6  +6  +6  +6  +7  +15  +15  +15  +17  +18  +19  +19  +24  +68  |  nTimeOffset = +4  (+0 minutes)
version message: version 1001100, blocks=370394, ip=202.152.202.152:53640
IRC got join
IRC got join
IRC got join
AddAddress(113.134.118.209:8398)
IRC got new address: 113.134.118.209:8398
IRC got join
IRC got join
IRC got join
IRC got join
IRC got join
IRC got join
AddAddress(192.155.88.115:8398)
IRC got new address: 192.155.88.115:8398
IRC got join
IRC got join
IRC got join
IRC got join
AddAddress(114.79.36.1:8398)
IRC got new address: 114.79.36.1:8398
IRC got join
IRC got join
AddAddress(114.125.44.9:8398)
IRC got new address: 114.125.44.9:8398
The last block ~4 hours ago.
Connections 31.
This situation only happens with Huntercoin wallet and Namecoin wallet. (Bitcoin wallet and Novacoin wallet never have this issue)
Approximately happens once in 2-3 days.
After restarting synchronization restore.

Huntercoin QT 1.0.12, Windows 7x64
« Last Edit: September 28, 2014, 06:18:46 AM by fsb4000 »

fsb4000

  • Newbie
  • *
  • Posts: 19
    • View Profile
Re: synchronization stopped
« Reply #1 on: October 02, 2014, 04:34:13 AM »
I tried use huntecoind but again synchronization stuck  :(
Code: [Select]
GameStateCache: storing for block @377696 e56f5ae12d0b40d86d3c3b0721d0e6d42820fcc7bb136a91faa2a70d8e88531c
GameStateCache: removing block with lowest height 377686
ProcessBlock: ACCEPTED @377696 e56f5ae12d0b40d86d3c with scrypt
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
10/02/14 02:52:56 Flushing wallet.dat
Flushed wallet.dat 40ms
getblocks 377694 to 00000000000000000000 limit 500
ResendWalletTransactions()
received block b946fff11f9330be2f2b
SetBestChain: new best=b946fff11f9330be2f2b  height=377697  work=281267551255311451720765
GameStateCache: storing for block @377697 b946fff11f9330be2f2b94dd1b49e6c649517daac47c205bf9d31fdf40134361
GameStateCache: removing block with lowest height 377687
ProcessBlock: ACCEPTED @377697 b946fff11f9330be2f2b with scrypt
10/02/14 02:53:14 Flushing wallet.dat
Flushed wallet.dat 37ms
ResendWalletTransactions()
received block 137bb066af10096f6a34
SetBestChain: new best=137bb066af10096f6a34  height=377698  work=281267557405635592236093
GameStateCache: storing for block @377698 137bb066af10096f6a34b71904f7cc5d3d2b61df8f518d50ff989e2a2a49c734
GameStateCache: removing block with lowest height 377688
ProcessBlock: ACCEPTED @377698 137bb066af10096f6a34 with scrypt
10/02/14 02:54:14 Flushing wallet.dat
Flushed wallet.dat 40ms
ResendWalletTransactions()
IRC got join
IRC got join
AddAddress(114.237.56.87:8398)
IRC got new address: 114.237.56.87:8398
IRC got join
IRC got join
IRC got join
IRC got join

reaper

  • Newbie
  • *
  • Posts: 34
    • View Profile
Re: synchronization stopped
« Reply #2 on: January 04, 2015, 10:13:39 PM »
Having the same issue. Wallet will sync, after that it stops syncing.

Even with new wallet.dat.
« Last Edit: January 04, 2015, 10:18:12 PM by reaper »

redbeans2012

  • Guest
Re: synchronization stopped
« Reply #3 on: January 04, 2015, 11:09:58 PM »
I lose sync once every day or 2.  A restart fixes it for me.   I'm using hte MM client, I think you are too.

reaper

  • Newbie
  • *
  • Posts: 34
    • View Profile
Re: synchronization stopped
« Reply #4 on: January 05, 2015, 01:25:28 AM »
Yeah, I was using MM.  It happens with the Qt as well. It was like that for me too, after a day or two it woulds stop syncing and i would restart. Now will only accept a block or two and stop.

redbeans2012

  • Guest
Re: synchronization stopped
« Reply #5 on: January 05, 2015, 01:42:20 AM »
did you try rescanning the blockchain? restart true in the console?

reaper

  • Newbie
  • *
  • Posts: 34
    • View Profile
Re: synchronization stopped
« Reply #6 on: January 05, 2015, 04:56:23 AM »
Yeah tried rescan yesterday. But I started the Qt and it seems to syncing fine now.
This is weird, the disaster seems to have played a role in fixing my problem. ;D

fsb4000

  • Newbie
  • *
  • Posts: 19
    • View Profile
Re: synchronization stopped
« Reply #7 on: February 17, 2015, 03:20:44 PM »
Just to clarify: For everyone the problem is solved, the synchronization works, and the client can work 24/7, is not it?

Snailbrain

  • Developer
  • Hero Member
  • *****
  • Posts: 1001
    • View Profile
Re: synchronization stopped
« Reply #8 on: February 17, 2015, 04:15:09 PM »
seems so..
do you have any network issues? -

what does your debug.log look like, and from your other post it seems you can still use RPC?

are you using ssd, ram drive or normal hard drive?

did you build yourself or using the ones i have provided?

fsb4000

  • Newbie
  • *
  • Posts: 19
    • View Profile
Re: synchronization stopped
« Reply #9 on: February 17, 2015, 05:06:39 PM »
seems so..
do you have any network issues? -

what does your debug.log look like, and from your other post it seems you can still use RPC?

are you using ssd, ram drive or normal hard drive?

did you build yourself or using the ones i have provided?
I don't have network issues.
Bitcoin core, namecore, novacoin-qt, bitcoindark, NXT are working fine.
Normal Hard drive.
I used https://mega.co.nz/#!gF8hVQIB!IklEUCt0RQpu7RHSl4A0I3VYIXDSkDVhRqBIOA7Jr4w
But now I'm testing my build( I replaced original sync code on the Novacoin sync code)
I hope it helps.
Just wanted to share if someone also have the same problem.
Now synchronization works(I hope sync will not stop and I can sync):
Code: [Select]
{
    "version" : 1020000,
    "balance" : 0.00000000,
    "blocks" : 44800,
    "timeoffset" : -17,
    "connections" : 15,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "algo" : "sha256d",
    "difficulty" : 57213779.19265896,
    "difficulty_sha256d" : 57213779.19265896,
    "difficulty_scrypt" : 109.80548211,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1408128868,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00000001,
    "errors" : ""
}

By the way, is there any reason why you build with gcc4.6 and boost 1.54? (not gcc4.9.2 and boost 1.57?)
« Last Edit: February 17, 2015, 05:08:14 PM by fsb4000 »

Snailbrain

  • Developer
  • Hero Member
  • *****
  • Posts: 1001
    • View Profile
Re: synchronization stopped
« Reply #10 on: February 17, 2015, 06:17:04 PM »
seems so..
do you have any network issues? -

what does your debug.log look like, and from your other post it seems you can still use RPC?

are you using ssd, ram drive or normal hard drive?

did you build yourself or using the ones i have provided?
I don't have network issues.
Bitcoin core, namecore, novacoin-qt, bitcoindark, NXT are working fine.
Normal Hard drive.
I used https://mega.co.nz/#!gF8hVQIB!IklEUCt0RQpu7RHSl4A0I3VYIXDSkDVhRqBIOA7Jr4w
But now I'm testing my build( I replaced original sync code on the Novacoin sync code)
I hope it helps.
Just wanted to share if someone also have the same problem.
Now synchronization works(I hope sync will not stop and I can sync):
Code: [Select]
{
    "version" : 1020000,
    "balance" : 0.00000000,
    "blocks" : 44800,
    "timeoffset" : -17,
    "connections" : 15,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "algo" : "sha256d",
    "difficulty" : 57213779.19265896,
    "difficulty_sha256d" : 57213779.19265896,
    "difficulty_scrypt" : 109.80548211,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1408128868,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00000001,
    "errors" : ""
}

By the way, is there any reason why you build with gcc4.6 and boost 1.54? (not gcc4.9.2 and boost 1.57?)

I have no idea, i know people use different boost around 1.5 for namecoin/hutnercoin and still works..
Huntercoin is based on pre-namecore namecoin.

note that I use easywinbuilder by "phelix" and this remains sort of untouched for a good amount of time (all windows dependencies are fixed in there afaik). Makes compiling very simple (for me :)) it's located in the contrib directory (a load of bat files)

tbh, i don't know how well syncing will go with a mechanical hard drive, although there have been many performance updates since. I assume that when on the latest blocks a mechanical hard drive will be fine, but when you get to around (i think) block no. 90k, things will go insanely slowly.
Domob implemented some fixes which reduced fragmentation ..
also make sure don't sync with wallet (may go much slower).

This is why we need to :- http://forum.huntercoin.org/index.php/topic,732.0.html

keep us updated please and thanks
« Last Edit: February 17, 2015, 06:30:58 PM by Snailbrain »

Snailbrain

  • Developer
  • Hero Member
  • *****
  • Posts: 1001
    • View Profile
Re: synchronization stopped
« Reply #11 on: February 17, 2015, 06:19:19 PM »
if it stops syncing, check debug.log and post here


Snailbrain

  • Developer
  • Hero Member
  • *****
  • Posts: 1001
    • View Profile
Re: synchronization stopped
« Reply #12 on: February 21, 2015, 12:20:26 PM »
btw, still looking into this with fsb and domob
The syncing on windows (after some testing) does seem to stop and requires restart..


reaper

  • Newbie
  • *
  • Posts: 34
    • View Profile
Re: synchronization stopped
« Reply #13 on: February 24, 2015, 04:27:30 AM »
02/24/15 04:06:46 Flushing wallet.dat
Flushed wallet.dat 203ms
getblocks -1 to 00000000000000000000 limit 500
ResendWalletTransactions()
received block b3b0ba45cc676f02eb68
SetBestChain: new best=b3b0ba45cc676f02eb68  height=585353  work=778055939084161539149729
GameStateCache: storing for block @585353 b3b0ba45cc676f02eb686c1e75a7ccf77fcf4651c7918d7e9852ff0deccf931a
GameStateCache: removing block with lowest height 585343
NotifyTransactionChanged 192beb9379cf5db9b99bad9eef7626add71cbc5a484b36e2f5ec85acad3c83a1 status=1
ProcessBlock: ACCEPTED @585353 b3b0ba45cc676f02eb68 with scrypt
updateWallet 192beb9379cf5db9b99bad9eef7626add71cbc5a484b36e2f5ec85acad3c83a1 1
   inWallet=0 inModel=0 Index=0-0 showTransaction=0 derivedStatus=1
02/24/15 04:06:52 Flushing wallet.dat
Flushed wallet.dat 172ms
getblocks -1 to 00000000000000000000 limit 500
ResendWalletTransactions()
received block 459165a7ef57aa414386
SetBestChain: new best=459165a7ef57aa414386  height=585354  work=778056058664421891399585
GameStateCache: storing for block @585354 459165a7ef57aa4143866e38e11aae71e32fa5b04427637f1b08ffcecb9525f4
GameStateCache: removing block with lowest height 585344
NotifyTransactionChanged 16b51ca56cac27924747e920fff301924a76465a7c393171c073805f31503531 status=1
ProcessBlock: ACCEPTED @585354 459165a7ef57aa414386 with scrypt
updateWallet 16b51ca56cac27924747e920fff301924a76465a7c393171c073805f31503531 1
   inWallet=0 inModel=0 Index=0-0 showTransaction=0 derivedStatus=1
getblocks -1 to 00000000000000000000 limit 500
02/24/15 04:07:07 Flushing wallet.dat
Flushed wallet.dat 172ms
ResendWalletTransactions()


stopped 4 or 5 times today

fsb4000

  • Newbie
  • *
  • Posts: 19
    • View Profile
Re: synchronization stopped
« Reply #14 on: February 24, 2015, 09:04:47 AM »
I hope this  https://github.com/chronokings/huntercoin/pull/100 solved the sync issue.

Full pull request changelog:
1) No lost sync(I hope)
2) gcc 4.9, miniupnp 1.9, boost 1.57, openssl 1.0.2  compatibility
(So Huntercoin can be compiled by this instruction https://bitcointalk.org/index.php?topic=149479.msg1587734#msg1587734)
3) Qt is not lagging
4) Quick shutdown
5) Added 2 nodes(67.225.171.185 and 178.62.17.234)
(So people don't have to add "addnode=<IP> in huntercoin.conf")
6) Automatic creation huntercoin.conf (if this file does not exist)
Code: [Select]
rpcuser=user
rpcpassword=<15 random letters>
rpcport=8399
port=8398
#(0=off, 1=on) daemon - run in the background as a daemon and accept commands
daemon=0
#(0=off, 1=on) server - accept command line and JSON-RPC commands
server=1
rpcallowip=127.0.0.1
testnet=0

Now Snailbrain is testing this pull request
You can test too
github: https://github.com/fsb4000/huntercoin/tree/sync
 
(static binary, no needed any dlls)
huntercoin-qt.exe: https://yadi.sk/d/OtQD-wvDepynM
huntercoind.exe: https://yadi.sk/d/lqWHGnOeepysv
« Last Edit: February 24, 2015, 09:29:47 AM by fsb4000 »