Quote from: PhoenixMiner on April 10, 2019, 07:58:35 AM

Quote from: aminlv2 on April 09, 2019, 03:09:23 PM

well, i switch back to Claymore...

1% better than hours of devfee by phoenixminer!

i don't have old logs
here is the link that 15 minutes devfee before i stop and switch back to claymore

https://gofile.io/?c=aYe0tA

Thank you for the log! It definitely helped us to identify the issue. If you look carefully in the log you posted, you will see that there is no DevFee prefix when posting shares - that is because the miner is not mining devfee at all. What is happening then? After some testing, the source of the problem is clear: the example epools.txt file, which is included in the zip file with the miner. If there is an epools.txt file in the same folder as the miner, it always reads it and adds the pools from there to the pools that you have specified at the command line (or in bat file, config.txt, etc.). This normally isn't a problem but if your main pool fails and the miner is not able to connect to it in three attempts, it switches to the next pool, which happens to be the on in the epools.txt file.

   So here is how to fix the issue (do one of the following things):
   - Delete the epools.txt file that comes with the miner or rename it to something else - the miner won'r read it and if you main pool fails, it will try to connect to it fovever
   - Open the epools.txt file and change the wallet (and pool if necessary) to your own wallet.

Quote from: Pilgrim75 on April 09, 2019, 02:01:43 PM

I apologize for the excessive emotionality in the previous message. Unfortunately, I did not save the logs and have already switched to another algorithm. I can only share the observation, this problem arose only on farms with a production level above 100MH.

No problem, we would also be upset in similar situation. Still, we would never jeopardize our reputation with such stupid "trick". Most probably the problem was the same as above - using the default epools.txt file that comes with the miner. Just delete epools.txt file or change the wallet to your own and the issue will go away.

Quote from: Digital_Seytan on April 09, 2019, 09:29:25 PM

I have had it a few times that phoenixminer, every 15 minutes devfee comes to mining for the developer there is certainly a bug present at phoenixminer 4.2.c. 4 x per hour devfee is certainly too much. therefore, to be sure, until a new version comes out, I go to claymore miner.

There is no bug in PhoenixMiner 4.2, just see above.

I got tripped up by this in the past - luckily realized the problem way before getting to the point of suspicion. But still need to remember every release or new rig setup to comment out epools, since I always use config exclusively.

Might be worth rethinking this design... one possible solution would be two different 'pool' flags - maybe '--pool' behavior ignores epools, while '--addpool' follows the current behavior?