Quote
MPH usually takes 5-15 minutes to show worker and hashrate
You can use this to check your miner command :
You can use this to check your miner command :
Code:
ps ax | grep miner
This was the command I was looking for.
Unfortunately it is showing me that the miner never changes ports to match what the switcher says I am now mining.
It appears to be stuck on port 20570, ZCASH:
Code:
m1@m1-desktop:~$ ps ax | grep miner
385 ? Ss 0:00 SCREEN -dmSL miner /home/m1/zec/zm/latest/zm_miner --server us-east.equihash-hub.miningpoolhub.com --user xxxxxxx.xxxxxxx --pass x --port 20570 --time
386 pts/27 Ssl+ 53:21 /home/m1/zec/zm/latest/zm_miner --server us-east.equihash-hub.miningpoolhub.com --user xxxxxxx.xxxxxxx --pass x --port 20570 --time
11073 pts/2 S+ 0:00 grep --color=auto miner
32670 pts/26 Sl+ 34608:17 /home/m1/cpuOPT/cpuminer -a cryptonight -o stratum+tcp://xmr-us-east1.nanopool.org:14444 -u 47xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.xxxxxxxxxx -p x -t 31
m1@m1-desktop:~$
385 ? Ss 0:00 SCREEN -dmSL miner /home/m1/zec/zm/latest/zm_miner --server us-east.equihash-hub.miningpoolhub.com --user xxxxxxx.xxxxxxx --pass x --port 20570 --time
386 pts/27 Ssl+ 53:21 /home/m1/zec/zm/latest/zm_miner --server us-east.equihash-hub.miningpoolhub.com --user xxxxxxx.xxxxxxx --pass x --port 20570 --time
11073 pts/2 S+ 0:00 grep --color=auto miner
32670 pts/26 Sl+ 34608:17 /home/m1/cpuOPT/cpuminer -a cryptonight -o stratum+tcp://xmr-us-east1.nanopool.org:14444 -u 47xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.xxxxxxxxxx -p x -t 31
m1@m1-desktop:~$
Could the fact I am CPU mining XMR as well be causing some issues?
I also have other rigs that are not yet using the WTM switcher and are still using the MPH_Equihash switcher until my testing is complete.
Could their setup on MPH be forcing this rig to stay on Equihash switching some how? Seems very unlikely.
And this is the print from the miner but not a single coin is showing in the balance other than ZCASH:
Code:
LAST 10 AUTO SWITCHES:
Sun Feb 11 13:56:10 MST 2018 - Mining switched from ZCL to ZEN
Sun Feb 11 14:21:06 MST 2018 - Mining switched from ZEN to ZEC
Sun Feb 11 15:01:36 MST 2018 - Mining switched from ZEC to FTC
Sun Feb 11 15:07:49 MST 2018 - Mining switched from FTC to ZEC
Sun Feb 11 15:38:59 MST 2018 - Mining switched from ZEC to ZEN
Sun Feb 11 16:03:55 MST 2018 - Mining switched from ZEN to ZCL
Sun Feb 11 16:41:19 MST 2018 - Mining switched from ZCL to ZEC
Sun Feb 11 16:54:16 MST 2018 - Mining switched from ZEC to FTC
Sun Feb 11 17:03:37 MST 2018 - Mining switched from FTC to ZEC
Sun Feb 11 17:22:19 MST 2018 - Mining switched from ZEC to ZCL
Sun Feb 11 13:56:10 MST 2018 - Mining switched from ZCL to ZEN
Sun Feb 11 14:21:06 MST 2018 - Mining switched from ZEN to ZEC
Sun Feb 11 15:01:36 MST 2018 - Mining switched from ZEC to FTC
Sun Feb 11 15:07:49 MST 2018 - Mining switched from FTC to ZEC
Sun Feb 11 15:38:59 MST 2018 - Mining switched from ZEC to ZEN
Sun Feb 11 16:03:55 MST 2018 - Mining switched from ZEN to ZCL
Sun Feb 11 16:41:19 MST 2018 - Mining switched from ZCL to ZEC
Sun Feb 11 16:54:16 MST 2018 - Mining switched from ZEC to FTC
Sun Feb 11 17:03:37 MST 2018 - Mining switched from FTC to ZEC
Sun Feb 11 17:22:19 MST 2018 - Mining switched from ZEC to ZCL
Any comments on this? At this point I do not believe the switcher is actually switching, just "reporting" correctly some stuff but stuck on one coin.
I see the COIN= getting updated in 1bash when a change occurs. Is some line of code in WTM suppose to restart 1bash when a switch is expected?
Wouldn't you expect to see some balances of random coins on MPH if you were mining them?
Thanks.
I doubt that CPU mining has any impact on it as they are just two different processes running independently.
Ok, I'm just checking the basic things first. I assume you are trying to use 'SALFTER_MPH_PROFIT_SWITCHING' switcher, its logging the switches but the actual switching isn't happening?
So, you see no balance increases at all with other coins? Was it mining a single coin fine??
In the above switches, all the coins except FTC uses equihash, and MPH_SWITCH works in a way that it doesn't switch ports for every single coin, also am not sure that COIN='XXX' value doesn't change in 1bash as MPH switch doesn't bother about the COIN variable at all.
This is my understanding from my experience of using it in past.
I will try to run it with latest version, tell you if its any different from past and update you.
Actually I am trying Papampi's WTM switcher now. That's what my post above is about.
I had SALFTER's version running fine but was seeing no increase in coins vs. straight mining so I decided to try WTM instead.
The list above shows what the nvOC wtm-log shows as it switches.
So, many coin types have been "switched" to, but zero coins of those types have ever shown up in the balance sheet on MPH except for the one that appears locked.
Mining MPH_Equihash and MPH_Ethash both switched fine and mining single coins works fine.
Also, the reason I mention the COIN type changing in 1bash is I have peeked in 1bash after several supposedly coin switch (in the list) and COIN=xxxx has changed to the type now supposedly being mined.
Maybe my eyes are playing tricks on me.
To run WTM switcher the COIN= entry in 1bash does not need any special coin type, correct?
Thanks for looking at my question.