Quote from: chuckinsuburbia on June 25, 2019, 03:59:41 PM

Quote from: patrike on June 25, 2019, 10:27:53 AM

Quote from: chuckinsuburbia on June 24, 2019, 02:04:36 PM

Quote from: patrike on June 24, 2019, 01:02:54 PM

Quote from: chuckinsuburbia on June 23, 2019, 05:44:42 PM

Quote from: patrike on June 21, 2019, 09:31:22 PM

Quote from: chuckinsuburbia on June 21, 2019, 12:05:23 AM

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?

Code:

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.