Topic: LTC - Minerd - cointron (no accepted/yay's) (Read 3368 times)
Did you solve this? What was the problem?
Windows 7 64bit CPU mining.
Cointron LTC mining
I've been using minerd.exe and mining_proxy.exe with the following commands on my main system and it works with no problem:
c:\ltcminer\mining_proxy -pa scrypt -o coinotron.com -p 3334
c:\ltcminer\minerd -a scrypt -r 1 -t 2 -s 6 -o http://127.0.0.1:8332 -O (my user name).1:1
(my user name - what i registered with but not shown).
I've recently diverted work to the laptops and freed up the main system for BTC mining. On my laptops I'm not always getting the results I want. (using different workers btw)
For the first couple of times it shows the following: accepted 1/1 (100%) then 2/2; 3/3 up till about 4/4. At that point, it starts showing this: JSON-RPC call failed: {"message": "Unexpected error during authorization", "code": -1 json_rpc_call failed , retry after 30 seconds
After that, it begins to hash again and shows LONGPOLL detected new block, but the have stopped appearing and the cointron dashboard shows the work has stopped (0kh/s).
What do you suppose causes this? Tried looking around, those who had similar issues were using 3333 port instead of 3334, but I'm definitely using 3334, plus I was getting working results for the first couple of runs, then it craps out and the work comes to a halt.
Cointron LTC mining
I've been using minerd.exe and mining_proxy.exe with the following commands on my main system and it works with no problem:
c:\ltcminer\mining_proxy -pa scrypt -o coinotron.com -p 3334
c:\ltcminer\minerd -a scrypt -r 1 -t 2 -s 6 -o http://127.0.0.1:8332 -O (my user name).1:1
(my user name - what i registered with but not shown).
I've recently diverted work to the laptops and freed up the main system for BTC mining. On my laptops I'm not always getting the results I want. (using different workers btw)
For the first couple of times it shows the following: accepted 1/1 (100%)
After that, it begins to hash again and shows LONGPOLL detected new block, but the
What do you suppose causes this? Tried looking around, those who had similar issues were using 3333 port instead of 3334, but I'm definitely using 3334, plus I was getting working results for the first couple of runs, then it craps out and the work comes to a halt.
Jump to: