search

soteria-dag / soterd

A GoLang Implementation of Soteria DAG Protocol Daemon
http://www.soteriadag.org
ISC License
14 stars 9 forks source link

cpuminers are out of sync #6

Open totaloutput opened 5 years ago

totaloutput commented 5 years ago

I have 2 cpuminers, they were synced, after a week of running it appears they are out of sync. Steps to reproduce the behavior: Don't really know what triggered them out of sync, still digging through logs. here is the current getdagtips output:

$ soterctl  --testnet --rpcuser=USER --rpcpass=PASS --rpcserver=134.209.59.43:5071 --skipverify getdagtips
{
  "tips": [
    "000000199766f00f0beb776c919fa6b322a5525221aaa5c66b80a36adb24434c"
  ],
  "hash": "ab494e8d1bc0f2f023c680dc71838a845807f7c6ba8b5598ea371b2a5a46532d",
  "minheight": 4305,
  "maxheight": 4305,
  "blkcount": 5078
}
$ soterctl  --testnet --rpcuser=USER --rpcpass=PASS --rpcserver=192.241.147.9:5071 --skipverify getdagtips
{
  "tips": [
    "000000048deeba7a88b85b2bf079a6445c6d28749f661aa48f27c52f82bfe6de"
  ],
  "hash": "3245ef195b5812662890a2302dd0b3904eb09d5b6ea4337658165ec50fe4b9df",
  "minheight": 4325,
  "maxheight": 4325,
  "blkcount": 5099
}
totaloutput commented 5 years ago

seems miner 192. is still moving forward... miner 134. stuck somewhere...

{
  "tips": [
    "00000006a2c0994789a28288bc615cd7fdcf1cd8ec9dd2341ae316ed07a12ee3"
  ],
  "hash": "9c7830f46ea48b9b5f8b3d5098843b273bdcf01489d7151f99d4bdb56182246c",
  "minheight": 4326,
  "maxheight": 4326,
  "blkcount": 5100
}

looks like 134. is trying to sync with 192.:

2019-05-13 15:31:31.533 [INF] SYNC: Syncing to block height 4320 from peer 192.241.147.9:42726
2019-05-13 15:31:31.549 [DBG] SRVR: New peer 192.241.147.9:42726 (inbound)
2019-05-13 15:31:31.549 [DBG] PEER: Sending verack to 192.241.147.9:42726 (inbound)
2019-05-13 15:31:31.549 [DBG] PEER: Sending getblocks (locator 4302, stop 0000000000000000000000000000000000000000000000000000000000000000) to 192.241.147.9:42726 (inbound)
2019-05-13 15:31:31.639 [DBG] PEER: Received getaddr from 192.241.147.9:42726 (inbound)
2019-05-13 15:31:36.720 [DBG] PEER: Received version (agent /soterwire:0.6.0/soterd:2.1.1/, pver 70013, block 4320) from 192.241.147.9:42728 (inbound)
2019-05-13 15:31:36.731 [DBG] PEER: Negotiated protocol version 70013 for peer 192.241.147.9:42728 (inbound)
2019-05-13 15:31:36.732 [DBG] PEER: Sending version (agent /soterwire:0.6.0/soterd:2.1.1/, pver 70013, block 4302) to 192.241.147.9:42728 (inbound)
2019-05-13 15:31:36.732 [DBG] PEER: Connected to 192.241.147.9:42728
2019-05-13 15:31:36.732 [INF] SYNC: New valid peer 192.241.147.9:42728 (inbound) (/soterwire:0.6.0/soterd:2.1.1/)
2019-05-13 15:31:36.734 [DBG] SRVR: New peer 192.241.147.9:42728 (inbound)
2019-05-13 15:31:36.734 [DBG] PEER: Sending verack to 192.241.147.9:42728 (inbound)
2019-05-13 15:31:36.860 [INF] SYNC: Lost peer 192.241.147.9:42728 (inbound)
2019-05-13 15:31:36.860 [DBG] SRVR: Removed peer 192.241.147.9:42728 (inbound)
2019-05-13 15:31:40.973 [DBG] PEER: Received verack from 192.241.147.9:42726 (inbound)
2019-05-13 15:31:40.973 [INF] SYNC: Lost peer 192.241.147.9:42726 (inbound)
2019-05-13 15:31:41.012 [DBG] SRVR: Removed peer 192.241.147.9:42726 (inbound)
2019-05-13 15:31:41.970 [DBG] PEER: Received version (agent /soterwire:0.6.0/soterd:2.1.1/, pver 70013, block 4320) from 192.241.147.9:42730 (inbound)
2019-05-13 15:31:41.974 [DBG] PEER: Negotiated protocol version 70013 for peer 192.241.147.9:42730 (inbound)
2019-05-13 15:31:41.974 [DBG] PEER: Sending version (agent /soterwire:0.6.0/soterd:2.1.1/, pver 70013, block 4302) to 192.241.147.9:42730 (inbound)
2019-05-13 15:31:41.974 [DBG] PEER: Connected to 192.241.147.9:42730
2019-05-13 15:31:41.975 [INF] SYNC: New valid peer 192.241.147.9:42730 (inbound) (/soterwire:0.6.0/soterd:2.1.1/)
2019-05-13 15:31:41.989 [INF] SYNC: Syncing to block height 4320 from peer 192.241.147.9:42730
totaloutput commented 5 years ago

