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

solved

it is fixed
i just unsintalled and reinstalled the intellibreezemaintenance service via new powershell and it works again -  i have no idea why...but anyway...next time i got the problem i will just do the same. until his...is there any way to "reset" all logs so that i have fresh start with logging? the log files i found was very huge allready

Thanks for the update. Although I agree that the worker name setup looks strange, the main issue is a permission problem where the Administrator task to run the mining software fails to register due to "Access Denied".

1) If possible, send me the complete Awesome Miner log in addition to the complete log "C:\ProgramData\IntelliBreeze\IntelliBreezeMaintenance.log". This will give me a more complete understanding of the issue. You can submit the logs here if you want:
https://www.awesomeminer.com/contact

2) Do you have any non-default permissions on your user folder or run any specific security software that could prevent the access?

at first - mining process is running on this machine with installed Awesome miner manager (no remote machine)

i think i see the problem but dont know the cause - there is "-w 164836"
in the miner settings i dont check "add to workername" and in pool settings i have workername.164836 (which is rig identifier in miningrigrentals).
the strangest thing is...i deleted identifier...now i have only workername (norman666) and nothing more...BUT...the log shows again the -w 164836

there must be something like a other config that AM used when i start mining process as admin
i have no entries in the other tabs in "managed miner properties" only general is filled and environment



with workername and rig identifier:

24.05.2022 15:29:04.247 [013] [S ]RegisterTask: Awesome.Execute001 C:\Users\Norman\AppData\Local\AwesomeMiner\t-rex-0.26.4-win_1\t-rex.exe, Account: Norman
24.05.2022 15:29:04.270 [013] [S ]  Prepare RegisterTask: Awesome.Execute001 C:\Users\Norman\AppData\Local\AwesomeMiner\t-rex-0.26.4-win_1\t-rex.exe, Account: Norman
24.05.2022 15:29:04.290 [013] [E ]Command: C:\Users\Norman\AppData\Local\AwesomeMiner\t-rex-0.26.4-win_1\t-rex.exe, Parameters:  --no-watchdog --pci-indexing -a ethash -o stratum+tcp://eu-de01.miningrigrentals.com:3344 -p x -u norman666.164836 -w 164836 --api-bind-http 0.0.0.0:4028, AccountName: Norman
 System.UnauthorizedAccessException: Zugriff verweigert (Ausnahme von HRESULT: 0x80070005 (E_ACCESSDENIED))
24.05.2022 15:29:04.294 [013] [E ]   bei Microsoft.Win32.TaskScheduler.V2Interop.ITaskFolder.RegisterTaskDefinition(String Path, ITaskDefinition pDefinition, Int32 flags, Object UserId, Object password, TaskLogonType LogonType, Object sddl)
   bei Microsoft.Win32.TaskScheduler.TaskFolder.RegisterTaskDefinition(String path, TaskDefinition definition, TaskCreation createType, String userId, String password, TaskLogonType logonType, String sddl)
   bei IntelliBreeze.TaskSchedule.TaskManager.RegisterTask(TaskInfo taskInfo)



without rig identifier

24.05.2022 15:36:52.058 [005] [S ]RegisterTask: Awesome.Execute001 C:\Users\Norman\AppData\Local\AwesomeMiner\t-rex-0.26.4-win_1\t-rex.exe, Account: Norman
24.05.2022 15:36:52.059 [005] [S ]  Prepare RegisterTask: Awesome.Execute001 C:\Users\Norman\AppData\Local\AwesomeMiner\t-rex-0.26.4-win_1\t-rex.exe, Account: Norman
24.05.2022 15:36:52.063 [005] [E ]Command: C:\Users\Norman\AppData\Local\AwesomeMiner\t-rex-0.26.4-win_1\t-rex.exe, Parameters:  --no-watchdog --pci-indexing -a ethash -o stratum+tcp://eu-de01.miningrigrentals.com:3344 -p x -u norman666.164836 -w 164836 --api-bind-http 0.0.0.0:4028, AccountName: Norman
 System.UnauthorizedAccessException: Zugriff verweigert (Ausnahme von HRESULT: 0x80070005 (E_ACCESSDENIED))
24.05.2022 15:36:52.063 [005] [E ]   bei Microsoft.Win32.TaskScheduler.V2Interop.ITaskFolder.RegisterTaskDefinition(String Path, ITaskDefinition pDefinition, Int32 flags, Object UserId, Object password, TaskLogonType LogonType, Object sddl)
   bei Microsoft.Win32.TaskScheduler.TaskFolder.RegisterTaskDefinition(String path, TaskDefinition definition, TaskCreation createType, String userId, String password, TaskLogonType logonType, String sddl)
   bei IntelliBreeze.TaskSchedule.TaskManager.RegisterTask(TaskInfo taskInfo)

Thanks for the feedback. I agree with your point here and you can expect this to be improved in the near future.

Hi,

Please try to start T-Rex as Admin one more time, to make sure there is a recent log file entry with the attempt.

