custom miner shows offline

[ParaplegicRacehorse]

running tpruvot/cpuminer-multi as custom. Note the terminal window top output.

Also had to pass all normal cli flags in the config window. Minera did not configure miner with pool/user/pass settings in config section.

Is this normal for custom miners?

[michelem09]

No it isn't, please check the miner logs and let me see it.

[ParaplegicRacehorse]

Gonna have to wait. OS updates require that I reinstall everything. Maybe it will even fix this error. I'll let you know tomorrow. It's bedtime here.

I wonder if this next install will rewrite my ssh keys again. Grr.

[michelem09]

How do you start it? Via Minera or manually?

[ParaplegicRacehorse]

The cpuminer? I start via minera. Installing minera ruins my ability to ssh from terminal, which is how I manage the rest of machine. I probably will not reinstall for that reason.

[ParaplegicRacehorse]

I just discovered that tprovot/cpuminer-multi, since 1.0.8, has had an API for monitoring (defaults to 127.0.0.1:4048). I assume I need to set the IP and port numbers to a range Minera looks for? Will it be the same as for bfgminer and others?

I will probably reinstall and test this out if I can figure out how/where to publish the API in a way Minera can monitor it. As for ssh keys, I'll figure something out. It bothers me a lot that Minera overwrites my existing key but it's not the end of the world. I won't do this today (probably) but I'll let you know what I discover.

[michelem09]

I think it uses a different way to get API requests but I'm unable to test it because I'm living abroad for the next months.

[michelem09]

Hello, I have investigated this and I can confirmcpuminer-multi works fine on Minera but you have to configure it. First of all, JSON file doesn't work I don't know why probably it want a different format, so disable it from Minera and put your miner command on Manual Options textarea like this:

-o stratum+tcp://<pool_url>:<pool_port> -u <pool_user> -p x --api-bind=127.0.0.1:4028

Note! You have also to use the option --api-bind because it runs by default on port 4048 while Minera get by default port 4028, this is why you didn't see anything in the dashboard.

Please let me know.

[ParaplegicRacehorse]

Thanks, Michele. I'm at sea and away from my miners for the rest of the year, unable to experiment. The API port difference makes sense.

I had to remove Minera from my miners, though. Node is extremely CPU-intensive, using up about 20% of my CPU cycles just to run it, an unacceptable loss of hash power for a CPU miner. I'm sure that's different for recent Intel and AMD processors, but my ARM machines just won't sustain Node and be profitable.

On May 4, 2017 02:38, "Michele Marcucci" notifications@github.com wrote:

Hello, I have investigare this and I can confirmcpuminer-multi works fine on Minera but you have to configure it. First of all, JSON file doesn't work I don't know why probably it want a different format, so disable it from Minera and put your miner command on Manual Options textarea like this:

-o stratum+tcp://: -u -p x --api-bind= 127.0.0.1:4028

Note! You have also to use the option --api-bind because it runs by default on port 4048 while Minera get by default port 4028, this is why you didn't see anything in the dashboard.

Please let me know.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/michelem09/minera/issues/157#issuecomment-299107419, or mute the thread https://github.com/notifications/unsubscribe-auth/AHQOiNpe7l0WW4HHro0TYW1PdP-Dvg6Rks5r2XJKgaJpZM4L3WAB .

[michelem09]

Oh well RPI cpu isn't so good to ask it a lot of things to do, yes better to put Minera in a desktop or server.