[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[Commie]

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating  nvlddmkm.sys pagefile error, no idea how to fix this so far

[patrike]

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating  nvlddmkm.sys pagefile error, no idea how to fix this so far

Is Awesome Miner directly connected to Remote Agent or is it cloud connected?

If a mining computer reboots, Remote Agent should automatically re-start the mining (as long as Auto-start is enabled on the Managed Miner), no matter if it's connected to Awesome Miner or not. Maybe you could send me the log file for Remote Agent and let me know the time of the issue?

[sxemini]

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating  nvlddmkm.sys pagefile error, no idea how to fix this so far

Reinstall driver is good point to start. What nvidia cards are in this rig? I have sometimes trouble with my OC on new dag epoch, but after the next dag epoch switch the rig runs fine with the same settings. Nvidia cards are so weird in my opinion.

[Firstblackhaw]

Awesome Miner have not displayed hashrate of SRB Miner new versions (0.83 and 0.84). Please update Awesome Miner software !

[patrike]

Version 9.0.7 (Development preview of 9.1)

 ASIC mining
  - Added support for Antminer D7
  - Added support for additional Goldshell ASIC miners. For Goldshell miners where the standard monitoring isn't available (example: Goldshell ST-Box), configure the External Miner mining software to: ASIC miner (Goldshell Web API).
  - Improved detection of dead head boards on Antminers
  - Beta: Remote Proxy can run on Raspberry Pi (ARM) for management of remote ASIC mining sites
 GPU mining
  - Managed Hosts can be configured to be excluded from global fan and power control
  - GPU overclocking on Windows will always use Administrator privileges
  - Updated memory clock range for Navi GPUs on Linux
 Features
  - Information column: Include Remote Host (IP address)
  - Mining history export will include Remote Host (IP address) and MAC address
 Improvements
  - Performance improvements, especially for large scale mining operations
 Mining software
  - CpuMiner-Opt 3.19.1
  - Gminer 2.73
  - Lolminer 1.36a
  - Nanominer 3.4.4
  - NbMiner 40.1
  - SrbMiner-Multi 0.8.4, including adjustment in Awesome Miner to display hashrate based on the updated SrbMiner-API
  - T-Rex Miner 0.24.7
  - TeamBlackMiner 1.27
  - WildRig 0.30.6
 Corrections
  - Correction for display of T-Rex miner HW errors
  - Correction to dual mining revenue calculations for GPU mining
  - Correction to setting Default Pools for specific Avalon ASIC firmware versions and improved Default Pools processing
  - Correction to selection of Worker Name in the filter menu

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates.

[patrike]

Awesome Miner have not displayed hashrate of SRB Miner new versions (0.83 and 0.84). Please update Awesome Miner software !

Please upgrade to Awesome Miner development version v9.0.7.

[Sensis82]

Can someone give me a little Setup Guide for MRR on Awesome Miner please ?

Kind regards

Dominik

[patrike]

Version 9.0.8 (Development preview of 9.1)

 GPU mining
  - Improved compatibility for setting GPU memory voltage for AMD on Linux
 Features
  - Mining history export will include current device count and the current number of failed hash boards
 Mining software
  - PhoenixMiner 5.9c
  - WildRig 0.30.6.1
  - XmRig 6.16.0
 Corrections
  - Correction to ASIC type detection

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates.

[cajunsands]

running the latest develpment version , running it for Raptoreum mining, when will it officlaly be added? (cant track the coin)

[patrike]

running the latest develpment version , running it for Raptoreum mining, when will it officlaly be added? (cant track the coin)

Thanks for your request. We will add it during the day.

[STSMiner]

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating  nvlddmkm.sys pagefile error, no idea how to fix this so far

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

[sxemini]

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating  nvlddmkm.sys pagefile error, no idea how to fix this so far

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

This happens if something is wrong with your Remote client installation or the windows of the remote client. And sometimes AM need a little bit to recognize a client after the reboot, but i think it is normal.

[cajunsands]

Anyone having issues with remote agent refusing to restart with windows reboot?

[STSMiner]

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating  nvlddmkm.sys pagefile error, no idea how to fix this so far

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

This happens if something is wrong with your Remote client installation or the windows of the remote client. And sometimes AM need a little bit to recognize a client after the reboot, but i think it is normal.

Did not have this issue before until version 9.0.X .... and nothing has changed here on the rigs other than drivers for the GPU's and the re-install of the client and main app in an attempt to fix the issue, but it still persists and can take up to 2 minutes to see the remote rigs on the same network / submask.

[Commie]

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

In my case Patrik helped me to find another active copy of AM on my other notebook, which was causing conflicts and delays. The situation improved after I disabled it. However, BSODs still happen regardless of OC settings, no idea what to do with that.

Also, I'm still having trouble configuring ETH+ZIL dual mining. I re-read sxemini's guide, studied pool instructions but currently my miner (T-rex) immediately connects to Ezil/Rustpool instead of Ethermine and drops connection by timeout. Screenshots are attached, what am I doing wrong?





PS Tried adding following line to extra parameters, same result:  -a ethash -o stratum+tcp://asia.ezil.me:5555 -u <ETH address> -p <ZIL address>@asia1.ethermine.org:4444 -w Rig2 --extra-dag-epoch 0

[patrike]

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating  nvlddmkm.sys pagefile error, no idea how to fix this so far

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

This happens if something is wrong with your Remote client installation or the windows of the remote client. And sometimes AM need a little bit to recognize a client after the reboot, but i think it is normal.

Did not have this issue before until version 9.0.X .... and nothing has changed here on the rigs other than drivers for the GPU's and the re-install of the client and main app in an attempt to fix the issue, but it still persists and can take up to 2 minutes to see the remote rigs on the same network / submask.

Can you please send me the Awesome Miner and Remote Agent log file and let me know the time of the issue? I will of course investigate to see what the issue might be. As Commie pointed out, his case was related to running two Awesome Miner instances connected to the same Remote Agent.

[patrike]

Anyone having issues with remote agent refusing to restart with windows reboot?

Remote Agent is set to automatically start with Windows, but you must still start it manually each time? Is this a default setup where Remote Agent runs under your local user account or have you modified any permissions or forced Admin-permissions for the Remote Agent executable (not recommended). Any security software running that could prevent applications for automatically starting?

[cajunsands]

for some reason i had set it to manually start as admin the shortcut, put it back to normal and checked the *run at startup* rebooted now it all seems ok ...odd

[patrike]

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

In my case Patrik helped me to find another active copy of AM on my other notebook, which was causing conflicts and delays. The situation improved after I disabled it. However, BSODs still happen regardless of OC settings, no idea what to do with that.

Also, I'm still having trouble configuring ETH+ZIL dual mining. I re-read sxemini's guide, studied pool instructions but currently my miner (T-rex) immediately connects to Ezil/Rustpool instead of Ethermine and drops connection by timeout. Screenshots are attached, what am I doing wrong?

PS Tried adding following line to extra parameters, same result:  -a ethash -o stratum+tcp://asia.ezil.me:5555 -u <ETH address> -p <ZIL address>@asia1.ethermine.org:4444 -w Rig2 --extra-dag-epoch 0

The ezil.me mining pool uses the following configuration concept (taken from https://ezil.me/start)
t-rex -a ethash -o stratum+tcp://asia.ezil.me:5555 -u ETH_WALLET.ZIL_WALLET -p x -w WORKER

From what I can see, there is no concept of specifying your own ETH-mining pool here.

1) The "Pool URL" field in Awesome Miner should be: stratum+tcp://asia.ezil.me:5555
2) The "Worker name" field in Awesome Miner should be on the following format, as it's corresponding to the full user name: ETH_WALLET.ZIL_WALLET
3) The "Password" and "Wallet address" fields in Awesome Miner should be left blank.