Please send me the following:
1) Remote Agent log file

2) The log file "C:\ProgramData\IntelliBreeze\IntelliBreezeMaintenance.log" from the Remote Agent computer.

Thanks,
Patrik

need to come back with this problem

after t-rex update...i have the problem again and now i cant even solve by reinstalling.

when i uncheck "run mining process with Administrator privileges" t-rex is starting, but stops cause admin needed
wenn i check "run mining process with Administrator privileges" the starting failed

i can run the awesome-start.bat in t-rex folder "as administrator" and it runs

so...what the hell is the problem? the intellibreeze service is running...

Hi Patrike,

i use the activity log and it is nice, but is it possibly to specify the source a little bit? It would be good to show the name of the rule that was triggert. I have many rules for tags, and at the moment i only see - source = rule, typ = miner and action = tags. But showing the rule name make it easier to find a failure for example. I know i can see the rule history with the rule name, but a little bit more information for the activiy log would be nice.

Thanks


Use the HiveOS distribution. It works well with AM, easy and fast install.

Hi Patrike, pls. push update for MiniZ miner https://github.com/miniZ-miner/miniZ/releases Regards

Thanks for the update!  We made a step forward, I can now see one GPU out of 10. I see only GPU ID: 0. It is probable something related about xorg or screen or else... sould I reinstall AM service?

Alos noticed lot of errors in the agent log

also I'm running uBuntu 22 and not 20 like stated earlier.  I wil test with uBuntu 18 this week-end

Thanks for the update.

Can you please send me the Remote Agent log file? First, try to run into this problem again, so it's a recent attempt to start / stop the miner.

The log file can be found either via the Awesome Miner toolbar Tools -> Log File -> Remote Agent, or on the computer running the Remote Agent where you can right click on the Remote Agent icon to access to log file.

You can submit the log file via this page. Thanks!
https://www.awesomeminer.com/contact

Please try to run the following to re-initialize the configuration for nVidia overclocking:
​sudo nvidia-xconfig -a --cool-bits=31 --allow-empty-initial-configuration
​sudo reboot

Just got a license for 2 rigs to get out of HiveOS.

Unfortunately, I'm unable to overclock any of my 10 GPUs on the first rig where I want tot test AM.

RIG OS: Ubuntu 20.04
Linux agent installed  (RIG is fully managed by AM)
Rig discovered by AM Windows app
Can stat mining... but useless as I can't at least set fan speeds to what I want. Overheat within a minute and I have to stop it
GPUs: RTX A4000 and RTX A2000 and one RTX 2060 super

Error message I get: Unable to read GPU information.

Should I conclude that overclocking feature is useless for a mining rig running on a Linux OS?  if so, I will have to ask a refund as I don't want to run on Windows

Awesome Miner version 9.4.3

 ASIC mining
  - Initial support for ePic Blockchain SC200 (Sia ASIC miner)
  - Firmware mining profile configuration includes properties for setting Global Voltage and Global Frequency
 GPU mining
  - Improved support for nVidia driver 510.xx on Linux for GPU clocking
 Mining software
  - Gminer 2.96
  - Lolminer 1.51
  - TeamRedMiner 0.10.0
 Corrections
  - Correction to miner status filter
  - Corrected detection of current firmware mining profile for Antminer S19j Pro running the Awesome Miner firmware

Thanks for the nice feedback!

Hi and thanks for your report. I've sent you a private message on this topic.

Hi, i have  problem with 3080 cards . All rigs i use have a problem with memory clock. Everytime i change in AW oc settings , all parametres change ( power, fans) exept memory clock, it stay same all the time (9251) not  what i set in AW . Rigs work on hiveos
Miner i try is nbminer 41,5 also Lolminer 1.50 .
Why i think it is problem from AW as when i set same oc in hive os and start mining there it work normally, memory push up and hashrate also.
Please let me know if there is any idea to solve it.
Thanks

Awesome Miner version 9.4.2

 GPU mining
  - The global fan control can be configured to consider the GPU memory temperature
 Features
  - Record current outside temperature and make available in the Miner Graph. Configure your current location in the Options dialog, Dashboard and History section.
  - Rule trigger for outside temperature
  - Additional temperature methods made available via C# scripting feature
 Mining software
  - Gminer 2.95
  - Lolminer 1.50
  - NbMiner 41.5
 Corrections
  - Correction to Antminer L7 board hashrate display

Hi.

1) Please go to the Awesome Miner Options dialog, Managed Hosts section. Please verify that you don't have two entries pointing to the same IP address.
2) Please also make sure you only have one single Awesome Miner instance controlling these Remote Agents, so you don't have a second Awesome Miner on the network trying to control the same Remote Agents.
3) Is it always the case that the Stop command isn't working for these two specific computers? So a reboot doesn't resolve the problem?
4) Does this happen only when running the mining instance as Administrator or is it the same no matter if running as Administrator or not?