Author

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 425. (Read 703583 times)

sr. member
Activity: 700
Merit: 294
I've noticed what appears to be a conflict between Awesome Miner and Teamviewer on Windows 10.

Whenever I remote in with Team Viewer, Awesome Miner stops mining and restarts itself.

Whenever I manually restart a mining process within Awesome Miner, Teamviewer times out for 30 seconds, before reconnecting.

Sometimes when my remote rig is mining, Teamviewer won't even connect at all.

How can I change the ports either Awesome Miner or Teamviewer use, to prevent this from happening?

Alternatively, does anyone have a guide on how to set up a remote rig within Awesome Miner? I cannot seem to get it working on my local network.

Others have noticed the same: https://www.reddit.com/r/gpumining/comments/7vchaj/awesome_miner_teamviewer_conflict/

Why not use good old RDP?  Are you trying to access your rig from outside your network?  Is this why you are using Teamviewer?
sr. member
Activity: 700
Merit: 294
Not sure if this makes sense so please advise if I'm not pointing to the right direction.

As I increase the number of rigs/GPUs, I see more rigs found in 'dead' state where I cannot issue soft 'reboot' command through AM. And this is not due to aggressive OC nor GPUs overheating. I understand that it's not AM's fault either. Seems to happen to one rig every couple of days when I wake up.

So in order to overcome this, I'm looking at watchdog (or similar) to hard reboot the machines. Eventually, I'll probably end up getting a watchdog built by the same person who built the SMOS but for now, since all rigs are all over my house, wired connection is not an option.

I bought couple of cheapo smart plugs that claim they are IFTTT compatible and I managed to get them to turn on and off using the webhook applet. I also managed to get them triggered via AM when the rigs are detected as 'offline'. It actually works well the first time it detects offline it but if it goes down again before I get a chance to clear the notification messages within AM, it no longer gets triggered.

This is what I did:

Trigger - (time interval : 5 mins) AND (detect offline, 120 secs)
Actions - (send webhook to turn switch off), (wait 30 secs), (send webhook to switch on), (notification)

For the last notification, I did turn off 'Notify once until acknowledged).

Am I doing this right?




Check out my solution...  Cheesy

Puwaha's Poor Man's Networked PDU: Using Smart Plugs and Awesome Miner

https://bitcointalksearch.org/topic/how-to-puwahas-poor-mans-networked-pdu-using-smart-plugs-and-awesome-miner-2866608
member
Activity: 140
Merit: 18
I've noticed what appears to be a conflict between Awesome Miner and Teamviewer on Windows 10.

Whenever I remote in with Team Viewer, Awesome Miner stops mining and restarts itself.

Whenever I manually restart a mining process within Awesome Miner, Teamviewer times out for 30 seconds, before reconnecting.

Sometimes when my remote rig is mining, Teamviewer won't even connect at all.

How can I change the ports either Awesome Miner or Teamviewer use, to prevent this from happening?

Alternatively, does anyone have a guide on how to set up a remote rig within Awesome Miner? I cannot seem to get it working on my local network.

Others have noticed the same: https://www.reddit.com/r/gpumining/comments/7vchaj/awesome_miner_teamviewer_conflict/

its not a TV and AM conflict, it's that TV is using the GPU.  I noticed a 75-100 sol/s decrease on the card that is running the monitor.  If I used the MB video that doesn't have a GPU, TV runs just fine and there is no sol/s decrease.  Actually in my case, I can work with TV and AM, but it will depend on your GPU.

But I would fully expect that crashes can occur depending on lots of variables, if the main windows display that TV is replicating is also running on the GPU.
newbie
Activity: 3
Merit: 0
I've noticed what appears to be a conflict between Awesome Miner and Teamviewer on Windows 10.

Whenever I remote in with Team Viewer, Awesome Miner stops mining and restarts itself.

Whenever I manually restart a mining process within Awesome Miner, Teamviewer times out for 30 seconds, before reconnecting.

Sometimes when my remote rig is mining, Teamviewer won't even connect at all.

How can I change the ports either Awesome Miner or Teamviewer use, to prevent this from happening?

Alternatively, does anyone have a guide on how to set up a remote rig within Awesome Miner? I cannot seem to get it working on my local network.

Others have noticed the same: https://www.reddit.com/r/gpumining/comments/7vchaj/awesome_miner_teamviewer_conflict/
jr. member
Activity: 99
Merit: 8
Any one else having problems with mining pool hub? It shuts down as soon as I start Awesome miner.

