Yeah, sure: Code: 10:30:09 2016-04-27 [INF] BMGR: New valid peer [2001:57a:f301:100:*:*]:5840 (inbound) (/dcrwire:0.0.1/dcrd:0.1.1/) 10:31:41 2016-04-27 [INF] BMGR: New valid peer 178.63.*:*:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.1/) 10:31:43 2016-04-27 [INF] BMGR: Processed 1 block in the last 3m20.8s (4 transactions, height 23077, 2016-04-27 10:31:23 -0500 CDT) 10:35:38 2016-04-27 [INF] BMGR: New valid peer 188.213.*.*:35503 (inbound) (/decred-seeder:0.01/) 10:35:39 2016-04-27 [INF] BMGR: Lost peer 188.213.*:*:35503 (inbound) 10:35:55 2016-04-27 [INF] BMGR: New valid peer 166.78.*:*:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.1/) 10:35:55 2016-04-27 [INF] BMGR: New valid peer 5.249.*:*:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.0.10/) 10:35:58 2016-04-27 [INF] BMGR: New valid peer 178.33.*:*:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.0/) 10:36:40 2016-04-27 [INF] BMGR: Processed 1 block in the last 4m56.94s (6 transactions, height 23078, 2016-04-27 10:36:59 -0500 CDT) 10:37:58 2016-04-27 [INF] BMGR: New valid peer [2604:a880:cad:d0::*:*]:49998 (inbound) (/decred-seeder:0.01/) 10:37:59 2016-04-27 [INF] BMGR: Lost peer [2604:a880:cad:d0::*:*]:49998 (inbound) 10:38:22 2016-04-27 [INF] BMGR: Lost peer [2001:57a:f301:100:*:*]:5840 (inbound) 10:38:35 2016-04-27 [INF] BMGR: New valid peer [2001:57a:f301:100:*:*]:6086 (inbound) (/dcrwire:0.0.1/dcrd:0.1.1/) 10:40:10 2016-04-27 [INF] BMGR: New valid peer [2607:ff48:aa81:800::*:*]:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.0.5/) 10:46:00 2016-04-27 [INF] BMGR: Processed 1 block in the last 9m20.18s (2 transactions, height 23079, 2016-04-27 10:45:53 -0500 CDT) 10:46:56 2016-04-27 [INF] BMGR: New valid peer [2607:f2f8:ae80::*:*]:14141 (inbound) (/decred-seeder:0.01/) 10:46:57 2016-04-27 [INF] BMGR: Lost peer [2607:f2f8:ae80::*:*]:14141 (inbound) 10:47:16 2016-04-27 [INF] BMGR: Processed 1 block in the last 1m16.29s (2 transactions, height 23080, 2016-04-27 10:47:04 -0500 CDT) It isn't showing any errors, just that I lose you at 10:38 and get you back a few seconds later. Looking through logs on my server I don't see anything indicating a connectivity issue either. Straaaaange.
So I actually noticed what I would call a stall right before that time we disconnected. It had been several minutes since I received any data from you when typically I would get a new set of blocks roughly every 10 seconds. I tried to shutdown dcrd by hitting ctrl-c, and then that's when the [ERR] came through. Code: 08:26:48 2016-04-27 [INF] BMGR: Processed 73 blocks in the last 10.04s (210 transactions, height 18333, 2016-04-11 02:54:23 -0700 PDT) 08:30:03 2016-04-27 [ERR] PEER: Can't read message from [2001:4800:7817:104:be76:4eff:fe05:ca1a]:9108 (outbound): read tcp [2001:57a:f301:100:88de:8b3 a:8fc3:660c]:5791->[2001:4800:7817:104:be76:4eff:fe05:ca1a]:9108: wsarecv: An existing connection was forcibly closed by the remote host. After the error message, it appeared to reconnect and continue working for several more minutes until it happened again just a few minutes ago. This time, the stall lasted 30 minutes before I noticed it, but pressing ctrl-c had a different behavior. When I pressed ctrl-c this time, It proceeded to "process 1 block", and I hit it again, and it processed 1 more block. Pressing ctrl-c a third time finally shut down the server. Notice the time stamps between 8:47 and 9:11. There were actually 5 blocks that were mined during that time period. In fact, block # 23085 had been mined prior to my dcrd client learning about block # 23081 as shown below: None of the blocks around this time period took more than 2-3 minutes each to be mined. Code: 08:41:25 2016-04-27 [INF] BMGR: Processed 82 blocks in the last 10.09s (306 transactions, height 23012, 2016-04-27 02:31:01 -0700 PDT) 08:46:00 2016-04-27 [INF] BMGR: Processed 66 blocks in the last 4m35.13s (251 transactions, height 23079, 2016-04-27 08:45:53 -0700 PDT) 08:47:17 2016-04-27 [INF] BMGR: Processed 1 block in the last 1m16.52s (2 transactions, height 23080, 2016-04-27 08:47:04 -0700 PDT) 09:11:14 2016-04-27 [INF] BMGR: Processed 1 block in the last 23m57.58s (1 transaction, height 23081, 2016-04-27 08:49:09 -0700 PDT)
As you surmised, these are both not normal nodes/peers, but crawlers doing the rounds. They don't need to stay connected after they are done pinging and/or getting your node list, so they disconnect.
There does seem to be an issue with the normal dcrd client connecting using ipv6. We'd like to get a few more people with IPv6 addresses to test the connections out and see if the issues we saw are repeatable on multiple clients before submitting a bug report.
Hi @chappjc, Just wondering if you have any idea why my public node is appearing on https://dcrstats.com/map but not on https://decred.monkeyland.io/online.shtml ? My node has been up and running with in-bound peers for around 2 weeks. Will gladly help you debug the issue if you aren't sure what's going on, send me a PM.
I'm having the same issue still. @Dyrk got with the devs and it looks like the problem is with decred-seeder. They're looking into it.
There are ban and ignore lists, and the ban times can be rather long. There were 75303 peers in the ban list! I suspect it's never unbanning. https://github.com/decred/decred-seeder/blob/master/db.h#L121-L127 I'll wipe the lists and initiate a full rescan now. It's going to take several hours though. The other bit is the time between asking known nodes for their list of peers, which is a week in the code. I have it set to 48 hours instead.
There didn't seem to be an issue on github, so I made one: https://github.com/decred/decred-seeder/issues/6
Well, you're still not on my crawler's list. Hopefully the issue with the seeder gets identified and fixed. Or perhaps my crawler just doesn't like Texans.
So I stood up a new node on a new piece of hardware just for the heck of it to see if it would magically appear. This one isn't either and I've been running it for a couple of weeks. It's geographically located in the eastern US. I'm getting connections from all sorts of IPs, so it's being found as a node, but this one isn't being hit by any seeders. IPs are is 74.208.103.245 & 2607:f1c0:84f:d800::7e:9992. Any ideas?
@Halestorm I just queried the 4 DNS seeders to find all the advertised peers, and yours didn't show up. Here's the list of peers I put together from all 4 servers (with duplicates removed) Spoiler: List 104.236.167.133 104.236.243.125 136.243.50.159 139.162.152.204 149.56.122.72 149.56.44.46 155.94.172.95 158.69.193.206 158.69.196.59 159.203.28.85 159.203.96.169 162.243.113.215 162.243.208.249 162.243.226.209 162.243.98.221 162.253.41.190 163.172.24.172 163.172.27.11 167.114.105.58 176.9.137.25 176.9.161.86 176.9.98.82 177.52.181.222 178.236.137.24 178.33.228.14 18.97.5.57 185.39.195.82 185.39.195.83 188.213.166.128 188.213.175.23 191.252.3.4 192.155.92.72 192.155.93.22 192.241.115.4 192.99.233.217 192.99.55.81 194.135.89.219 198.58.124.195 208.94.242.218 212.83.146.45 23.227.190.67 23.253.224.221 24.65.144.89 38.68.15.124 46.102.244.61 51.254.32.88 52.26.180.125 52.33.183.11 52.72.239.88 52.9.127.149 54.175.231.41 62.210.253.159 75.9.96.199 80.236.18.96 81.169.187.209 81.2.247.82 81.31.49.4 89.40.126.183 89.46.74.232 92.222.73.115 93.158.215.188 94.112.96.100 Also, I just connected my IPv6 node to yours via IPv6, so it's definitely working. I really don't know why your node wouldn't be listed by the official DNS without going through the code. On another note, it will be interesting to see if the IPv6 connection is stable now! 16:34:45 2016-06-01 [INF] BMGR: New valid peer [2607:f1c0:84f:d800::7e:9992]:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.3/) 16:34:45 2016-06-01 [INF] BMGR: Syncing to block height 33287 from peer [2607:f1c0:84f:d800::7e:9992]:9108
I am running the DCRD on a VPS with a static IP address, solo PoS mining. How can I make it a full public note and appear on the Active nodes map? (https://dcrstats.com/map) I have read every comments in the thread, but I still don't really understand what else I would need to do.
@Szfinx Keep in mind that you don't need to do this in order to successfully PoS mine solo. The outgoing connections a non-public node creates are sufficient. That said, if you want to be listed (open to unsolicited incoming connections), you'll need to set the "--externalip" option, and open the firewall. If routing is not already set up, you may have to set port forwarding too, but this is usually an automatic 1-to-1 NAT set up by your VPS provider.
1) your VPS has to be accessible from the net, IPv4 is tested better than IPv6 2) enable port 9108 (mainnet; or 19108 testnet) in your firewall 3) start dcrd with --externalip=__YOUR_EXT_IP__ or amend config accordingly
I have been trying to run a public node on a VPS. I have specified the external ip in the config file but even after running it over 48 hours i dont see any incoming connection nor does the IP reflect in any maps (official or dcrstats) tried : - using ipv6 and ipv4 both addresses - netstat shows 9108 is open and listening - no firewalls are installed