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

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: patrike on November 30, 2018, 09:13:10 AM

Quote from: bensam1231 on November 30, 2018, 03:38:28 AM

Hey Patrik, please add a Tab for Properties>Command Line>Parameters in the main miner window where you have Summary, Pools, GPU, Etc when you click on each miner. That is probably the absolutely most tweaked and hardest to get to element in the UI right now. That's extremely useful for adjusting, testing new configs, troubleshooting.

Hello again and thanks for your feedback! I agree with your point here so I will see if there is a good way of making it easier to access this setting via the tabs while still not making it look too odd to have a specific setting outside the Properties.

There is also another feature that you might find helpful when testing different settings. In the Benchmark dialog for a miner, you can click on the drop down arrow next to the Start button to run a benchmark with specific command line parameters. This is intended to be a way where you try different command lines and see the result. What you enter here is however not saved to the Properties of the miner, but it for some testing scenarios it might still be of help.

Alright, yeah it is kinda out of place, but very useful for testing things. I'll check out the other option. I've never used the benchmark dialogue.

Can a c# script in rules be used to monitor a text file and look for a specific value such as a date and time?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: bensam1231 on November 30, 2018, 03:38:28 AM

Hey Patrik, please add a Tab for Properties>Command Line>Parameters in the main miner window where you have Summary, Pools, GPU, Etc when you click on each miner. That is probably the absolutely most tweaked and hardest to get to element in the UI right now. That's extremely useful for adjusting, testing new configs, troubleshooting.

Hello again and thanks for your feedback! I agree with your point here so I will see if there is a good way of making it easier to access this setting via the tabs while still not making it look too odd to have a specific setting outside the Properties.

There is also another feature that you might find helpful when testing different settings. In the Benchmark dialog for a miner, you can click on the drop down arrow next to the Start button to run a benchmark with specific command line parameters. This is intended to be a way where you try different command lines and see the result. What you enter here is however not saved to the Properties of the miner, but it for some testing scenarios it might still be of help.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on November 29, 2018, 08:41:10 PM

GMiner v1.10 available for download

v1.10
+ fixed performance regression on Equihash 144,5/Equihash 192,7 under Windows

Download links:
Linux x64 https://mega.nz/#F!HeIHzYDI!Rf3-qpxMjAkeQ7SDeeN2rw
Windows x64 https://mega.nz/#F!2GQl0AaR!_YzlNiVNNOUbEqYwz40E8A

New gminer 1.10 with improvements, you can provide me with a correct url to add it as custom, until you update again. Thanks in advance

The next release of Awesome Miner will use this link for v1.10:
https://s3.amazonaws.com/awesomeminer-download/gminer_1_10_windows64.zip

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: jaye1701 on November 29, 2018, 12:46:03 PM

Hello everyone!!

I updated about 20 minutes ago, and since there was a miner update (Gminer) I benchmarked like I always do.

This time however the benchmark failed. The miner would not start. I tried EWBF and it worked fine.
I then tried to mine BTG from miningpoolhub with both to make sure the pool was ok. Again, Gminer did the quick flash and fail.
I can't see what I am doing wrong. Anyone have any clue? Here is the diagnostic.

Initialize diagnostics (20)
Starting Diagnostics. Awesome Miner version: 6.0.1
OS: Microsoft Windows 10 Pro 64-bit
nVidia driver version: 416.34
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: GMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: GMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\Jaye\AppData\Local\AwesomeMiner\gminer_1_09_windows64_1\miner.exe -a 144_5 -s us-east.equihash-hub.miningpoolhub.com -n 20595 -u blahblah.blah -p x --api 4028
====================================================================================================
> personalization string not specified
Failed to start miner process: Process has exited, so the requested information is not available.
Failed to start miner in Diagnostics mode
Diagnostics completed

The issue is related to the missing personalization string. Did you manually add this pool in Awesome Miner, or was is a re-use of one of the predefined pools?

If you added this pool yourself, please open the properties of the pool and fill in the Personalization field: BgoldPoW

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: mmartoccia on November 29, 2018, 10:23:38 AM

Quote from: patrike on November 29, 2018, 04:24:23 AM

Quote from: mmartoccia on November 28, 2018, 04:29:33 PM

Is there a way to use Rules to be notified when a Pool Group reaches a profit value?

It should be possible if you create a Profit Profile that only uses this Pool Group.