Starting Diagnostics. Awesome Miner version: 4.4.1
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: ZecEwbfMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\jcndj\AppData\Local\AwesomeMiner\Zec.miner.0.3.4b_1\0.3.4b\miner.exe
C:\Users\jcndj\AppData\Local\AwesomeMiner\Zec.miner.0.3.4b_1\0.3.4b\miner.exe  --server us-east.us-east.equihash-hub.miningpoolhub.com --port 20594 --user Arackis.Arackis --pass x --api 0.0.0.0:4028   (WindowMode: ConsoleFormat, EngineType: ZecEwbfMiner, IsProfitMiner: True)
Configuration:

>
+-------------------------------------------------+
> |         EWBF's Zcash CUDA miner. 0.3.4b         |
> +-------------------------------------------------+
> INFO: Current pool: us-east.us-east.equihash-hub.miningpoolhub.com:20594
> INFO: Selected pools: 1
> INFO: Solver: Auto.
> INFO: Devices: All.
> INFO: Temperature limit: 90
> INFO: Api: Listen on 0.0.0.0:4028
> ---------------------------------------------------
> ERROR: Cannot resolve hostname
Failed to start miner process: Process has exited, so the requested information is not available.
Failed to start miner in Diagnostics mode
Diagnostics completed


look at the address you have set for MPH

us-east.us-east.equihash-hub.miningpoolhub.com:20594


guessing that us-east shouldn't be in there twice
newbie
Activity: 3
Merit: 0
Any one else having problems with mining pool hub? It shuts down as soon as I start Awesome miner.

Starting Diagnostics. Awesome Miner version: 4.4.1
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: ZecEwbfMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\jcndj\AppData\Local\AwesomeMiner\Zec.miner.0.3.4b_1\0.3.4b\miner.exe
C:\Users\jcndj\AppData\Local\AwesomeMiner\Zec.miner.0.3.4b_1\0.3.4b\miner.exe  --server us-east.us-east.equihash-hub.miningpoolhub.com --port 20594 --user Arackis.Arackis --pass x --api 0.0.0.0:4028   (WindowMode: ConsoleFormat, EngineType: ZecEwbfMiner, IsProfitMiner: True)
Configuration:

>
+-------------------------------------------------+
> |         EWBF's Zcash CUDA miner. 0.3.4b         |
> +-------------------------------------------------+
> INFO: Current pool: us-east.us-east.equihash-hub.miningpoolhub.com:20594
> INFO: Selected pools: 1
> INFO: Solver: Auto.
> INFO: Devices: All.
> INFO: Temperature limit: 90
> INFO: Api: Listen on 0.0.0.0:4028
> ---------------------------------------------------
> ERROR: Cannot resolve hostname
Failed to start miner process: Process has exited, so the requested information is not available.
Failed to start miner in Diagnostics mode
Diagnostics completed
newbie
Activity: 3
Merit: 0
Quick question guys, trying to troubleshoot an issue with hashrefinery its reporting a ridiculous profit in awesome miner for nist5 (£1300 a month) and its throwing the profit switching for my 6GPU rig I wish it was right!

Any ideas where I can start to troubleshoot this? all other Algos look as expected. I have benchmarked and also tried saving the hash rate but still its obsessed with this algorithm.

Many thanks

I disabled HashRefinery completely. That pool is a scam. You will see coins waiting for days to go to exchange and even large amounts vanish from your account.  
I think there should be some replacements and new more reliable pools to be added. Today HashRefinery reported even $400/day/rig and that is totally unacceptable and made 10000 AM users to switch to that pool and lost their money.



Yeah they killed me too last night. Said I was making like $36 a day on a Gtx 1070 ti.
newbie
Activity: 140
Merit: 0
With this very low price of 7k for BTC , ROI for GPU went to one year from a few months and Antminer S9 will get your money back in 2 years. So you will wait years to even recover the money you spent on hardware and at that time it will cost more electricity than the money produced.

I guess people will start selling devices. Already almost everyone had a miner that you could hear by the noisy fan, and that was a clear sigh that the bubble will pop, when everybody makes the bubble larger.
newbie
Activity: 140
Merit: 0
Quick question guys, trying to troubleshoot an issue with hashrefinery its reporting a ridiculous profit in awesome miner for nist5 (£1300 a month) and its throwing the profit switching for my 6GPU rig I wish it was right!

Any ideas where I can start to troubleshoot this? all other Algos look as expected. I have benchmarked and also tried saving the hash rate but still its obsessed with this algorithm.

Many thanks

I disabled HashRefinery completely. That pool is a scam. You will see coins waiting for days to go to exchange and even large amounts vanish from your account.  
I think there should be some replacements and new more reliable pools to be added. Today HashRefinery reported even $400/day/rig and that is totally unacceptable and made 10000 AM users to switch to that pool and lost their money.
newbie
Activity: 9
Merit: 0
Quick question guys, trying to troubleshoot an issue with hashrefinery its reporting a ridiculous profit in awesome miner for nist5 (£1300 a month) and its throwing the profit switching for my 6GPU rig I wish it was right!

