this is a log of Diagnostic tool:
Initialize diagnostics (40)
Starting Diagnostics (120s). Awesome Miner Remote Agent version: 8.1.12
OS: Unix 5.0.21.0
GPU Details:
nVidia driver version: 450.80.02
GPUs:
Prerequisites:
Microsoft .NET Framework: 4.0.30319.42000
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: No
Microsoft VC++ 2017 runtime installed: No
Microsoft VC++ 2019 runtime installed: No
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: TrexMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Set clocking start profile: 196, 2080TI_P85_C150_M(1600-2000)_F(0-100)_CFX (when stopping, the following will be used: 3, type: Single, Use: True)
Properties: (WindowMode: ConsoleFormat, EngineType: TrexMiner, IsProfitMiner: True, RunAsAdmin: False)
====================================================================================================
/root/.config/AwesomeMinerService/t-rex-0.19.3-linux-cuda10.0.tar_1/t-rex -i 23 --no-watchdog --pci-indexing -a octopus -o stratum+tcp://cfx-eu.ss.poolflare.com:3366 -p x -u 0x1975ae1c8a11F232CC49c4DBdeC8e4E1Ee197d3E.2080TI --api-bind-http 0.0.0.0:4028
Configured command line:
-i 23
====================================================================================================
Mining Engine Process started, PID: 26313
20201211 21:32:43 TREX: eyJhIjoiTzNnZHowWDl4V0R3UkpaWXhaK1kvUTQzTFlpeDhTaHA0VW10UEZOQmNCdz0iLCJiIjoiYTlmQzBZeVdOa0JTMjBpSTI4c2JkUT09In0K
====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed
AM started wrong miner, must start G-Miner and mine Cortex, but always tryed to start T-Rex. What happens with remote agent after updating? How to repair? I am not fisicaly near miner.
I am not understand, why AM constantly try to start wrong configuration. I have changed miner soft in profit profile, looks like ufter update somethig go wrong with configuration.
Patrike please help. Big problem!
Upd: T-Rex 0.19.3 defenitly not work with AM 8.1.12 i am on Linux Driver 450.80.02 and 455.45.01 (But driver version not important for this problem)
I can start miners as Managed Miner, but if i try use T-Rex i get this restarting loop and crash. Now i must change Profit Profile for all miners and algo where T-Rex is used. Or wait on next update
Upd: Update has corrupted a Profit Profile data for some miners, only copy of Profit Profile from normal working miner have solve problem of corrupted data. But if i invistigate a corrupted Profit Profile, the data wich set for algos looks absolutly normal. this corruption have impact on Profit switching of course
upd: Found another thing. If miner configured as Managed Miner and you try mine Eth on Niceahsh with PhoenixMiner 5.3b, you get disconnected.
upd: i have try to start miner directly from terminal window with following comand string:
/root/.config/AwesomeMinerService/t-rex-0.19.3-linux-cuda10.0.tar_1/t-rex --no-watchdog --pci-indexing -a octopus -o stratum+tcp://cfx-eu.ss.poolflare.com:3366 -p x -u 0x1975ae1c8a11F232CC49c4DBdeC8e4E1Ee197d3E.2080TIRS-02 --api-bind-http 0.0.0.0:4028
and all works super. Looks like after update something go wrong for T-Rex miner on the AM side. Other mining programs work without problems. I have cleared mining software over AM, but that not help. I have try to use ConfigData.xml file from backup before update, that not help too. I have no idea how to solve this problem. Will try to reinstall AM.
Upd: reinstalling of AM not help. I have put in rig other USB with AwesomeMinerAgent 8.10.0 and started AM, same problem. Looks like problem on the AM v. 8.1.12 main programm side.
Patrike, where user can find a archive for old versions of AM. In this situation like i have now, maybe this is only sollution to downgrade the AM version.
Next problem found: Unable automatic download of MiniZ miner if rig OS is Linux.
Upd: T-Rex 0.19.1 works on AM 8.1.12 without problem.
Upd: Update T-Rex miner to 0.19.4 not solve this Base64 problem. But looks like the problem on the T-Rex miner side.
Upd: Have tested starting T-Rex 0.19.4 from terminal window with command string:
/root/.config/AwesomeMinerService/t-rex-0.19.4-linux-cuda11.1.tar_1/t-rex --no-watchdog --pci-indexing -a octopus -o stratum+tcp://cfx-eu.ss.poolflare.com:3366 -p x -u 0x1975ae1c8a11F232CC49c4DBdeC8e4E1Ee197d3E.2080TIRS-02 --api-bind-http 0.0.0.0:4028
and T-Rex started without problem. Where is a problem now? T-Rex or AwesomeMiner side? Using T-Rex and AM different base64 libs? Was base64 lib upgraded recently? Is base64 lib functionality compatible on different OS now?