In case you want to use the "WORKER" parameters as well (optional), you may have to manually add "-w WORKER" in the additional command line.

[sxemini]

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

In my case Patrik helped me to find another active copy of AM on my other notebook, which was causing conflicts and delays. The situation improved after I disabled it. However, BSODs still happen regardless of OC settings, no idea what to do with that.

Also, I'm still having trouble configuring ETH+ZIL dual mining. I re-read sxemini's guide, studied pool instructions but currently my miner (T-rex) immediately connects to Ezil/Rustpool instead of Ethermine and drops connection by timeout. Screenshots are attached, what am I doing wrong?





PS Tried adding following line to extra parameters, same result:  -a ethash -o stratum+tcp://asia.ezil.me:5555 -u <ETH address> -p <ZIL address>@asia1.ethermine.org:4444 -w Rig2 --extra-dag-epoch 0

My config only works for rustpool or shardpool. Why all using ezil for mining zil? Ezil is a eth+zil in one pool.
And you must understand, if you mining over for example rustpool -> it will only connect to rustpool, but you get the jobs from ethermine, because rustpool work as an proxy server.

If you want to mine zil on ezil and eth on ethermine, you need dual stratum connections -> teamredminer, lolminer, srbminer can handle it, but you need many more arguments for the commandline.b (maybe t-rex miner also, but also with more arguments)

There are so many ways to mine zil+eth/rvn/erg/vtc and so on, but first you must understand how zil mining and the pools are working (not so hard by the way)