JayDDee / cpuminer-opt

Optimized multi algo CPU miner
Other
765 stars 543 forks source link

Solomining not working "json_rpc_call failed", but works with original tpruvot miner #339

Closed Shai0Hulud closed 2 years ago

Shai0Hulud commented 2 years ago

Hey there! I am testmining scrypt algos. Using your optimized miner in pools is no problem, but I cant get it to work for solomining.

Original tpruvot miner works with the exact same settings, so something reagrding solomining must have changed (on purpose?).

For smaller and/or new projects cpumining scrypt is still an option ^^

Would be nice if your cpuminer works too, as your hashrate is a lot higher (3950X, 16 cores used: 240kH/s vs. 180kH/s [tpruvot])

image

Cheers!

JayDDee commented 2 years ago

Which version of cpuminer-opt are you using? If v3.18.0 try v3.17.1. It's a little slower but will tell me if I broke it or it never worked. If it never worked I'll need more details about the coin you're mining, some way to test it,and command line options. Also add -D -P for testing so I can get more debug info. It would also nice to capture the same data from TPruvot so I can compare logs.

Solo mining support is on a best effort basis. If it works with TPruvot I should be able to figure it out eventually. But I won't be able to look at it for a while, I'm working on some scrypt performance issues for v3.18.1. It will have to wait for v3.18.2.

rubenh2905 commented 2 years ago

on 3.18.0 image

JayDDee commented 2 years ago

@rubenh2905, different algo, different error message, likely a different problem. I already replied to OP that more data is required.

To both of you, without a proper problem description and supporting data I will assume user error and summarilly close this issue.

YetAnotherRussian commented 2 years ago

on 3.18.0 image

Seems to be an atempt to use json-rpc on a stratum pool. Show us your settings

JayDDee commented 2 years ago

OP hasn't responded in 5 days. No one else has reported a similar issue. I assume the problem was either solved or the issue was abandoned.

The second isssue reported by another user is unrelated..