jtgrassie / monero-pool

A Monero mining pool server written in C
BSD 3-Clause "New" or "Revised" License
351 stars 124 forks source link

Possible issue with my pool? #32

Closed Emperornero closed 4 years ago

Emperornero commented 4 years ago

Trying to mine on a new pool I've set up and the miner keeps submitting bad shares because I THINK (?) the algo is not defaulting to rx/0.

My config for my xmr-node-proxy looks like this:

{
  "pools": [
    {
      "hostname": "192.168.1.8",
      "port": 4242,
      "ssl": false,
      "allowSelfSignedSSL": false,
      "share": 100,
      "username": "47LXHrn4rqrQ2f395s5gHsMLechiLvnpS9Gt5N6q45UyfA5RSHVdDHGTdviokJt93WXnUnWYHGELc7z7Wc6rbgUNCQ5X4wp",
      "password": "x",
      "keepAlive": true,
      "algo": "rx/0",
      "algo_perf": { "rx/0": 1, "rx/loki": 1 },
      "blob_type": "cryptonote",
      "default": true
    }
  ],
  "listeningPorts": [
    {
      "port": 8080,
      "ssl": false,
      "diff": 10000
    },
    {
      "port": 8443,
      "ssl": true,
      "diff": 10000
    },
    {
      "port": 3333,
      "ssl": false,
      "diff": 1000,
      "algo": "rx/0"
    },
    {
      "port": 1111,
      "ssl": false,
      "diff": 1
    }
  ],
  "bindAddress": "0.0.0.0",
  "developerShare": 1,
  "daemonAddress": "127.0.0.1:18081",
  "accessControl": {
    "enabled": false,
    "controlFile": "accessControl.json"
  },
  "httpEnable": false,
  "httpAddress": "127.0.0.1",
  "httpPort": "8081",
  "httpUser": "",
  "httpPass": "",
  "addressWorkerID": false,
  "minerInactivityTime": 120,
  "keepOfflineMiners": 0,
  "refreshTime": 30,
  "theme": "light",
  "coinSettings": {
    "xmr":{
      "minDiff": 1,
      "maxDiff": 10000000,
      "shareTargetTime": 30
    }
  }
}

and the pool errors are


05:54:30 TRACE src/pool.c:2383: Submission reserved values: 1061 26 1 1
05:54:30 DEBUG src/pool.c:2446: Invalid share
05:54:30 TRACE src/pool.c:2311: Client submitted nonce=66689, result=4131e3bc6769d2f0ed76d3e832e20d7fea03f012dbe4d01ef8192849d7341b00
05:54:30 TRACE src/pool.c:2383: Submission reserved values: 66689 26 1 1
05:54:30 DEBUG src/pool.c:2446: Invalid share
05:54:31 TRACE src/pool.c:2311: Client submitted nonce=67010, result=2278527ba293d4b97b7f759c5bb6161791033a09c91efca3ebda3f5ae3fa0f00
05:54:31 TRACE src/pool.c:2383: Submission reserved values: 67010 26 1 1
05:54:31 DEBUG src/pool.c:2446: Invalid share
05:54:32 TRACE src/pool.c:2311: Client submitted nonce=67227, result=d70e7a0a124abcc3f1abf54664d975d92e988511978eae385f8397d2e0950600
05:54:32 TRACE src/pool.c:2383: Submission reserved values: 67227 26 1 1
05:54:32 DEBUG src/pool.c:2446: Invalid share
05:54:32 INFO  src/pool.c:2572: Removing client. Too many bad shares.

I have attempted to connect to the dev pool and recieve the same error however. So perhaps an issue with xmr-node-proxy?

jtgrassie commented 4 years ago

Well obviously you can't submit non monero rx hashes to a monero mining pool. Fix your miner/proxy config.

Emperornero commented 4 years ago

Thanks for the fast response.

I'm using XMRRig-5.5.1 I suspect it's an issue with the xmr-node-proxy, but I don't see any settings out of place in my miner.

Here is what it looks like with no miners connected and mining. Issue

As soon as I connect with a miner this happens:

Issue 2

Perhaps an incompatibility with xmr-node-proxy?

jtgrassie commented 4 years ago

Clearly a) you have Loki specified in your config b) this is not a pool issue its with your miner/proxy config and c) this is not a support channel to help you setup your proxy or miner.

Perhaps an incompatibility with xmr-node-proxy?

Nope. Tested and working fine with both xmr-node-proxy and the far superior xmrig-proxy.

Emperornero commented 4 years ago

I managed to get it up and running with xmrig-proxy. I was having issues with xmrig-proxy before, so I had been using xmr-node-proxy for a while.

Either way, thanks for the help.