Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"No active pools, stop mining" and other strange things #118

Closed
ght3d opened this issue Sep 19, 2017 · 13 comments
Closed

"No active pools, stop mining" and other strange things #118

ght3d opened this issue Sep 19, 2017 · 13 comments

Comments

@ght3d
Copy link

@ght3d ght3d commented Sep 19, 2017

Hey there, dear developer.

A big fan of your miner here, pretty much the fastest and simplest to set up i've found for monero.

The issue is that 1 day ago, suddenly xmrig started displaying the "No active pools, stop mining", the overall hashrate of the farm divided by 3 and slowed down, a lot of jobs were being accepted constantly, but only 2, sometimes 3 found shares where accepted by the pool. Then share accepting messages just stop appearing.
Also "Connection reset by peer" started appearing, but nothing in my network configuration changed since i started mining. For 20 days straight, not a single invalid share, no errors, nothing, and now this.

I also tried to reroute all farms to and Xmrig-proxy installed on one of the machines in the same network. Errors are pretty much the same, no matter what pool is use or what xmrig flags i set, you can see them in the screenshots i provided.

The other thing i did, to make sure it's not a network problem, is to install a 4g connection to the computer instead of using internet provided by the LAN. Same story on a 4g connection. First i thought the pool banned me for making a bunch of connections from 30 computers, but it's the same errors on all pools.

Tried to solve it by myself and last thing i wanted is to bother the developer with my noob problems.

Thank you for this wonderful miner!

screenshot_1
screenshot_2
screenshot_3

@ght3d
Copy link
Author

@ght3d ght3d commented Sep 20, 2017

screenshot_4
Mined all night and had some other errors. The shares are being accepted but at an incredibly slow rate (only 125 for a whole night, which wasn't the case before).

@ght3d
Copy link
Author

@ght3d ght3d commented Sep 20, 2017

When trying to mine aeon it gives me this. A lot of people had same problem on forum with different mining software, but no explanation or solution was found:

screenshot_1

@LeozMaralz
Copy link

@LeozMaralz LeozMaralz commented Sep 20, 2017

When trying to mine aeon it gives me this. A lot of people had same problem on forum with different mining software, but no explanation or solution was found

@ght3d Remove stratum+tcp:// from the pool address and all should be fine.

@ght3d
Copy link
Author

@ght3d ght3d commented Sep 20, 2017

@LeozMaralz same story with or without stratum+tcp:// . But thanks for suggestions

@calvintam236
Copy link

@calvintam236 calvintam236 commented Sep 21, 2017

You are getting timed out. Looks like the pool is too far from your location (It's 500-1000ms in the screenshot). Try to lower the response time by using different region server/pool. Normally, I think it should less than 250ms.

@ght3d
Copy link
Author

@ght3d ght3d commented Sep 21, 2017

@calvintam236 Didn't have the error for a month and ping couldn't suddenly change, connection settings stayed the same, also tried on a faster 4g connection and errors reproduced again. The errors appear on any pool, from any country, even if the ping is less than 100 ms.

@calvintam236
Copy link

@calvintam236 calvintam236 commented Sep 21, 2017

@ght3d Can you list out your OS, hardware spec, and xmrig version? Did you install/update any software on the rig recently?

@ght3d
Copy link
Author

@ght3d ght3d commented Sep 21, 2017

@calvintam236 Double Xeon E5-2650 renderblades with 40mb L3 cache with Windows Server 2012 and a couple of single Xeon X5690 workstations with Windows 7. Latest XmRig 2.3.1 and no hardware/software changes in the last week whatsoever. Only one workstation got a new graphics card which i used successfully for mining for a week or so, but it's irrelevant as it doesn't affect other machines. All machines have the same issue, no matter their specs. In total there are 30 machines, all mining to the same wallet simultaneously. Tried Xmrig proxy and there are still timeout errors, machines keep connecting/disconnecting, share rate became pretty pathetic, almost a quarter of what it was before.

@eXellenz
Copy link

@eXellenz eXellenz commented Sep 29, 2017

confirm. i have same problem.
thx 4 nice miner & nh support by gpu miner.
cpu_i7

@ght3d
Copy link
Author

@ght3d ght3d commented Sep 29, 2017

Well, after researching the problem for a week, and testing miners and network configurations, i found out that the network config was actually changed by the system admin. In order to protect the network from ddos attacks, the admin turned off any kind of DNS requests and the ICMP protocol which allows you to ping a machine. The miners couldn't ping servers because of this, so i made a http and socks5 proxy on a specific machine which reroutes traffic around the firewall. All the connection errors from the first screenshot dissapeared. I used XmrigProxy on said machine and sent all miners to this machine's address. Works great!

For the other half of my farm i had to use another old miner , optimized for old machines which do not have the AES-NI instructions set and xmrig yields 10 times less speed on them then the old miner. Hopefully that miner had the option to set a proxy in the .bat file directly like "miner.exe -x http://proxy-address -o stratum+tcp://pool-address -u user -x password. These old miners, which do not use xmrig and xmrigproxy, mine directly to the pool through http proxy , but on the same wallet.

Too bad that Xmrig doesn't support direct http proxies yet.

@eXellenz - Work is accepted correctly, there are no connection issues or errors, you can easily ignore the "no active pools" error in your case.

@ght3d ght3d closed this as completed Sep 29, 2017
@joaopaulo164
Copy link

@joaopaulo164 joaopaulo164 commented Apr 14, 2019

which old miner did you use? @ght3d

@Spudz76
Copy link
Contributor

@Spudz76 Spudz76 commented Apr 15, 2019

Also high diff and low hashrate, some pools will hangup on you for no results in 90s or whatever.
You should be running a vardiff proxy to subdivide the enormous difficulty for your slow miners.

@jacksonkr
Copy link

@jacksonkr jacksonkr commented Jul 15, 2020

I noticed that one of my miners was not reporting and after looking into it I saw "No active pools, stop mining" in the terminal. While investigating what was going on the miner had reconnected itself and showed up as an active miner again on my supportxmr.com dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants