Bitcoin Forum
October 12, 2024, 06:51:12 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Bitcoin Forum > Bitcoin > Bitcoin Technical Support > bitcoind recieve version message from 127.0.0.1:8333 every two seconds
Pages: [1]
« previous topic next topic »
  Print  
Author Topic: bitcoind recieve version message from 127.0.0.1:8333 every two seconds  (Read 1171 times)
krile (OP)
Hero Member
*****
Offline Offline

Activity: 746
Merit: 500



View Profile
May 05, 2015, 09:29:41 PM
 #1
Hello,

any idea what is causing this? It just goes on forever, every two seconds. I noticed today that bitcoind crashed, upon restarting it again I followed the log for a while and saw this. 

Code:
2015-05-05 21:19:59 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=516
2015-05-05 21:20:01 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=517
2015-05-05 21:20:02 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=518
2015-05-05 21:20:04 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=519
2015-05-05 21:20:06 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=520
2015-05-05 21:20:08 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=521
2015-05-05 21:20:09 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=522
2015-05-05 21:20:11 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=523
2015-05-05 21:20:13 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=524
2015-05-05 21:20:14 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=525
2015-05-05 21:20:16 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=526
2015-05-05 21:20:18 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=527
2015-05-05 21:20:20 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=528
2015-05-05 21:20:23 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=529
2015-05-05 21:20:25 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=530
2015-05-05 21:20:26 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=531
2015-05-05 21:20:29 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=532
2015-05-05 21:20:30 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=533
2015-05-05 21:20:32 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=534
2015-05-05 21:20:34 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=535
2015-05-05 21:20:37 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=536
2015-05-05 21:20:40 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=537
2015-05-05 21:20:42 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=538
2015-05-05 21:20:45 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=539
2015-05-05 21:20:46 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=540
2015-05-05 21:20:49 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=541
2015-05-05 21:20:51 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=542
2015-05-05 21:20:53 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=543
2015-05-05 21:20:54 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=544
2015-05-05 21:20:56 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=545
2015-05-05 21:20:57 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=546
2015-05-05 21:20:59 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=547
2015-05-05 21:21:01 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=548
2015-05-05 21:21:02 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=549
2015-05-05 21:21:04 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=550
2015-05-05 21:21:06 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=551
2015-05-05 21:21:08 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=552
2015-05-05 21:21:09 receive version message: /breadwallet:1.8/: version 70002, blocks=0, us=86.61.18.19:8333, peer=553
2015-05-05 21:21:09 Added time data, samples 34, offset -8 (+0 minutes)
2015-05-05 21:21:09 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=554
2015-05-05 21:21:12 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=555
2015-05-05 21:21:14 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=556
2015-05-05 21:21:16 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=557
2015-05-05 21:21:17 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=558
2015-05-05 21:21:21 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=559
2015-05-05 21:21:22 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=560
2015-05-05 21:21:23 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=561
2015-05-05 21:21:25 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=562
2015-05-05 21:21:27 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=563
2015-05-05 21:21:28 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=564
2015-05-05 21:21:31 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=565
2015-05-05 21:21:34 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=566
2015-05-05 21:21:36 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=567
2015-05-05 21:21:37 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=568
2015-05-05 21:21:39 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=569
2015-05-05 21:21:41 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001, blocks=355119, us=127.0.0.1:8333, peer=570
FreeBitcoin Faucet
hexafraction
Sr. Member
****
Offline Offline

Activity: 392
Merit: 268

Tips welcomed: 1CF4GhXX1RhCaGzWztgE1YZZUcSpoqTbsJ


View Profile
May 05, 2015, 10:10:19 PM
 #2
Are you running any Java-based Bitcoin applications (including wallets like Multibit)? The fact that the IP is 127.0.0.1 (even if "our" IP) suggests that the loopback interface is being used.

That application might be crashing or doing something weird and abnormal.
I have recently become active again after a long period of inactivity. Cryptographic proof that my account has not been compromised is available.
btchris
Hero Member
*****
Offline Offline

Activity: 672
Merit: 504

a.k.a. gurnec on GitHub


View Profile WWW
May 06, 2015, 04:36:53 PM
Last edit: May 10, 2015, 01:43:50 PM by btchris
 #3
Wumpus (a Bitcoin core dev) noticed the same thing last year: http://bitcoinstats.com/irc/bitcoin-dev/logs/2014/09/11

At the time, he identified them as connections from Blockchain.info, and suspected that it was a bug (of Blockchain.info's custom software).

It seems likely that the connections with that "/BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/" user-agent are (still) from Blockchain.info: here's one (edit: oops, forgot the evidence link, here it is) from March with an IP of 37.187.136.15. Note that markets.blockchain.info currently resolves to that same IP.


Quote from: hexafraction on May 05, 2015, 10:10:19 PM
Are you running any Java-based Bitcoin applications (including wallets like Multibit)? The fact that the IP is 127.0.0.1 (even if "our" IP) suggests that the loopback interface is being used.

That was my first thought too, however the log messages are a little misleading. That "us" IP is the IP which the remote peer claims to be connecting to, however this IP is simply added to the payload of the version message by the remote peer. Nothing restricts the remote peer from lying or being buggy (as seems to be the case here).

(FYI it's there to help bitcoin clients identify their "real" public IP in the case that they're behind NAT).
krile (OP)
Hero Member
*****
Offline Offline

Activity: 746
Merit: 500



View Profile
May 10, 2015, 09:49:43 AM
 #4
Well it stopped doing this when it reached peer=1500. And no I am not running anything else apart from bitcoind, so this has to have come from the outside...

But bitcoind crashed on me a few more times, this error: https://github.com/bitcoin/bitcoin/issues/5668

I deleted the blocks folder and did a resync, everything is normal since. And I have to give a big hand of applause to bitcoind 10.1, it resynced in half a day from scratch.

But I must say I never thought that there would be so much hassle with running a node, in a months time I had quite a few errors, database corruptions especially...
FreeBitcoin Faucet
Pages: [1]
  Print  
Bitcoin Forum > Bitcoin > Bitcoin Technical Support > bitcoind recieve version message from 127.0.0.1:8333 every two seconds
 « previous topic next topic »
 
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!