seems 192.* reach it's limit:

2019-05-13 12:17:16.420 [DBG] MINR: Hash speed:    434 kilohashes/s
2019-05-13 12:17:17.695 [DBG] CMGR: Attempting to connect to 134.209.59.43:5070 (reqid 1)
2019-05-13 12:17:17.775 [DBG] CMGR: Connected to 134.209.59.43:5070 (reqid 1)
2019-05-13 12:17:17.776 [DBG] PEER: Sending version (agent /soterwire:0.6.0/soterd:2.1.1/, pver 70013, block 4297) to 134.209.59.43:5070 (outbound)
2019-05-13 12:17:17.872 [DBG] PEER: Received version (agent /soterwire:0.6.0/soterd:2.1.1/, pver 70013, block 4292) from 134.209.59.43:5070 (outbound)
2019-05-13 12:17:17.872 [DBG] PEER: Negotiated protocol version 70013 for peer 134.209.59.43:5070 (outbound)
2019-05-13 12:17:17.874 [DBG] AMGR: No worthy address for 134.209.59.43:5070
2019-05-13 12:17:17.874 [DBG] PEER: Connected to 134.209.59.43:5070
2019-05-13 12:17:17.874 [INF] SYNC: New valid peer 134.209.59.43:5070 (outbound) (/soterwire:0.6.0/soterd:2.1.1/)
2019-05-13 12:17:17.876 [WRN] SYNC: No sync peer candidates available
2019-05-13 12:17:17.876 [INF] SRVR: Max peers reached [125] - disconnecting peer 134.209.59.43:5070 (outbound)
2019-05-13 12:17:17.877 [INF] SYNC: Lost peer 134.209.59.43:5070 (outbound)
2019-05-13 12:17:17.877 [DBG] CMGR: Disconnected from 134.209.59.43:5070 (reqid 1)
2019-05-13 12:17:17.877 [DBG] CMGR: Reconnecting to 134.209.59.43:5070 (reqid 1)
2019-05-13 12:17:17.877 [DBG] CMGR: Retrying connection to 134.209.59.43:5070 (reqid 1) in 5s
totaloutput commented 5 years ago

However, getpeerinfo only shows one peer:

$ soterctl  --testnet --rpcuser=USER --rpcpass=PASS --rpcserver=node2:5071 --skipverify getpeerinfo
[
  {
    "id": 53926,
    "addr": "159.203.31.237:52308",
    "addrlocal": "172.17.0.2:5070",
    "services": "00000013",
    "relaytxes": true,
    "lastsend": 1557767316,
    "lastrecv": 1557767316,
    "bytessent": 449318,
    "bytesrecv": 124663,
    "conntime": 1557666131,
    "timeoffset": 0,
    "pingtime": 56523,
    "pingwait": 103705788.076,
    "version": 70013,
    "subver": "/soterwire:0.6.0/soterd:2.1.1/",
    "inbound": true,
    "startingheight": 3390,
    "currentheight": 3752,
    "banscore": 0,
    "feefilter": 0,
    "syncnode": false
  }
]
totaloutput commented 5 years ago

current workaround is to restart miner.