Any ideas where I can start to troubleshoot this? all other Algos look as expected. I have benchmarked and also tried saving the hash rate but still its obsessed with this algorithm.

Many thanks
newbie
Activity: 140
Merit: 0
Awesome Miner version 4.4.1

- Cloud Services: Multiple Telegram clients can sign in and get notifications from Awesome Miner
- Cloud Services: Heartbeat feature includes support for Telegram notifications
- Display of Accepted and Rejected shares per GPU for Claymore Ethereum miner
- Configuration of automatic restart of crashed miner can be disabled by setting 0 restart attempts in the Options dialog, Advanced section
- Trigger for Check Statistics adds support for evaluating Rejected shares in addition to Accepted shares.
- Trigger for Computer Idle adds support for specifying time in seconds instead of minutes
- Notification list support keyboard shortcut Ctrl+A and Ctrl+C to copy all notifications to clipboard
- Awesome Miner API for miners includes hashrate value specified as a number
- Profit switcher will show error message if no pool can fulfill the requirements of the selected combination of algorithms and mining software
- Excavator 1.4 supported as External Miner
- Alexis Ccminer version updated
- Corrected hashrate summary when moving miners between groups
- Minor corrections

Thanks for the Excavator support!

I want to configure excavator and I added external miner excavator (latest) but I am undable to benchmark or start mining with excavator. Do you have any tutorial about how to configure the latest version of excavator ?
Why can't we use excavator with "managed profit miner" by adding excavator to "user defined mining software" and select compatibility "excavator latest" ?



Trying to figure out. No luck as yet...

Anyone managed to configure it ?
member
Activity: 531
Merit: 29
Awesome Miner version 4.4.1

- Cloud Services: Multiple Telegram clients can sign in and get notifications from Awesome Miner
- Cloud Services: Heartbeat feature includes support for Telegram notifications
- Display of Accepted and Rejected shares per GPU for Claymore Ethereum miner
- Configuration of automatic restart of crashed miner can be disabled by setting 0 restart attempts in the Options dialog, Advanced section
- Trigger for Check Statistics adds support for evaluating Rejected shares in addition to Accepted shares.
- Trigger for Computer Idle adds support for specifying time in seconds instead of minutes
- Notification list support keyboard shortcut Ctrl+A and Ctrl+C to copy all notifications to clipboard
- Awesome Miner API for miners includes hashrate value specified as a number
- Profit switcher will show error message if no pool can fulfill the requirements of the selected combination of algorithms and mining software
- Excavator 1.4 supported as External Miner
- Alexis Ccminer version updated
- Corrected hashrate summary when moving miners between groups
- Minor corrections

Thanks for the Excavator support!

I want to configure excavator and I added external miner excavator (latest) but I am undable to benchmark or start mining with excavator. Do you have any tutorial about how to configure the latest version of excavator ?
Why can't we use excavator with "managed profit miner" by adding excavator to "user defined mining software" and select compatibility "excavator latest" ?



Trying to figure out. No luck as yet...
newbie
Activity: 7
Merit: 0
I let auto profit mining for a while and I have found out all my zpool mining, which was pointed to a BTC wallet, was considered BCH. I even had the "Select BTC payout when using zpool..." option enabled.  Now I have $21 in a non withdrawable address (BCH pointed to a BTC address).   I have changed to another BTC address, and manually added a "-p c=BTC" at the command line for all zpool rows at "Online Services".

Not sure if this is a zpool error, or AM.
This is a zpool error. I had the same issue and I reached out to zpool support and took care of it for me right away. They are able to convert it from BCH to BTC.
newbie
Activity: 31
Merit: 0
I let auto profit mining for a while and I have found out all my zpool mining, which was pointed to a BTC wallet, was considered BCH. I even had the "Select BTC payout when using zpool..." option enabled.  Now I have $21 in a non withdrawable address (BCH pointed to a BTC address).   I have changed to another BTC address, and manually added a "-p c=BTC" at the command line for all zpool rows at "Online Services".

Not sure if this is a zpool error, or AM.
newbie
Activity: 119
Merit: 0
Not sure if this makes sense so please advise if I'm not pointing to the right direction.

As I increase the number of rigs/GPUs, I see more rigs found in 'dead' state where I cannot issue soft 'reboot' command through AM. And this is not due to aggressive OC nor GPUs overheating. I understand that it's not AM's fault either. Seems to happen to one rig every couple of days when I wake up.

So in order to overcome this, I'm looking at watchdog (or similar) to hard reboot the machines. Eventually, I'll probably end up getting a watchdog built by the same person who built the SMOS but for now, since all rigs are all over my house, wired connection is not an option.

