search

fireice-uk / xmr-stak

Free Monero RandomX Miner and unified CryptoNight miner
GNU General Public License v3.0
4.05k stars 1.8k forks source link

Miner can't reconnect to the pool #1756

Open givo111 opened 5 years ago

givo111 commented 5 years ago

Using 'Version: xmr-stak/2.4.7/c5f0505/master/lin/nvidia-amd-cpu/0' on Linux (HiveOS) and mining BitTube with AMD GPUs (RX470, RX580).

For some reason, miner looses connection with the pool and simply can't reconnect back again. From the log: [2018-07-30 19:17:25] : Result accepted by the pool. [2018-07-30 19:18:15] : Fast-connecting to ca.bittube.miner.rocks:7777 pool ... [2018-07-30 19:18:32] : SOCKET ERROR - [ca.bittube.miner.rocks:7777] CONNECT error: GetAddrInfo: Temporary failure in name resolution [2018-07-30 19:18:32] : Fast-connecting to sg.bittube.miner.rocks:7777 pool ... [2018-07-30 19:18:33] : SOCKET ERROR - [bittube.miner.rocks:7777] CALL error: Timeout while waiting for a reply [2018-07-30 19:18:33] : Pool sg.bittube.miner.rocks:7777 connected. Logging in... [2018-07-30 19:18:43] : Fast-connecting to bittube.miner.rocks:7777 pool ... [2018-07-30 19:18:43] : SOCKET ERROR - [sg.bittube.miner.rocks:7777] CALL error: Timeout while waiting for a reply [2018-07-30 19:18:44] : Pool bittube.miner.rocks:7777 connected. Logging in... [2018-07-30 19:19:32] : Result rejected by the pool. [2018-07-30 19:22:08] : Result rejected by the pool.

Miner never recovers from this error on its own. After restarting miner, all is fine.

psychocrypt commented 5 years ago

lease fill out the issue template you provided not enough data to analyse the issue. Please also add the pools.txt file

givo111 commented 5 years ago

Please provide as much as possible information to reproduce the issue.

Basic information

Compile issues

Issue with the execution

AMD OpenCl issue

  run `clinfo` and add the output here

= Attached clinfo.txt clinfo.txt

Stability issue

Pools.txt pools.txt

Just one more note - miner does recover sometimes, but when it starts showing message "Result rejected by the pool." - then it never recovers and miner restart is required.

psychocrypt commented 5 years ago

where do you downloaded the miner? The pools.txt not looks like a config from us. Do you use an forked xmr-stak?

Schmoozer0069 commented 5 years ago

I have similar issues when my VPN is acting up. If you are running a VPN try changing it to a different host. If you are running your own VPN try doing a reset/reboot.

givo111 commented 5 years ago

@psychocrypt - It comes pre-compiled with HiveOS (https://hiveos.farm/changelog/). In settings I selected "fireice-uk" fork.

@Schmoozer0069 - not using VPN. From what I have learned so far - triger to this behavior can be any networking problem (i.e. ISP changes IP address, VPN problems, intermittent DNS failure, …). Question is, once network has stabilized why doesn't miner reconnect?!?

psychocrypt commented 5 years ago

how many config files do the miner in hiveos is creating?

givo111 commented 5 years ago

amd.txt cpu.txt nvidia.txt config.txt pools.txt

config and pools are the same. I'm not using cpu.txt nor nvidia.txt. amd.txt attached. amd.txt

givo111 commented 5 years ago

This is from the log where miner successfully reconnects after a network failure: [2018-07-30 22:06:00] : Result accepted by the pool. [2018-07-30 22:06:15] : Fast-connecting to ca.bittube.miner.rocks:7777 pool ... [2018-07-30 22:06:15] : Fast-connecting to sg.bittube.miner.rocks:7777 pool ... [2018-07-30 22:06:15] : SOCKET ERROR - [bittube.miner.rocks:7777] CALL error: Timeout while waiting for a reply [2018-07-30 22:06:15] : Pool ca.bittube.miner.rocks:7777 connected. Logging in... [2018-07-30 22:06:16] : Pool sg.bittube.miner.rocks:7777 connected. Logging in... [2018-07-30 22:06:16] : Difficulty changed. Now: 238093. [2018-07-30 22:06:16] : Pool switched. [2018-07-30 22:06:16] : New block detected. [2018-07-30 22:06:22] : Result accepted by the pool.

But, once we receive "Result rejected by the pool." - then it never reconnects... Just prints out this message over and over again.

givo111 commented 5 years ago

Again all my rigs went crazy some 8 hours ago... Changed pool and algo (now running pure CN Heavy on NiceHash). While changing I've noticed that miner recovers on their own from "Result rejected...".

Maybe some fine tuning on retry_timeout and call_timeout would do the trick. Is it possible that before attempting new connection to wait for all previous connections to finish completely (FIN_WAIT)?

psychocrypt commented 5 years ago

I will have a look on in soon