Jump to content

unick

daemon is getting behind sync

Recommended Posts

unick

One of my deamons on linux (headless) is getting behind about 30 minutes and I was wondering why?  anybody experienced this issue?

 

the log is full of pending sync-checkpoints like it's being flooded. I assume this is causing the lag in keeping the client up to sync.

07/19/14 16:43:04 ProcessSyncCheckpoint: pending for sync-checkpoint ed920e3857c30f3b79a791a0251dd395544a7503785ecbc5951e642c2a879da4
07/19/14 16:43:04 ProcessSyncCheckpoint: pending for sync-checkpoint c23e7d92314480c1ba9f33c60a6486737d7334cbe8fc6f6d3a30d3938ea835c6
07/19/14 16:43:04 ProcessSyncCheckpoint: pending for sync-checkpoint aee5da48db39e1b9a1bcbe97a0fe0d86bd701a3306c7a7fbb9d0486fd846d50f
07/19/14 16:43:04 ProcessSyncCheckpoint: pending for sync-checkpoint 118e50b8cce85aa90718555837cbf2e715562ce3bb51b5a4014db046bf492401
07/19/14 16:43:04 ProcessSyncCheckpoint: pending for sync-checkpoint c53a5f08fe0e9d22e369aec9c1a8829334ceca1ef659c198b4a0403c20879a4b
07/19/14 16:43:05 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000006ecd763c44c3d5889720cc673f4e88d4b9043182a6aba27ff4e2a96
07/19/14 16:43:05 ProcessSyncCheckpoint: pending for sync-checkpoint 64b17f2fc75fbac621025543d7c40df4c0d282eae55c54af5a816c1e4d0ba853
07/19/14 16:43:05 ProcessSyncCheckpoint: pending for sync-checkpoint 67606c4197be5542b49ddd9ca2a8e9c41e3e6057c956c5e4b36b6409e498d87a
07/19/14 16:43:05 ProcessSyncCheckpoint: pending for sync-checkpoint 84f6b1718869adbacf94c6f96f1db89f89b1fd393a714d3b845397d8035f2ad7
07/19/14 16:43:05 ProcessSyncCheckpoint: pending for sync-checkpoint e937160ed1ddff5389b377ae4ea630fb16216d625f2c3694191f4c6deea87c07
07/19/14 16:43:06 ProcessSyncCheckpoint: pending for sync-checkpoint 3699f0e5c7dcac60e30608517dfa94bbbf078cd7906e33f43c64a541ee74782e
07/19/14 16:43:06 ProcessSyncCheckpoint: pending for sync-checkpoint f773b365dc87b9579105a2889cb213e829383298cea776dce8da1128c326cd8d
07/19/14 16:43:06 ProcessSyncCheckpoint: pending for sync-checkpoint b4d3111e89a27a993cd9c8a225ce70a980ddee3288d2d95e20499a28ca8c4b38
07/19/14 16:43:06 ProcessSyncCheckpoint: pending for sync-checkpoint 1f38a44cadd20b9efa79c4cd8fc18f7296cb0a2e016d4e0de87a30a13e4c95ae
07/19/14 16:43:06 ProcessSyncCheckpoint: pending for sync-checkpoint 21f65809dd6122b04c4f7ded5ba4fdccc48a1aea31e9e7c513314ffb7b3b1403

Share this post


Link to post
Share on other sites
Tranz

Can you look back through the logs and see when you got a normal block in the correct time, and then after you were frozen for a bit. Perhaps that will give a bit more information. But I have not seen this issue.  It almost seems like you are getting the checkpoint but not the block from your peers.

 

How many connections do you allow? I have a win client with 60+ connections and no issues, but my headless linux running on the Pi I only allow 16. In any event both seem to stay up to the second with each other.

 

PI

 

07/21/14 01:36:42 received block 11b4255a4b397542577e sent from 188.165.223.132:7372
07/21/14 01:36:44 SetBestChain: new best=11b4255a4b397542577e  height=1048281  trust=5299304985639  date=07/21/14 01:36:35
07/21/14 01:36:44 ProcessBlock: ACCEPTED
07/21/14 01:36:44 ProcessSyncCheckpoint: sync-checkpoint at 11b4255a4b397542577e7157fbb92b0ec94266d86e5a070b9a1597b83b1b82b0
07/21/14 01:36:45 received block e913dba509e985268f97 sent from 5.39.90.17:7372
07/21/14 01:36:45 SetBestChain: new best=e913dba509e985268f97  height=1048282  trust=5299321763111  date=07/21/14 01:36:41
07/21/14 01:36:45 ProcessBlock: ACCEPTED
07/21/14 01:36:46 ProcessSyncCheckpoint: sync-checkpoint at e913dba509e985268f9796a572d5690e83c8865e565724a1d5131fd765716690
07/21/14 01:36:47 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:48 Flushing wallet.dat
 

 

Win:

 

07/21/14 01:36:40 SetBestChain: new best=11b4255a4b397542577e  height=1048281  trust=5299304985639  date=07/21/14 01:36:35
07/21/14 01:36:40 ProcessBlock: ACCEPTED
07/21/14 01:36:40 received getdata for: block a4329579403832255294
07/21/14 01:36:43 Flushing wallet.dat
07/21/14 01:36:43 accepted connection [2001:0:5ef5:79fb:2040:f26:b5b7:ab92]:51079
07/21/14 01:36:43 Flushed wallet.dat 570ms
07/21/14 01:36:44 getblocks 1044668 to 00000000000000000000 limit 500
07/21/14 01:36:44   getblocks stopping at limit 1045167 0000000003c4fb7c473c
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 ProcessSyncCheckpoint: sync-checkpoint at 11b4255a4b397542577e7157fbb92b0ec94266d86e5a070b9a1597b83b1b82b0
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:44 getblocks -1 to 00000000000000000000 limit 500
07/21/14 01:36:45 getblocks -1 to 00000000000000000000 limit 500
 

Share this post


Link to post
Share on other sites
Tranz

I do also remember reading about older boost version causing an issue with the client getting behind. I can't remember which version for sure.

Share this post


Link to post
Share on other sites
cinnamon_carter

that was supossed to be corrected in 1_55_0 ,  i know it can happen if you build with 1_53_0 

 

seems almost rare/random it happens but it's happend to me

I do also remember reading about older boost version causing an issue with the client getting behind. I can't remember which version for sure.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Cryptocurrenytalk Logo

 

News, information, and discussions about cryptocurrencies, blockchains, technology, and events. Blockchaintalk is your source for advice on what to mine, technical details, new launch announcements, and advice from trusted members of the community. Cryptocurrencytalk is your source for everything crypto. We love discussing the world of cryptocurrencies.

 

   
×
×
  • Create New...

Important Information

By using CRYPTOCURRENCYTALK.COM, you agree to our Terms of Use.