 Show Posts
|
|
Pages: [1]
|
|
Thanks. It has been 24 hours and still only 2 connections. I swear when I used to run a full node 6 months ago that it didn't take too long to start ramping up inbound connections. I'll certainly keep an eye on it and return if I'm still at 2 inbound connections.
|
|
|
|
I just compiled and started a full node again recently (after about 6 months) on ubuntu 12.04 (ARM). For some reason I am only seeing 2 inbound connections (and the max of 8 out). I have compiled versions 14.2, 13.1, and 13.2 and have seen the behavior on all three versions. Here is the debug.log information from my last start. I notice that a 3rd in connection will open when I get a version message from bitnodes.21.co, and then it will quickly disappear. Does anyone know why I cannot get more than 2 inbound connections? 2017-07-05 17:40:47 Bitcoin version v0.14.2.0-gfc61c8322bd
2017-07-05 17:40:47 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-07-05 17:40:47 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-07-05 17:40:47 Prune configured to target 100000MiB on disk for block and undo files.
2017-07-05 17:40:48 Default data directory [redacted]
2017-07-05 17:40:48 Using data directory /media/Ext160/Bitcoin/
2017-07-05 17:40:48 Using config file /media/Ext160/Bitcoin/bitcoin.conf
2017-07-05 17:40:48 Using at most 125 automatic connections (1024 file descriptors available)
2017-07-05 17:40:48 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-07-05 17:40:48 Using 4 threads for script verification
2017-07-05 17:40:48 scheduler thread start
2017-07-05 17:40:48 Bound to [::]:8333
2017-07-05 17:40:48 Bound to 0.0.0.0:8333
2017-07-05 17:40:48 Cache configuration:
2017-07-05 17:40:48 * Using 2.0MiB for block index database
2017-07-05 17:40:48 * Using 8.0MiB for chain state database
2017-07-05 17:40:48 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-07-05 17:40:48 init message: Loading block index...
2017-07-05 17:40:48 Opening LevelDB in /media/Ext160/Bitcoin/blocks/index
2017-07-05 17:40:48 Opened LevelDB successfully
2017-07-05 17:40:48 Using obfuscation key for /media/Ext160/Bitcoin/blocks/index: 0000000000000000
2017-07-05 17:40:48 Opening LevelDB in /media/Ext160/Bitcoin/chainstate
2017-07-05 17:40:49 Opened LevelDB successfully
2017-07-05 17:40:49 Using obfuscation key for /media/Ext160/Bitcoin/chainstate: 26a31189c8470808
2017-07-05 17:41:15 LoadBlockIndexDB: last block file = 925
2017-07-05 17:41:15 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=99, size=90529560, heights=474277...474374, time=2017-07-05...2017-07-05)
2017-07-05 17:41:15 Checking all blk files are present...
2017-07-05 17:41:16 LoadBlockIndexDB(): Block files have previously been pruned
2017-07-05 17:41:16 LoadBlockIndexDB: transaction index disabled
2017-07-05 17:41:17 LoadBlockIndexDB: hashBestChain=00000000000000000117dfa34fd2e03182ca2f3ca67ec56dfe11e96b2157cacd height=474374 date=2017-07-05 17:22:03 progress=0.999984
2017-07-05 17:41:17 init message: Rewinding blocks...
2017-07-05 17:41:26 init message: Verifying blocks...
2017-07-05 17:41:26 Verifying last 6 blocks at level 3
2017-07-05 17:41:26 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-07-05 17:45:57 No coin database inconsistencies in last 7 blocks (14995 transactions)
2017-07-05 17:45:57 block index 309325ms
2017-07-05 17:45:57 No wallet support compiled in!
2017-07-05 17:45:57 Unsetting NODE_NETWORK on prune mode
2017-07-05 17:45:57 init message: Pruning blockstore...
2017-07-05 17:45:57 mapBlockIndex.size() = 474376
2017-07-05 17:45:57 nBestHeight = 474374
2017-07-05 17:45:57 torcontrol thread start
2017-07-05 17:45:57 init message: Loading addresses...
2017-07-05 17:45:58 Loaded 42622 addresses from peers.dat 1155ms
2017-07-05 17:45:58 init message: Loading banlist...
2017-07-05 17:45:58 init message: Starting network threads...
2017-07-05 17:45:58 net thread start
2017-07-05 17:45:58 init message: Done loading
2017-07-05 17:45:58 dnsseed thread start
2017-07-05 17:45:58 addcon thread start
2017-07-05 17:45:58 msghand thread start
2017-07-05 17:45:58 opencon thread start
2017-07-05 17:45:58 GUI: Platform customization: "other"
2017-07-05 17:45:59 receive version message: /ViaBTC:bitpeer.0.2.0/: version 70012, blocks=0, us=0.0.0.0:0, peer=0
2017-07-05 17:45:59 Misbehaving: 54.191.174.46:49814 peer=0 (0 -> 1)
2017-07-05 17:45:59 ProcessMessages(headers, 82 bytes) FAILED peer=0
2017-07-05 17:46:05 receive version message: /Satoshi:0.14.1/: version 70015, blocks=474375, us=71.38.110.197:53317, peer=2
2017-07-05 17:46:09 Loading addresses from DNS seeds (could take a while)
2017-07-05 17:46:10 117 addresses found from DNS seeds
2017-07-05 17:46:10 dnsseed thread exit
2017-07-05 17:46:48 UpdateTip: new best=000000000000000000afd12a6c1dff66ecdd6d8c8c040741fc6cc8225b5437a3 height=474375 version=0x20000000 log2_work=86.709421 tx=237116126 date='2017-07-05 17:44:43' progress=0.999998 cache=5.3MiB(6342tx) warning='1 of last 100 blocks have unexpected version'
2017-07-05 17:46:48 receive version message: /Satoshi:0.13.1/: version 70014, blocks=474375, us=71.38.110.197:46165, peer=3
2017-07-05 17:46:50 receive version message: /Satoshi:0.14.0/: version 70015, blocks=474376, us=71.38.110.197:42938, peer=4
2017-07-05 17:47:34 UpdateTip: new best=0000000000000000015150f69bab844021dfa367dfe6aa7b9735e9ae1fb4c867 height=474376 version=0x20000002 log2_work=86.709455 tx=237118003 date='2017-07-05 17:46:44' progress=0.999999 cache=10.0MiB(12014tx) warning='1 of last 100 blocks have unexpected version'
2017-07-05 17:47:34 ProcessMessages(version, 178 bytes) FAILED peer=5
2017-07-05 17:47:41 receive version message: /Satoshi:0.14.0/: version 70015, blocks=474376, us=71.38.110.197:42844, peer=6
2017-07-05 17:47:46 receive version message: /Satoshi:0.14.0/: version 70015, blocks=474376, us=71.38.110.197:33340, peer=7
2017-07-05 17:47:53 receive version message: /Satoshi:0.14.1/: version 70015, blocks=474376, us=71.38.110.197:42480, peer=8
2017-07-05 17:47:53 receive version message: /Satoshi:0.13.1/: version 70014, blocks=474376, us=71.38.110.197:50384, peer=9
2017-07-05 17:47:54 receive version message: /Satoshi:0.14.99/: version 70015, blocks=474376, us=71.38.110.197:39142, peer=10
2017-07-05 17:47:58 connect() to 203.59.228.185:8333 failed after select(): No route to host (113)
2017-07-05 17:48:04 receive version message: /Satoshi:0.14.1(UASF-SegWit-BIP148)/: version 70015, blocks=474376, us=71.38.110.197:43780, peer=11
2017-07-05 17:49:42 receive version message: /bitnodes.21.co:0.1/: version 70015, blocks=474374, us=71.38.110.197:8333, peer=12
2017-07-05 17:50:37 connect() to 178.175.235.72:8333 failed after select(): Connection refused (111)
2017-07-05 17:51:04 receive version message: /Satoshi:0.14.0/: version 70015, blocks=474376, us=71.38.110.197:8333, peer=13
2017-07-05 17:51:04 receive version message: /bitnodes.21.co:0.1/: version 70015, blocks=474376, us=71.38.110.197:8333, peer=14
2017-07-05 17:56:35 receive version message: /bitnodes.21.co:0.1/: version 70015, blocks=474376, us=71.38.110.197:8333, peer=15
2017-07-05 17:58:22 receive version message: /Satoshi:0.13.1/: version 70014, blocks=474377, us=71.38.110.197:42265, peer=16
2017-07-05 17:59:03 Imported mempool transactions from disk: 1445 successes, 5478 failed, 0 expired
2017-07-05 17:59:10 UpdateTip: new best=0000000000000000008040bb8295419ac763910e74b8d5438b117c7c49bbf76f height=474377 version=0x20000002 log2_work=86.70949 tx=237119130 date='2017-07-05 17:52:32' progress=0.999995 cache=235.8MiB(37322tx) warning='1 of last 100 blocks have unexpected version'
2017-07-05 18:00:58 receive version message: /bitnodes.21.co:0.1/: version 70015, blocks=474377, us=71.38.110.197:8333, peer=17
2017-07-05 18:01:25 connect() to 115.206.30.167:8333 failed after select(): Connection refused (111)
2017-07-05 18:06:12 UpdateTip: new best=0000000000000000012a05d7bc7e306525ffcd155e5f0391e2677b2b3b013651 height=474378 version=0x20000002 log2_work=86.709525 tx=237121036 date='2017-07-05 18:06:12' progress=1.000000 cache=253.5MiB(42488tx) warning='1 of last 100 blocks have unexpected version'
2017-07-05 18:06:38 receive version message: /bitnodes.21.co:0.1/: version 70015, blocks=474377, us=71.38.110.197:8333, peer=19
2017-07-05 18:12:15 Pre-allocating up to position 0xc00000 in rev00925.dat
2017-07-05 18:12:16 UpdateTip: new best=00000000000000000078c2351965f436a97135ef46939ecae6acb832c1bff4f1 height=474379 version=0x20000000 log2_work=86.70956 tx=237122542 date='2017-07-05 18:12:04' progress=1.000000 cache=258.6MiB(46913tx) warning='1 of last 100 blocks have unexpected version'
2017-07-05 18:12:21 receive version message: /bitnodes.21.co:0.1/: version 70015, blocks=474378, us=71.38.110.197:8333, peer=21
2017-07-05 18:18:08 receive version message: /bitnodes.21.co:0.1/: version 70015, blocks=474379, us=71.38.110.197:8333, peer=22
2017-07-05 18:18:35 connect() to 200.31.4.105:8333 failed after select(): Connection refused (111) |
|
|
|
|
I've seen it get down to 8 incoming before I have bumped the router. I would assume that even those would eventually drop off as well given time.
The NAT table filling up is kinda what I suspect as well. I'm going to check with Asus to see if there is a way to timeout the connections.
|
|
|
|
I am running a full node with Bitcoin-qt on an ubuntu server (ARM based). The node seems to spin up fine and will start receiving incoming connections. I believe I have seen upwards to about 60 incoming connections. The problem is that after a couple of days the incoming connections will start to drop off. If I reboot my router (Asus RT-AC66U) then it will begin to receive incoming connections, yet after another couple of days they start to drop once again. If I check the status of my node at https://getaddr.bitnodes.io/#join-the-network, initially it will say that my node is up. When the connections begin to drop then that site will report that it can no longer connect to my node. Rebooting the router and it can connect once more. Can anyone give me some insight on what is happening and perhaps a way to correct this problem? I would like to continue running a full node but don't feel like bumping my router ever few days to do so. Thanks. |
|
|
|
|
