damn, thanks for looking into it though, most profitable coins for cpu mining are either cryptonight or zoin/zcoin or something else/new
Did you try ccminer-tpruvot? It's coded differently and doesn't have the rpc2-login call in workio_thread. just tried, it issues the following rpc method: [2017-03-20 16:17:33] JSON protocol request:
{"method":"getwork","params":[],"id":0} which results in [2017-03-20 16:17:34] JSON decode failed(1): '[' or '{' expected near 'Requested'
[2017-03-20 16:17:34] Requested url is not found
[2017-03-20 16:17:34] get_work failed, retry after 30 secondsseems ccminer is not compatible with solo mining as else it has to request the getblocktemplate method (?) |
|
|
|
They have been working on that miner for like 2-3 years  . My favorite part about the pictures is that the circuit boards do not have circuits -- lol its a rendering, no actual image  |
|
|
|
Same bugs there, zcoin, zcoinc, but you could try gbt since the miner is now fixed.
i have done so, didnt work out sadly |
|
|
|
with the workio_login thing commented out i get: [2017-03-18 23:28:23] 1 miner threads started, using 'cryptonight' algorithm.
[2017-03-18 23:28:23] Tried to call rpc2 command before authentication
[2017-03-18 23:28:23] getblocktemplate failed, falling back to getwork
[2017-03-18 23:28:23] Tried to call rpc2 command before authentication
[2017-03-18 23:28:23] json_rpc_call failed, retry after 10 seconds
i then commented out line 242 and got the same output as above i then uncommented the workio_login thingy and it went back to the initial output posted before rpc2_workio_login is called regardless of gbt or not. The login method isn't recongnized and skipping it results in no authentication. With no working model and no real understanding of the protocol I think I'm stuck. damn, thanks for looking into it though, most profitable coins for cpu mining are either cryptonight or zoin/zcoin or something else/new as a matter of fact i also tested zcoinclassic over this night but it seems their wallet contains the same bug hexxdev encountered in the imported changes from zcoin which my old wallet hadnt had: zcoin classics avg ttf is 0.6h with my hashrate but no block found over the last 7h, might be the same for zcoin itself (not tested) |
|
|
|
Yeah, no login method, but I don't think it's GBT related. I found an intereting bit of code cpu-miner.c line 1264 if(jsonrpc_2 && !have_stratum)
ok = rpc2_workio_login(curl);
while (ok)
{
Notice no "else" clause so no login attempt here for other algos. You could try commenting out the login to see what happens. I also looked at GBT code. I'm not sure now why I defaulted to disable GBT for RPC2. cpuminer-multi doesn't do it. You could try commenting that out in ago-gate-api.c line 242. I don't really expect either of these to fix it but it might eliminate some of the noise. with the workio_login thing commented out i get: [2017-03-18 23:28:23] 1 miner threads started, using 'cryptonight' algorithm.
[2017-03-18 23:28:23] Tried to call rpc2 command before authentication
[2017-03-18 23:28:23] getblocktemplate failed, falling back to getwork
[2017-03-18 23:28:23] Tried to call rpc2 command before authentication
[2017-03-18 23:28:23] json_rpc_call failed, retry after 10 seconds
i then commented out line 242 and got the same output as above i then uncommented the workio_login thingy and it went back to the initial output posted before |
|
|
|
Looks like a problem with longpoll, try --no-longpoll.
edit: also try cpuminer-multi, if it works I can compare.
i have executed it with the --no-longpoll option, same error it seems, also tested with cpuminer-multi with and without --no-longpoll, same result: felix@mobile:~/local projects/cpuminer-multi$ ./cpuminer -a cryptonight -t 3 -o http://10.1.1.173:41264 -DP --no-longpoll
** cpuminer-multi 1.3.1 by tpruvot@github **
BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd (tpruvot)
[2017-03-18 22:06:50] Using JSON-RPC 2.0
[2017-03-18 22:06:50] CPU Supports AES-NI: YES
[2017-03-18 22:06:50] JSON protocol request:
{"method": "login", "params": {"login": "", "pass": "", "agent": "cpuminer-multi/1.3.1"}, "id": 1}
* Rebuilt URL to: http://10.1.1.173:41264/
* Trying 10.1.1.173...
* TCP_NODELAY set
[2017-03-18 22:06:50] Binding thread 0 to cpu 0 (mask 1)
[2017-03-18 22:06:50] Binding thread 1 to cpu 1 (mask 2)
[2017-03-18 22:06:50] 3 miner threads started, using 'cryptonight' algorithm.
[2017-03-18 22:06:50] Binding thread 2 to cpu 2 (mask 4)
* Connected to 10.1.1.173 (10.1.1.173) port 41264 (#0)
* Server auth using Basic with user ''
> POST / HTTP/1.1
Host: 10.1.1.173:41264
Authorization: Basic Og==
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 98
User-Agent: cpuminer-multi/1.3.1
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue
* Done waiting for 100-continue
< HTTP/1.1 200 OK
< Content-Length: 77
< Server: CryptoNote-based HTTP server
<
* Connection #0 to host 10.1.1.173 left intact
[2017-03-18 22:06:51] JSON protocol response:
{
"error": {
"code": -32601,
"message": "Method not found"
},
"id": 1,
"jsonrpc": "2.0"
}
[2017-03-18 22:06:51] JSON-RPC call failed: Method not found
[2017-03-18 22:06:51] ...retry after 10 seconds
^C[2017-03-18 22:06:54] SIGINT received, exiting
i have tested this with the wallet rpc port, with the daemon rpc port i get: felix@mobile:~/local projects/cpuminer-multi$ ./cpuminer -a cryptonight -t 3 -o http://10.1.1.173:41263 -DP --no-longpoll
** cpuminer-multi 1.3.1 by tpruvot@github **
BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd (tpruvot)
[2017-03-18 22:20:39] Using JSON-RPC 2.0
[2017-03-18 22:20:39] CPU Supports AES-NI: YES
[2017-03-18 22:20:39] JSON protocol request:
{"method": "login", "params": {"login": "", "pass": "", "agent": "cpuminer-multi/1.3.1"}, "id": 1}
* Rebuilt URL to: http://10.1.1.173:41263/
* Trying 10.1.1.173...
* TCP_NODELAY set
[2017-03-18 22:20:39] Binding thread 0 to cpu 0 (mask 1)
[2017-03-18 22:20:39] 3 miner threads started, using 'cryptonight' algorithm.
[2017-03-18 22:20:39] Binding thread 1 to cpu 1 (mask 2)
[2017-03-18 22:20:39] Binding thread 2 to cpu 2 (mask 4)
* Connected to 10.1.1.173 (10.1.1.173) port 41263 (#0)
* Server auth using Basic with user ''
> POST / HTTP/1.1
Host: 10.1.1.173:41263
Authorization: Basic Og==
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 98
User-Agent: cpuminer-multi/1.3.1
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue
* Done waiting for 100-continue
< HTTP/1.1 404 Not Found
< Content-Length: 27
< Server: CryptoNote-based HTTP server
* HTTP error before end of send, stop sending
<
* Closing connection 0
[2017-03-18 22:20:40] JSON decode failed(1): '[' or '{' expected near 'Requested'
[2017-03-18 22:20:40] ...retry after 10 seconds
^C[2017-03-18 22:20:41] SIGINT received, exiting
to me it seems the rpc request method is "login" but this only works for pools afaik one needs to connect to the daemon and use getblocktemplate? atleast for the wallet there is no mining related method ( https://getmonero.org/knowledge-base/developer-guides/wallet-rpc) whereas the daemon rpc has a getblocktemplate method ( https://getmonero.org/knowledge-base/developer-guides/daemon-rpc) no matter which features is disable it always uses "login" method it seems (no-stratum, no-getwork, etc) edit: after taking a look at this ( https://github.com/sammy007/monero-stratum/blob/master/go-pool/rpc/rpc.go), im pretty sure for solo mining to work cpuminer(-opt) needs the getblocktemplate support for cryptonight coins integrated first |
|
|
|
What one needs to do is thus adding this new communications protocol to the miner and adjust it accordingly. This way the miner can solo mine this and similar coins without problem.
Thanks but the code already exists in the miner, it just hasn't been tested since I forked it. i get the following: felix@mobile:~/local projects/WebstormProjects/wallet-miner-agent$ bin/cpuminer -a cryptonight -t 3 -o http://10.1.1.173:41264 -DP
********** cpuminer-opt 3.6.0 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
Forked from TPruvot's cpuminer-multi with credits
to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
Wolf0, Jeff Garzik and Optiminer.
CPU: Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
CPU features: SSE2 AES AVX AVX2
SW built on Mar 16 2017 with GCC 5.4.0
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES
[2017-03-18 17:40:53] JSON protocol request:
{"method": "login", "params": {"login": "", "pass": "", "agent": "cpuminer-opt/3.6.0"}, "id": 1}
* Rebuilt URL to: http://10.1.1.173:41264/
* Trying 10.1.1.173...
* TCP_NODELAY set
[2017-03-18 17:40:53] Binding thread 0 to cpu 0 (mask 1)
[2017-03-18 17:40:53] Binding thread 1 to cpu 1 (mask 2)
[2017-03-18 17:40:53] 3 miner threads started, using 'cryptonight' algorithm.
[2017-03-18 17:40:53] Binding thread 2 to cpu 2 (mask 4)
* Connected to 10.1.1.173 (10.1.1.173) port 41264 (#0)
* Server auth using Basic with user ''
> POST / HTTP/1.1
Host: 10.1.1.173:41264
Authorization: Basic Og==
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 96
User-Agent: cpuminer-opt/3.6.0
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue
* Done waiting for 100-continue
< HTTP/1.1 200 OK
< Content-Length: 77
< Server: CryptoNote-based HTTP server
<
* Connection #0 to host 10.1.1.173 left intact
[2017-03-18 17:40:54] JSON protocol response:
{
"error": {
"code": -32601,
"message": "Method not found"
},
"id": 1,
"jsonrpc": "2.0"
}
[2017-03-18 17:40:54] JSON-RPC call failed: Method not found
[2017-03-18 17:40:54] ...retry after 10 seconds
^C[2017-03-18 17:40:58] SIGINT received, exiting
|
|
|
|
|
thanks for the feedback/options, will "measure" temps with my fingers and see if it gets hot, but the new psu will not arrive/get ordered till later this year as it is getting hotter in my country and my gpu rigs are not running till winter
|
|
|
|
@ Felix
-u mustmatch coin conf
-p as in coin conf too
one of the benefits is with coinbase adr, you dont need to have the wallet started (usually)
try this pls and report us if it works for you
for me i have done so some time ago and it has worked
Cryptonight uses a different version of RPC and doesn't support GBT. Coinbase addr is not used for getwork. i will try to test getwork later today, will report findings |
|
|
|
@ Felix
-u mustmatch coin conf
-p as in coin conf too
one of the benefits is with coinbase adr, you dont need to have the wallet started (usually)
try this pls and report us if it works for you
for me i have done so some time ago and it has worked
i see, i think this only applies to non cryptonight algos, as joblo pointed out below they dont use coinbase-addr |
|
|
|
No one has reported it not working. ah yes, i assumed it doesnt work anything different as with "normal" coins like hexx? my cmdline would look like this (blockchain still syncing): cpuminer -a cryptonight -t 3 --coinbase-addr=<ADDR> -o http://localhost:RPC_PORT -u ?? -p ?? not sure about the username and pass param, will see if needed and/or how to set in coin config |
|
|
|
Also gcc 5.4 tested, OK!
These guys are trolling you.
Why waste the time.. It is history.
This is 2017
Even the centos is just as dead as dead can be. But original redhat.. Like from museum.
It is like asking to compile it on commodore 16.
Ok, my nintedo is faster..
everybody with compile problems and running linux can use docker btw, this approach is clean and neat |
|
|
|
anybody knows some coins which can still be solomined (besides hexxcoin)? i want to test cpuminer-opt getwork/gbt support as well as my wrapper  |
|
|
|
What was your wallet version? It is possible if you had older it will work. Else i just cannot tell how it is possible. wallet is 3.0.0.8, will test latest version later and confirm still working |
|
|
|
HexxCoin supports old format: rpcallow=192.168.0.* Getwork fixed. Solomining with cpuminer-opt 3.6.0 will be possible. Source updated, new wallets soon. I will be back with my original hexxodev nick. thanks, will test soon i successfully mined a block with 3.5.13 modified (as per the instructions in the cpuminer-opt thread), what part of getwork was broken? i used the default hexx windows wallet, no modifications |
|
|
|
Getwork doesn't work, yet, wait for 3.6.0.
i have tested with the modifications mentioned, it works! regarding cryptonight/cryptolight: if i understood correctly their getwork and/or gbt code is nonexistent and/or different, so coins utilizing this algo might very likely not work with solo mining? Did you get the wallet fixes? Cryptonight doesn't support gbt and the miner will automatically disable it. In addition the getwork code, all the rpc code, is different from all other algos, so you presumption is correct. It is my hope that any other coin that supports getwork should now work. i was using the standard hexx wallet, no modifications will test some other coins when i find some where the nethash is low and the wallet doesnt take forever to sync |
|
|
|
That's excellent news. It's looking like the miner side is working and it's just a wallet issue now.
That means it should work with almost any coin who's wallet already supports getwork.
Keep me updated on your progress. The next release will be 3.6.0 with getwork support.
i have thought about writing a small tool to setup multiple wallets and only mine when nethashrate is below a certain limit this is intended for me walking through the ann section, finding a new coin with no pools which just launched, setting it up in the tool and boom, miner starts working there till there are enough other people so its unlikely to be profitable awesomeminer might be able to do that already im not sure, but i want it to be able to run on linux as well will see if this project is possible in a short timeframe and if mining even works, so im glad getwork/gbt is being worked on  edit: im interested in testing as well, i have noticed the api hashrate isnt updated when using getwork it seems, it always returns 0 Getwork doesn't work, yet, wait for 3.6.0. i have tested with the modifications mentioned, it works! hashrate gets displayed via api after some time (i just went shopping and returned to block found and api working)    until 3.6.0 is released i will continue testing with this modified version, maybe i find some bugs when using other wallets/coins regarding cryptonight/cryptolight: if i understood correctly their getwork and/or gbt code is nonexistent and/or different, so coins utilizing this algo might very likely not work with solo mining? edit: the hashrate api bug is no bug, i just noticed its the same with stratum, only after the first submitted share the api hashrate gets updated, with getwork and solomining that can take a while, maybe the api hashrate can be updated even when no shares got submitted yet? |
|
|
|
|
Show Posts