I bought couple of cheapo smart plugs that claim they are IFTTT compatible and I managed to get them to turn on and off using the webhook applet. I also managed to get them triggered via AM when the rigs are detected as 'offline'. It actually works well the first time it detects offline it but if it goes down again before I get a chance to clear the notification messages within AM, it no longer gets triggered.

This is what I did:

Trigger - (time interval : 5 mins) AND (detect offline, 120 secs)
Actions - (send webhook to turn switch off), (wait 30 secs), (send webhook to switch on), (notification)

For the last notification, I did turn off 'Notify once until acknowledged).

Am I doing this right?


member
Activity: 140
Merit: 18
Not sure if people saw this yesterday on ahashpool or not

Code:
Announcement: [2018-02-04 22:49 UTC] Please do not use 24 hour actuals in your profit switching script. When chain split happens, the pool will disable coins, or even disable the entire algo, and if you are using the past 24 hours actuals algo profit ranking to pick algo, you will be wasting your hash power. Bul wark just had a chain split, we disabled Bulwark but there are still 700+ miners on Nist5 after an hour, this tells us at least 700 rigs are doing it wrong. You should only use current estimates in determining your algo. And if you don't want it to switch too often, just increase the interval time. Do NOT use 24 hours actuals.

So which is the preferred way to setup AM?
hero member
Activity: 1151
Merit: 528
Patrike the HTTP API coin setting is wonderful, thank you very much. I am making extensive use of it.

As another line item, can you please add the ability to create new coins via the API as well? The plugins I'm writing/hope to be distributing sorely need it.

Something along the lines of:
POST http://mypc:17790/api/coins/NEW?longname=COIN_NAME&shortname=CNNME&algo=skein

Thank you!
Request to the top!
newbie
Activity: 2
Merit: 0
When can we expect to see support for Bminer? It's easily the fastest equihash miner available right now for CUDA mining.

https://bitcointalksearch.org/topic/annbminer-a-fast-equihashethashcuckaroo29z-miner-for-amdnvidia-gpus-1649-2519271

Has anyone else gotten this working as external software? I've added it by following all of the steps in the documentation but when AwesomeMiner tries to run it the cmd prompt opens then closes right away. Bminer works correctly on this system if I run it on it's own.
newbie
Activity: 140
Merit: 0
Awesome Miner version 4.4.1

- Cloud Services: Multiple Telegram clients can sign in and get notifications from Awesome Miner
- Cloud Services: Heartbeat feature includes support for Telegram notifications
- Display of Accepted and Rejected shares per GPU for Claymore Ethereum miner
- Configuration of automatic restart of crashed miner can be disabled by setting 0 restart attempts in the Options dialog, Advanced section
- Trigger for Check Statistics adds support for evaluating Rejected shares in addition to Accepted shares.
- Trigger for Computer Idle adds support for specifying time in seconds instead of minutes
- Notification list support keyboard shortcut Ctrl+A and Ctrl+C to copy all notifications to clipboard
- Awesome Miner API for miners includes hashrate value specified as a number
- Profit switcher will show error message if no pool can fulfill the requirements of the selected combination of algorithms and mining software
- Excavator 1.4 supported as External Miner
- Alexis Ccminer version updated
- Corrected hashrate summary when moving miners between groups
- Minor corrections

Thanks for the Excavator support!

I want to configure excavator and I added external miner excavator (latest) but I am undable to benchmark or start mining with excavator. Do you have any tutorial about how to configure the latest version of excavator ?
Why can't we use excavator with "managed profit miner" by adding excavator to "user defined mining software" and select compatibility "excavator latest" ?

member
Activity: 531
Merit: 29
Awesome Miner version 4.4.1

- Cloud Services: Multiple Telegram clients can sign in and get notifications from Awesome Miner
- Cloud Services: Heartbeat feature includes support for Telegram notifications
- Display of Accepted and Rejected shares per GPU for Claymore Ethereum miner
- Configuration of automatic restart of crashed miner can be disabled by setting 0 restart attempts in the Options dialog, Advanced section
- Trigger for Check Statistics adds support for evaluating Rejected shares in addition to Accepted shares.
- Trigger for Computer Idle adds support for specifying time in seconds instead of minutes
- Notification list support keyboard shortcut Ctrl+A and Ctrl+C to copy all notifications to clipboard
- Awesome Miner API for miners includes hashrate value specified as a number
- Profit switcher will show error message if no pool can fulfill the requirements of the selected combination of algorithms and mining software
- Excavator 1.4 supported as External Miner
- Alexis Ccminer version updated
- Corrected hashrate summary when moving miners between groups
- Minor corrections

Thanks for the Excavator support!
Jump to: