Bitcoin Forum
June 14, 2024, 12:15:53 PM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: bitcoind -testnet - error- Potential stale tip detected  (Read 227 times)
jrian (OP)
Jr. Member
*
Offline Offline

Activity: 39
Merit: 6


View Profile
January 31, 2018, 11:34:03 AM
 #1

Hello!

Trying to run  bitcoind -testnet on new server, got this error in debug.log

2018-01-27 14:11:32 init message: Done loading
2018-01-27 14:11:32 msghand thread start
2018-01-27 14:11:32 opencon thread start
2018-01-27 14:11:43 Loading addresses from DNS seeds (could take a while)
2018-01-27 14:11:43 1 addresses found from DNS seeds
2018-01-27 14:11:43 dnsseed thread exit
2018-01-27 14:43:47 Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
2018-01-27 14:54:17 Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago)
2018-01-27 15:04:47 Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago)


I dont have problems with testnet on other servers. google says nothing. anyone?
aleksej996
Sr. Member
****
Offline Offline

Activity: 490
Merit: 389


Do not trust the government


View Profile
January 31, 2018, 12:51:28 PM
 #2

You might have a problem with connection to other peers.
Have you changed the bitcoin.conf in the testnet subdirectory?
What does your client return when you run "bitcoin-cli -testnet getpeerinfo" ?
AdolfinWolf
Legendary
*
Offline Offline

Activity: 1946
Merit: 1427


View Profile
January 31, 2018, 04:08:43 PM
 #3

The error you have is usually received when something is stopping you from connecting... (duh).

It seems that you might be running bitcoind with -connect=0, or something similar ( bitcoin core not having access to any network, as above user mentioned.)? Could you check that?


jrian (OP)
Jr. Member
*
Offline Offline

Activity: 39
Merit: 6


View Profile
February 01, 2018, 06:47:54 PM
 #4

The error you have is usually received when something is stopping you from connecting... (duh).

It seems that you might be running bitcoind with -connect=0, or something similar ( bitcoin core not having access to any network, as above user mentioned.)? Could you check that?
I'm always use the same bitcoin.conf - and only one server refuse to work with testnet

You might have a problem with connection to other peers.
Have you changed the bitcoin.conf in the testnet subdirectory?
What does your client return when you run "bitcoin-cli -testnet getpeerinfo" ?

I just run bitcoind in testnet, and now its connected to 6 nodes. I dont know why few days ago I had a problem, but thank you anyway Smiley
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!