You can then create a rule simliar to "Example: Start mining when profitability is above a defined value":
https://support.awesomeminer.com/support/solutions/articles/35000085907-rules-detect-mining-issues-and-automate-tasks

In this example, the action is to start the mining. You can change this to use the Notification action instead.

Appreciate the response! If I have more than one Profit Profile, how does the rule evaluate which of the two is at or above value?

OK - now I see the difficulty here. The trigger for "Revenue and profit" is considering all miners that you have enabled for the rule (either all miners or specific miners you apply the rule for).

If you configure the rule to look at the Profit Profile, it will look at the Profit Profile for each of the miners enabled for the rule. So you do need to have one miner using this Profit Profile for the concept to work. Based on your description, this may not be the case and you simply want to get notifications without having any miners using the Profit Profile already. Is that correct?

This trigger would then need to be improved to allow you to set a specific Profit Profile, not related to any of the profiles for the miners.

bensam1231

legendary

Activity: 1764

Merit: 1024

Hey Patrik, please add a Tab for Properties>Command Line>Parameters in the main miner window where you have Summary, Pools, GPU, Etc when you click on each miner. That is probably the absolutely most tweaked and hardest to get to element in the UI right now. That's extremely useful for adjusting, testing new configs, troubleshooting.

trucobit

jr. member

Activity: 756

Merit: 2

GMiner v1.10 available for download

v1.10
+ fixed performance regression on Equihash 144,5/Equihash 192,7 under Windows

Download links:
Linux x64 https://mega.nz/#F!HeIHzYDI!Rf3-qpxMjAkeQ7SDeeN2rw
Windows x64 https://mega.nz/#F!2GQl0AaR!_YzlNiVNNOUbEqYwz40E8A

New gminer 1.10 with improvements, you can provide me with a correct url to add it as custom, until you update again. Thanks in advance

jaye1701

newbie

Activity: 5

Merit: 0

Hello everyone!!

I updated about 20 minutes ago, and since there was a miner update (Gminer) I benchmarked like I always do.

This time however the benchmark failed. The miner would not start. I tried EWBF and it worked fine.
I then tried to mine BTG from miningpoolhub with both to make sure the pool was ok. Again, Gminer did the quick flash and fail.
I can't see what I am doing wrong. Anyone have any clue? Here is the diagnostic.

Initialize diagnostics (20)
Starting Diagnostics. Awesome Miner version: 6.0.1
OS: Microsoft Windows 10 Pro 64-bit
nVidia driver version: 416.34
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: GMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: GMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\Jaye\AppData\Local\AwesomeMiner\gminer_1_09_windows64_1\miner.exe -a 144_5 -s us-east.equihash-hub.miningpoolhub.com -n 20595 -u blahblah.blah -p x --api 4028
====================================================================================================
> personalization string not specified
Failed to start miner process: Process has exited, so the requested information is not available.
Failed to start miner in Diagnostics mode
Diagnostics completed

mmartoccia

newbie

Activity: 47

Merit: 0

Quote from: patrike on November 29, 2018, 04:24:23 AM

Quote from: mmartoccia on November 28, 2018, 04:29:33 PM

Is there a way to use Rules to be notified when a Pool Group reaches a profit value?

It should be possible if you create a Profit Profile that only uses this Pool Group.

You can then create a rule simliar to "Example: Start mining when profitability is above a defined value":
https://support.awesomeminer.com/support/solutions/articles/35000085907-rules-detect-mining-issues-and-automate-tasks

In this example, the action is to start the mining. You can change this to use the Notification action instead.

Appreciate the response! If I have more than one Profit Profile, how does the rule evaluate which of the two is at or above value?

Allo-4ka

newbie

Activity: 71

Merit: 0

Quote from: patrike on November 28, 2018, 08:35:02 AM

Are there only a few specific coins that are incorrect on Coincalculators? Any example?

At first there was a MAZA coin and then BCHSV. There were a few more, but I don’t remember

baf28

newbie

Activity: 117

Merit: 0

Quote from: patrike on November 29, 2018, 04:41:01 AM

Awesome Miner version 6.0.1

Mining software
- Gminer Cuda Miner 1.09
Corrections
- Correction to an issue where Awesome Miner didn't start correctly on some systems

thank
Version 6.0-6.0.1 is a great and very good update.
Thank.

patrike

legendary

Activity: 3346

Merit: 1094

Awesome Miner version 6.0.1

