0
Under review

no active pools, stop mining

vospasss 7 years ago updated by Monero 7 years ago 24

xmr.coinfoundry.org:3032
xmrig

"no active pools, stop mining"

this comes out pretty frequently the past few days

googled it, probably some connection issues?It happens from different locations of workers.
Any ideas?

Under review

Hmm, the pool hashrate appears to be pretty stable overall and I cannot spot any obvious issues with any of the servers.

I'm having the same issues, used to point to the old poolmining server but once this started appearing I changed to the new coinfoundry address but it is still persisting.

What is the new address?

The one you mentioned in your original post, I used to be on the previous one.


I have noticed the var diff seems to have changed where I now only get diff <6900. Previously I used to be allocated much lower difficulties.

Which port are you connecting to and from which geographical region?

xmr.coinfoundry.org:3032
from EU- Cyprus

Yes, i agree with the difficulty increase.

xmr.coinfoundry.org:3032
from EU- Cyprus

yes Monero

I didn't get your question...

I mean which port and location for user "Monero".

You meant the User Monero.. now i got it :) oops

BTW Oliver, can you explain why the difficulty of the shares accepted changed from 1000 to 6000-7000 ?
I suppose this is better.
Anyway those are just some work pcs mining on low end cpu's, dont really care, but just curious.

+1

All ports of all pools use vardiff (variable-difficulty), which means there's a starting difficulty (7500 in case of port 3032) which gets assigned to all miners after connecting. The pool constantly monitors the rate of submitted shares per miner and if the rate is too high, the pool sends the miner a higher difficulty. If the rate is too low (too few shares per 15 seconds), the miner gets assigned a lower difficulty. This auto-tuning process repeats endlessly.

3032 from London, UK.

Hi Oliver, 


I recently start getting the "no active pools, stop mining" error too. I think this started sometime this week. I am connecting from the UK on port 3104.

My address is etnk2BpMrZGMJ2a8KkGZ8h8J6gW5JJrQpUo83bGXZ8eq2wCktdUzpmeBqSghELUBBmRtw7Urp2VXbZMmBiAwQMSbA4u14Vq6wW.


Is there something I need to change on my end? 

Guys, is this only happening on the SSL ports?

No SSL enabled for me. Config below:


 {
    "algo": "cryptonight",
    "av": 0,
    "background": false,
    "colors": true,
    "cpu-affinity": null,
    "donate-level": 0,
    "log-file": null,
    "max-cpu-usage": 40,
    "print-time": 60,
    "retries": 5,
    "retry-pause": 5,
    "safe": false,
    "syslog": false,
    "threads": null,
    "pools": [
      {
        "url": "etn.coinfoundry.org:3104",
        "user": "etnk2BpMrZGMJ2a8KkGZ8h8J6gW5JJrQpUo83bGXZ8eq2wCktdUzpmeBqSghELUBBmRtw7Urp2VXbZMmBiAwQMSbA4u14Vq6wW.etn-mnr01",
        "pass": "x",
        "keepalive": true,
        "nicehash": false
      }
    ]
  }

No, I'm not using utilising SSL port myself.

im only seeing it when cpu mining, not gpu mining

Still persisting and variable difficulty still not adjusting properly even after installing newest (2.4.5.) version of XmRig.


From the little bit of googling I've done it seems to be affecting only XmRig and be connected to DDOS protection.


Because the variable difficulty doesn't adjust and the miner 'cutting out' every other minute there isn't many solved calculations being produced.

If you could provide your wallet address I could perform a deeper inspection. I would like to figure out what could be causing this.

4B3soyYopCYeDHdFKdMih9jKr3GbGhTPsJ6hiUXoETMAhnS9Wjzdk7QG2epR6c3i9R5eBJh71yhGTHxD1rz4QM6HM3PhZ3w

49ukf8s4QQXEpB8em78S7WVrNc7mzPsx2VCb4wHjD3okKErLsbVgCgC1RR9kLX5DZhiKeaNYpUkGhDBBQVyMevyU9gppcvL


At least it seems to be a common issue, not only this pool is affected.