Bitcoin core 0.11.0 losing nodes/peers while syncing...

[SolidStateSurvivor]

Anyone have this problem or read about it somewhere? While I am syncing my 0.11.0 on windows, over time the 8-12 nodes/peers go from ping time xxx ms to N/A and it stops DL blocks. Is this a rare bug or? It takes about 30-90 mins or so, but it is like they keep disconnecting after a while.

So I have to re-start it and it takes forever to sync the wallet, some days.

Any ideas?

[1715195666]

1715195666

[1715195666]

1715195666

[1715195666]

1715195666

[shorena]

Anyone have this problem or read about it somewhere? While I am syncing my 0.11.0 on windows, over time the 8-12 nodes/peers go from ping time xxx ms to N/A and it stops DL blocks. Is this a rare bug or? It takes about 30-90 mins or so, but it is like they keep disconnecting after a while.

So I have to re-start it and it takes forever to sync the wallet, some days.

Any ideas?

I noticed a low number of connections while syncing my node (Ubuntu VPS) as well. In my case I had close to 100% CPU load I suspected that connections get closed because of that. Now that its synced the number of connections grows steadily. Is your CPU (or maybe RAM) maxed out as well? Another think I could imagine is a connection reset, e.g. if you get a forced disconnect on a DSL line.

[SolidStateSurvivor]

Yeah, CPU load goes pretty high while doing sync, jumps between 75-95% or so, most of the time, the RAM usage isn't nearly as bad, but 60-70%.

[manselr]

This used to happen to me coupled with forever increasing ram usage by bitcoin-qt executable, it turns out it was a memory leak caused by a faulty ram slot (not stick but actual slot in the motherboard). I had to buy a new computer basically, then it worked okay. It sucks when you waste a lot of time trying to solve a problem and then you find out the actual computer was screwed up beyond repair.

[^.^]

I can say this is safely bitcoin cores fault... Doing the same on my node not to mention its sooo slow at reindexing. Looks like a bug somewhere in the program

[Hannu]

Anyone have this problem or read about it somewhere? While I am syncing my 0.11.0 on windows, over time the 8-12 nodes/peers go from ping time xxx ms to N/A and it stops DL blocks. Is this a rare bug or? It takes about 30-90 mins or so, but it is like they keep disconnecting after a while.

So I have to re-start it and it takes forever to sync the wallet, some days.

Any ideas?

Windows and linux server is easy to configure. You just need install bitcoin core.
Raspnode is diffrent.

[chaintool]

Hey,

I have been syncing for 5 days now and I'm still only at 30GB. Looks like I now get 3 GB a day? The whole blockchain is 60GB and growing...

I run Bitcoin Core version v0.11.0 (64-bit) on OS X 10.10.5

My CPU's are cold, there's very little memory pressure...

Process name    CPU% CPU Time         Threads
Bitcoin Core   38,2   12:44:25,86   22   

My network traffic has huge periods of inactivity, I tried -addnode with 20 peers from blockchain.info/peers but can't get more than 8 outbound and 1 or 2 inbound connections?

I have say this is unworkable, running a full node is too much hassle. Does any one else have these problems?

[doof]

Anyone have this problem or read about it somewhere? While I am syncing my 0.11.0 on windows, over time the 8-12 nodes/peers go from ping time xxx ms to N/A and it stops DL blocks. Is this a rare bug or? It takes about 30-90 mins or so, but it is like they keep disconnecting after a while.

So I have to re-start it and it takes forever to sync the wallet, some days.

Any ideas?

I noticed a low number of connections while syncing my node (Ubuntu VPS) as well. In my case I had close to 100% CPU load I suspected that connections get closed because of that. Now that its synced the number of connections grows steadily. Is your CPU (or maybe RAM) maxed out as well? Another think I could imagine is a connection reset, e.g. if you get a forced disconnect on a DSL line.

I've just setup 3 VPS.  Was about to post here.  After 3days, none of them have more than 8 connections.  Doing a port scan on them, Macs Network Util says port 8333 is open.

I've also tried adding nodes via the addnode=xxx.xxx.xxx.xxx in bitcoin.conf but no luck either.

[doof]

Anyone have this problem or read about it somewhere? While I am syncing my 0.11.0 on windows, over time the 8-12 nodes/peers go from ping time xxx ms to N/A and it stops DL blocks. Is this a rare bug or? It takes about 30-90 mins or so, but it is like they keep disconnecting after a while.

So I have to re-start it and it takes forever to sync the wallet, some days.

Any ideas?

I noticed a low number of connections while syncing my node (Ubuntu VPS) as well. In my case I had close to 100% CPU load I suspected that connections get closed because of that. Now that its synced the number of connections grows steadily. Is your CPU (or maybe RAM) maxed out as well? Another think I could imagine is a connection reset, e.g. if you get a forced disconnect on a DSL line.

I've just setup 3 VPS.  Was about to post here.  After 3days, none of them have more than 8 connections.  Doing a port scan on them, Macs Network Util says port 8333 is open.

I've also tried adding nodes via the addnode=xxx.xxx.xxx.xxx in bitcoin.conf but no luck either.

As soon as one completed syncing node count went up.

[zvs]

(Underpowered) nodes while syncing will usually timeout on new connects (the further you get down the blockchain, the more time it takes to validate new batches of blocks == huge latency for bitcoind)

ed:  if it takes 3 days to sync, then i don't know if this node should be running client.   For this Supermicro 6-bay Opteron 1381 8GB RAM on Dacentec, it took about 8 hours.  That's only 3050 or so on passmark?

(and cpu load xx% doesn't mean so much on a VPS, if you've been running it for days, you are probably throttled heavily)