Mining software
- Gminer Cuda Miner 1.09
Corrections
- Correction to an issue where Awesome Miner didn't start correctly on some systems

baf28

newbie

Activity: 117

Merit: 0

Quote from: patrike on November 29, 2018, 03:54:18 AM

Quote from: baf28 on November 29, 2018, 02:39:22 AM

Quote from: trucobit on November 28, 2018, 11:26:33 PM

Quote from: baf28 on November 28, 2018, 10:41:39 PM

After stopping mining, the gminer continues to work.
This problem is present if Hide Window is set in the settings of the Environment.
Please fix the bug
Thank.

I use gminer and I've only encountered problems with RTX.

I have one of the rigs with 1070 and 1060, and the error you indicate does not happen to me.

If there is still a problem, it is not from Awesome miner, it is from the miner himself and we will have to wait for an update. Do not blame this program for the faults of a specific miner.

This problem is in an awesome miner. The problem is when the miner window is hidden. When the miner window is visible, everything works correctly.
Awesome miner does not give a command or does not give the correct command to turn off Gminer.

I wasn't able to reproduce this, but it could be some timing thing related to when Awesome Miner terminates the Gminer process and the built-in watchdog in Gminer.

Could you please start Gminer with the watchdog disabled to see if you run into the same problem. You can add the command line:
-w 0

Please let me know the result - thanks!

Yes, this option turns off the miner, Gminer turns off.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: baf28 on November 28, 2018, 09:32:20 PM

Sorry, problem solved: - New setting to force CUDA device order to follow the GPU PCI Bus ID. In case of mixed nVidia GPU models in the same system, this can resolve issues to the GPU selection order.
Thank you, all that is written below is no longer relevant.

Thanks for the update. The new feature to use force the CUDA mining software to use PCI Bus ID order is actually the best setup to have.

The reason why I've not made it default yet is that it may change the device order that users already have configured, and then a new release of Awesome Miner would all of a sudden would instruct the mining software to mine on other GPU's than before.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: mmartoccia on November 28, 2018, 04:29:33 PM

Is there a way to use Rules to be notified when a Pool Group reaches a profit value?

It should be possible if you create a Profit Profile that only uses this Pool Group.

You can then create a rule simliar to "Example: Start mining when profitability is above a defined value":
https://support.awesomeminer.com/support/solutions/articles/35000085907-rules-detect-mining-issues-and-automate-tasks

In this example, the action is to start the mining. You can change this to use the Notification action instead.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: baf28 on November 29, 2018, 02:39:22 AM

Quote from: trucobit on November 28, 2018, 11:26:33 PM

Quote from: baf28 on November 28, 2018, 10:41:39 PM

After stopping mining, the gminer continues to work.
This problem is present if Hide Window is set in the settings of the Environment.
Please fix the bug
Thank.

I use gminer and I've only encountered problems with RTX.

I have one of the rigs with 1070 and 1060, and the error you indicate does not happen to me.

If there is still a problem, it is not from Awesome miner, it is from the miner himself and we will have to wait for an update. Do not blame this program for the faults of a specific miner.

This problem is in an awesome miner. The problem is when the miner window is hidden. When the miner window is visible, everything works correctly.
Awesome miner does not give a command or does not give the correct command to turn off Gminer.

I wasn't able to reproduce this, but it could be some timing thing related to when Awesome Miner terminates the Gminer process and the built-in watchdog in Gminer.

Could you please start Gminer with the watchdog disabled to see if you run into the same problem. You can add the command line:
-w 0

Please let me know the result - thanks!

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: baf28 on November 29, 2018, 02:55:25 AM

I found a very serious problem on all my farms in version 6.0
After restarting Avesome’s computer, the miner starts and immediately shuts down. after manual start it works.

I've found the issue that could cause Awesome Miner to shutdown shortly after starting. There will be a 6.0.1 release available very soon.

baf28

newbie

Activity: 117

Merit: 0

I found a very serious problem on all my farms in version 6.0
After restarting Avesome’s computer, the miner starts and immediately shuts down. after manual start it works.

Code:

