 Show Posts
|
|
Pages: [1]
|
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it? 6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon. Unfortunately this still seems to be an issue in 6.5.7. For this user defined Managed Software you added for CpuMiner - have you configured it to have the compatibility mode "Full" with CpuMinerOpt? I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters. Yes, it is configured as Full (Command line and API). Sorry, I probably should have mentioned in my original post, but I saw some similar behavior with the Windows agent in 6.5.6 where it would not use the algorithm argument from the "Default command line argument" column, but would use an argument from the "User defined command line algorithm" column even if it was the same value. I worked around this by simply replicating all the default args as user defined args. But this workaround did not seem to work for the Linux agent. So this may be a combination of multiple issues. I'm happy to provide any additional info you might need to track this down. What I still could reproduce on Linux for 6.5.7 was that the "User defined command line" not being used correctly and I will of course correct that. It should however fallback to use the "Default command line argument" in 6.5.7 (didn't work in 6.5.6). Is it not even doing this fallback when you test it? I'm away from my rigs for a day or so, but I will run through some more tests as soon as I can and post the results. My apologies for the super delayed response, just wanted to say that whatever issue I was seeing before seems to have been resolved at this point. |
|
|
|
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it? 6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon. Unfortunately this still seems to be an issue in 6.5.7. For this user defined Managed Software you added for CpuMiner - have you configured it to have the compatibility mode "Full" with CpuMinerOpt? I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters. Yes, it is configured as Full (Command line and API). Sorry, I probably should have mentioned in my original post, but I saw some similar behavior with the Windows agent in 6.5.6 where it would not use the algorithm argument from the "Default command line argument" column, but would use an argument from the "User defined command line algorithm" column even if it was the same value. I worked around this by simply replicating all the default args as user defined args. But this workaround did not seem to work for the Linux agent. So this may be a combination of multiple issues. I'm happy to provide any additional info you might need to track this down. What I still could reproduce on Linux for 6.5.7 was that the "User defined command line" not being used correctly and I will of course correct that. It should however fallback to use the "Default command line argument" in 6.5.7 (didn't work in 6.5.6). Is it not even doing this fallback when you test it? I'm away from my rigs for a day or so, but I will run through some more tests as soon as I can and post the results. |
|
|
|
I have a Linux agent and was able to run Claymore's dual ETH miner using AM's default settings. Although it does appear that the GPU clocking profile is being ignored.
how time used LA? in new installation not work epools is clear, manual correction epools not work too - after start LA clear file recreated Sorry, I'm not 100% sure what you're asking, but I did a new install on Ubuntu 18.04 on 2019-06-16, on a rig that was having OS stability issues with Windows. The agent has been updated to the latest dev release 6.5.7 and have had no issues with the supported miners. |
|
|
|
Thanks for the feedback.
It's correct that Linux on Remote Agent doesn't include all features and all mining software. For mining software it's about 20 of them supported and the Claymore miners should work fine.
Can you please let me know the main features you are missing? The goal is of course to continue improving Remote Agent on Linux so all feedback is of course welcome. Thanks!
Hi Patrik. Thank you for paying attention to me. I confirm that none of the Caymore`s miners work by default. Only dances with a tambourine forced Dual miner to work and then only when I registered him completely the launch line in the profile. With the rest so far did not suffer. On the tab GPU there is no control of energy consumption. Its utilites report from my test rig ========================ROCm System Management Interface======================== ================================================================================ GPU Temp AvgPwr SCLK MCLK Fan Perf PwrCap SCLK OD MCLK OD GPU% 0 67.0c 80.0W 1140Mhz 2150Mhz 100.0% manual N/A 0% 0% N/A 1 64.0c 83.0W 1140Mhz 2150Mhz 80.0% manual N/A 0% 0% N/A 2 66.0c 82.0W 1140Mhz 2150Mhz 60.0% manual N/A 0% 0% N/A 3 67.0c 88.0W 1140Mhz 2150Mhz 61.96% manual N/A 0% 0% N/A 4 64.0c 80.0W 1140Mhz 2150Mhz 80.0% manual N/A 0% 0% N/A 5 65.0c 84.0W 1140Mhz 2150Mhz 100.0% manual N/A 0% 0% N/A 6 66.0c 77.0W 1140Mhz 2150Mhz 61.96% manual N/A 0% 0% N/A ================================================================================ ==============================End of ROCm SMI Log ============================== I will be glad to provide all possible assistance in testing the Linux Agent, if necessary. Sincerely, Vladimir. p.s. I do not see the possibility to insert screenshots. I have a Linux agent and was able to run Claymore's dual ETH miner using AM's default settings. Although it does appear that the GPU clocking profile is being ignored. |
|
|
|
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it? 6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon. Unfortunately this still seems to be an issue in 6.5.7. For this user defined Managed Software you added for CpuMiner - have you configured it to have the compatibility mode "Full" with CpuMinerOpt? I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters. Yes, it is configured as Full (Command line and API). Sorry, I probably should have mentioned in my original post, but I saw some similar behavior with the Windows agent in 6.5.6 where it would not use the algorithm argument from the "Default command line argument" column, but would use an argument from the "User defined command line algorithm" column even if it was the same value. I worked around this by simply replicating all the default args as user defined args. But this workaround did not seem to work for the Linux agent. So this may be a combination of multiple issues. I'm happy to provide any additional info you might need to track this down. |
|
|
|
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it? 6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon. Unfortunately this still seems to be an issue in 6.5.7. |
|
|
|
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it? 6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon. Thanks for the quick fix as always. |
|
|
|
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it? 6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
|
|
|
|
|
Great product and support, keep up the good work.
I just wanted to suggest a "nice to have" feature for future consideration. It would be nice to have a statistic for profit margin (daily profit / daily revenue), which could then be used in rules. E.g.: If profit margin is less than 10%, stop miner.
|
|
|
|
For any others having the same trouble I had, the Linux agent runs the miner software using the screen utility, which isn't installed by default in Ubuntu. Just do and you should be good to go. Has anyone had luck with the remote agent for Linux? I installed the agent on a fresh Ubuntu 18.04 install but I'm having some trouble getting a miner to start. Downloaded and installed according to the docs at https://support.awesomeminer.com/support/solutions/articles/35000086210-remote-agent-for-linuxException: installed in /usr/local/awesomeminer-remoteagent/ and updated awesome.service accordingly. Agent starts and can be seen by my server, but starting any mining software fails. Diagnostics shows Failed to start miner process: No such file or directory (full output pasted below). It looks like the miner is being downloaded to an absolute path (/AwesomeMinerService/t-rex-0.5.6-linux-cuda9.1_1/) but the agent is looking for it using a relative path. Any help or guidance would be greatly appreciated. Initialize diagnostics (10)
Starting Diagnostics. Awesome Miner Remote Agent version: 5.5
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: TrexMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
AwesomeMinerService/t-rex-0.5.6-linux-cuda9.1_1/t-rex -a lyra2z -o stratum+tcp://lyra2z.mine.ahashpool.com:4553 -u [redacted] -p c=BTC --api-bind-http 0.0.0.0:4028 (WindowMode: ConsoleFormat, EngineType: TrexMiner, IsProfitMiner: False)
Configuration:
Failed to start miner process: No such file or directory
Failed to start miner in Diagnostics mode
Diagnostics completed
|
|
|
|
Has anyone had luck with the remote agent for Linux? I installed the agent on a fresh Ubuntu 18.04 install but I'm having some trouble getting a miner to start. Downloaded and installed according to the docs at https://support.awesomeminer.com/support/solutions/articles/35000086210-remote-agent-for-linuxException: installed in /usr/local/awesomeminer-remoteagent/ and updated awesome.service accordingly. Agent starts and can be seen by my server, but starting any mining software fails. Diagnostics shows Failed to start miner process: No such file or directory (full output pasted below). It looks like the miner is being downloaded to an absolute path (/AwesomeMinerService/t-rex-0.5.6-linux-cuda9.1_1/) but the agent is looking for it using a relative path. Any help or guidance would be greatly appreciated. Initialize diagnostics (10)
Starting Diagnostics. Awesome Miner Remote Agent version: 5.5
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: TrexMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
AwesomeMinerService/t-rex-0.5.6-linux-cuda9.1_1/t-rex -a lyra2z -o stratum+tcp://lyra2z.mine.ahashpool.com:4553 -u [redacted] -p c=BTC --api-bind-http 0.0.0.0:4028 (WindowMode: ConsoleFormat, EngineType: TrexMiner, IsProfitMiner: False)
Configuration:
Failed to start miner process: No such file or directory
Failed to start miner in Diagnostics mode
Diagnostics completed
|
|
|
|
|