29.11.2018 13:49:54.522 [001] [S]Configuration Created: 19.02.2018 3:55:07
29.11.2018 13:49:54.522 [001] [S]External miners: 0, Managed miners: 2
29.11.2018 13:49:54.522 [001] [S]Checksum:
29.11.2018 13:49:54.694 [020] [S]Loaded assembly: PE.Sqlite, Version=6.0.0.0, Culture=neutral, PublicKeyToken=null
29.11.2018 13:49:54.694 [001] [S]Application Context Form Display
29.11.2018 13:49:54.694 [001] [S]Loading system tray icon
29.11.2018 13:49:54.694 [001] [S]System tray icon loaded: True
29.11.2018 13:49:54.709 [020] [S]Loaded assembly: System.Data.SQLite, Version=1.0.108.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139
29.11.2018 13:49:54.709 [020] [S]Loaded assembly: System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
29.11.2018 13:49:54.803 [020] [S]Loaded assembly: System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
29.11.2018 13:49:54.850 [020] [S]Adding index to database
29.11.2018 13:49:54.850 [020] [S]Database initialized
29.11.2018 13:49:54.944 [007] [S][ManagedMiner#6 - 1050ti] Execute command: Add
29.11.2018 13:49:54.944 [007] [S][ManagedMiner#6 - 1050ti] Adding miner
29.11.2018 13:49:54.944 [007] [S][ManagedMiner#6 - 1050ti] Setting up Miner Engine. Instance: 1
29.11.2018 13:49:54.944 [007] [S][ManagedMiner#6 - 1050ti] Engine Type: 7, Auto Download: True, EnginePath: D:\Shara\Maйнинг\Miner Soft\gminer_1_08_windows64\miner.exe, Subtype: Disabled, CustomExecutable:
29.11.2018 13:49:54.944 [007] [S]EngineSetup: 7
29.11.2018 13:49:54.944 [007] [S][ManagedMiner#6 - 1050ti] InstanceID: 1
29.11.2018 13:49:54.944 [007] [S]Looking for process: 3368
29.11.2018 13:49:54.944 [007] [S][ManagedMiner#6 - 1050ti] Couldn't reattach.
29.11.2018 13:49:55.037 [001] [S]Failed to initialize threads
29.11.2018 13:49:56.803 [013] [S]nVidia driver version: 25.21.14.1634
29.11.2018 13:49:56.803 [013] [S]nVidia driver version: 25.21.14.1634
29.11.2018 13:49:56.803 [013] [S]nVidia driver version: 25.21.14.1634
29.11.2018 13:50:25.053 [001] [S]CoreContext received event for Shutdown
29.11.2018 13:50:25.053 [001] [S]Shutdown: Save statistics
29.11.2018 13:50:25.647 [007] [S]Shutting down ManagedController - Running miners: 2
29.11.2018 13:50:25.647 [007] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
29.11.2018 13:50:25.662 [007] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
29.11.2018 13:50:25.834 [001] [S]Shutting down timer
29.11.2018 13:50:25.850 [001] [S]Request to close Main Window
29.11.2018 13:50:26.022 [001] [S]Shutdown: Save configuration
29.11.2018 13:50:26.022 [001] [S]Wait for Save Thread to terminate
29.11.2018 13:50:26.162 [003] [S]Saving configuration to: C:\Users\Alexandr\AppData\Roaming\AwesomeMiner\ConfigData.xml.tmp

baf28

newbie

Activity: 117

Merit: 0

Quote from: trucobit on November 28, 2018, 11:26:33 PM

Quote from: baf28 on November 28, 2018, 10:41:39 PM

After stopping mining, the gminer continues to work.
This problem is present if Hide Window is set in the settings of the Environment.
Please fix the bug
Thank.

I use gminer and I've only encountered problems with RTX.

I have one of the rigs with 1070 and 1060, and the error you indicate does not happen to me.

If there is still a problem, it is not from Awesome miner, it is from the miner himself and we will have to wait for an update. Do not blame this program for the faults of a specific miner.

This problem is in an awesome miner. The problem is when the miner window is hidden. When the miner window is visible, everything works correctly.
Awesome miner does not give a command or does not give the correct command to turn off Gminer.

zergbitcore

newbie

Activity: 17

Merit: 0

Patrike, I see the problem with autostart after power fail. Awesome miner did not start while it was set to start automatically with windows. It always works well, but not after power fail. 2 rigs - same problem. There is something wrong with this in version 6.

UPD: I saw Awesome Miner starts with Windows, but it closes itself after several seconds without any error message...

UPD2: I created a task to start awesome miner if it is not running. This task makes awesome miner to start, but it also closes with no reason after several seconds... If start it manually by mouse click it works without closing.

Any thoughts?

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