An (even more) optimized version of cpuminer (pooler's cpuminer, CPU-only)

[bilabonic]

Where do you put this line ?

$ ./minerd --url=stratum+tcp://myminingpool.com:3333 --userpass=my.worker:password

It only has 3 .dll and the .exe files when extracted to a folder ?

Cheers

[1713432402]

1713432402

[1713432402]

1713432402

[mruk]

I have used these formulas:
  minerd - url = http://myminingpool.com:9332 - UserPass = my.worker: password. It works without a problem in p2pool

minerd - url = stratum + tcp :/ / myminingpool.com: 3333 - UserPass = my.worker: password. It does not work in the mines. I have tried here http://bel.blocksolved.com
How to configure Pooler cpuminer 2.3.2-win32?
I have a windows xp system with sp3

My file. Whip: minerd - url = stratum + tcp :/ / bel.blocksolved.com: 3333 - UserPass =: my.worker: password.

I have a message:
Stratum authentication failed
  ... retry after 30 seconds
What am I doing wrong?

I'm sorry for the mistakes, I use google translator

[pooler]

https://www.virustotal.com/ru/file/cd9fd5008246dad98e689bde42d71579125fe7759dd870239f8d43f7dd0f69de/analysis/

Q: My antivirus flags the Windows binary as malware.
A: That's a known false positive. More information here.

I have used these formulas:
  minerd - url = http://myminingpool.com:9332 - UserPass = my.worker: password. It works without a problem in p2pool

minerd - url = stratum + tcp :/ / myminingpool.com: 3333 - UserPass = my.worker: password. It does not work in the mines. I have tried here http://bel.blocksolved.com
How to configure Pooler cpuminer 2.3.2-win32?
I have a windows xp system with sp3

My file. Whip: minerd - url = stratum + tcp :/ / bel.blocksolved.com: 3333 - UserPass =: my.worker: password.

I have a message:
Stratum authentication failed
  ... retry after 30 seconds
What am I doing wrong?

I'm sorry for the mistakes, I use google translator

You didn't really use "my.worker:password" to authenticate, did you? Pools usually require you to register an account on their website and to use the credentials of one of your workers to authenticate when mining. (That is not the case with P2Pool.)
There are also syntax errors in your commands above, but I suppose those were introduced by Google Translator, otherwise minerd would have complained.

[mruk]

https://www.virustotal.com/ru/file/cd9fd5008246dad98e689bde42d71579125fe7759dd870239f8d43f7dd0f69de/analysis/

Q: My antivirus flags the Windows binary as malware.
A: That's a known false positive. More information here.

I have used these formulas:
  minerd - url = http://myminingpool.com:9332 - UserPass = my.worker: password. It works without a problem in p2pool

minerd - url = stratum + tcp :/ / myminingpool.com: 3333 - UserPass = my.worker: password. It does not work in the mines. I have tried here http://bel.blocksolved.com
How to configure Pooler cpuminer 2.3.2-win32?
I have a windows xp system with sp3

My file. Whip: minerd - url = stratum + tcp :/ / bel.blocksolved.com: 3333 - UserPass =: my.worker: password.

I have a message:
Stratum authentication failed
  ... retry after 30 seconds
What am I doing wrong?

I'm sorry for the mistakes, I use google translator

You didn't really use "my.worker:password" to authenticate, did you? Pools usually require you to register an account on their website and to use the credentials of one of your workers to authenticate when mining. (That is not the case with P2Pool.)
There are also syntax errors in your commands above, but I suppose those were introduced by Google Translator, otherwise minerd would have complained.

Of course I'm registered at the pool.
I enter my login.adres wallet: password
It worked and not before.

[Androidicus]

I have a conundrum:

I have quite a few VPS set up for CPU Mining. 8 x VPS on one well known provider on Ubuntu 13.04 (x86 64bit) builds all work like a dream with cpuminer-2.3.2 or the quark derivative.

My problem is with 2 'test' VPS on Server4You which only offer Centos 6.5, Debian 6, Ubuntu 10.04. I have had cpuminer-2.3.2 working on both on either Centos 6.5 or Ubuntu 10.04 after preparing the minimal install and following the widely available tuts on this forum etc.

Then they stopped working... I have rebuilt the VPS trying each OS in turn and while minerd will run it either won't connect or throws  'stratum_subscribe timed out' errors...

I have asked support the general question about blocked destinations and they assure me that NO destination hosts/ips/ports are blocked on the host system.

I have checked iptables -L and NO rules are set.

I have tried lots of different pools to which I subscribe and no joy. I have checked and rechecked the command line to check for silly errors but can find none.

Any thoughts please as if I can't get these 2 working again I will just have to ditch them?

[Androidicus]

Just additional info to my last question:

Binaries have the same problem. Whether built or binaries, ./minerd --benchmark runs fine and shows threads/hashrates but cannot connect to any pool.

Have used EXACT SAME command lines (copied/pasted into Putty) used on other boxes which are working to test for syntax/typos.

Grrrr...

[pmconrad]

Are other networking applications working as they should? E. g. can you download large files from remote servers using wget or curl?
Can you connect to the pools using telnet or netcat?
Have you tried using tcpdump on the stratum connections?

[Androidicus]

Hi,

wget & curl seem fine. Can't telnet to most pools but guess to be expected?

Output of -P

(worker user and pass genericised!)

Code:

[root@[VPS] cpuminer-2.3.2]# ./minerd -a scrypt -o stratum+tcp://ca1.miningpool.co:9999 -u MY.USERNAME -p MYPASSWORD -R 10 -P
[2014-01-09 14:02:01] 16 miner threads started, using 'scrypt' algorithm.
[2014-01-09 14:02:01] Starting Stratum on stratum+tcp://ca1.miningpool.co:9999
[2014-01-09 14:02:01] Binding thread 12 to cpu 12
[2014-01-09 14:02:01] Binding thread 15 to cpu 15
[2014-01-09 14:02:01] Binding thread 13 to cpu 13
[2014-01-09 14:02:01] Binding thread 5 to cpu 5
* About to connect() to ca1.miningpool.co port 9999 (#0)
*   Trying 192.99.9.229... * TCP_NODELAY set
[2014-01-09 14:02:01] Binding thread 14 to cpu 14
[2014-01-09 14:02:01] Binding thread 4 to cpu 4
[2014-01-09 14:02:01] Binding thread 11 to cpu 11
[2014-01-09 14:02:01] Binding thread 6 to cpu 6
[2014-01-09 14:02:01] Binding thread 9 to cpu 9
[2014-01-09 14:02:01] Binding thread 7 to cpu 7
[2014-01-09 14:02:01] Binding thread 10 to cpu 10
[2014-01-09 14:02:01] Binding thread 8 to cpu 8
[2014-01-09 14:02:01] Binding thread 3 to cpu 3
[2014-01-09 14:02:01] Binding thread 2 to cpu 2
[2014-01-09 14:02:01] Binding thread 0 to cpu 0
[2014-01-09 14:02:01] Binding thread 1 to cpu 1
* Timeout
* connect() timed out!
* Closing connection #0
[2014-01-09 14:02:31] Stratum connection failed: connect() timed out!
[2014-01-09 14:02:31] ...retry after 10 seconds

Other pools seems have stratum_subscribe timed out errors etc.

The exact command line above works fine on other VPS's...

[jedimstr]

Hi,

wget & curl seem fine. Can't telnet to most pools but guess to be expected?

Output of -P

(worker user and pass genericised!)

Code:

[root@[VPS] cpuminer-2.3.2]# ./minerd -a scrypt -o stratum+tcp://ca1.miningpool.co:9999 -u MY.USERNAME -p MYPASSWORD -R 10 -P
[2014-01-09 14:02:01] 16 miner threads started, using 'scrypt' algorithm.
[2014-01-09 14:02:01] Starting Stratum on stratum+tcp://ca1.miningpool.co:9999
[2014-01-09 14:02:01] Binding thread 12 to cpu 12
[2014-01-09 14:02:01] Binding thread 15 to cpu 15
[2014-01-09 14:02:01] Binding thread 13 to cpu 13
[2014-01-09 14:02:01] Binding thread 5 to cpu 5
* About to connect() to ca1.miningpool.co port 9999 (#0)
*   Trying 192.99.9.229... * TCP_NODELAY set
[2014-01-09 14:02:01] Binding thread 14 to cpu 14
[2014-01-09 14:02:01] Binding thread 4 to cpu 4
[2014-01-09 14:02:01] Binding thread 11 to cpu 11
[2014-01-09 14:02:01] Binding thread 6 to cpu 6
[2014-01-09 14:02:01] Binding thread 9 to cpu 9
[2014-01-09 14:02:01] Binding thread 7 to cpu 7
[2014-01-09 14:02:01] Binding thread 10 to cpu 10
[2014-01-09 14:02:01] Binding thread 8 to cpu 8
[2014-01-09 14:02:01] Binding thread 3 to cpu 3
[2014-01-09 14:02:01] Binding thread 2 to cpu 2
[2014-01-09 14:02:01] Binding thread 0 to cpu 0
[2014-01-09 14:02:01] Binding thread 1 to cpu 1
* Timeout
* connect() timed out!
* Closing connection #0
[2014-01-09 14:02:31] Stratum connection failed: connect() timed out!
[2014-01-09 14:02:31] ...retry after 10 seconds

Other pools seems have stratum_subscribe timed out errors etc.

The exact command line above works fine on other VPS's...

Could be an upstream proxy/firewall on that VPS instance blocking ports.  Have you tried trace route to the various pools to see where the droppoff is?  It may not even be on the immediate service side, and instead further upstream to the backbone.

[Androidicus]

Seems to get across the pond:

Code:

[root@euve33599 cpuminer-2.3.2]# traceroute ca1.miningpool.co
traceroute to ca1.miningpool.co (192.99.9.229), 30 hops max, 60 byte packets
 1  static-ip-85-25-32-149.inaddr.ip-pool.com (85.25.32.149)  0.032 ms  0.010 ms  0.009 ms
 2  149.14.12.37 (149.14.12.37)  0.357 ms 149.14.12.17 (149.14.12.17)  0.415 ms 149.14.12.13 (149.14.12.13)  0.480 ms
 3  te2-6.ccr01.sxb01.atlas.cogentco.com (154.54.74.245)  0.490 ms te4-8.ccr01.sxb01.atlas.cogentco.com (154.54.62.201)  0.587 ms  0.601 ms
 4  te0-7-0-9.mpd22.fra03.atlas.cogentco.com (154.54.75.17)  3.892 ms te0-7-0-15.ccr21.fra03.atlas.cogentco.com (154.54.62.169)  3.919 ms te0-7-0-27.ccr22.fra03.atlas.cogentco.com (154.54.75.9)  23.630 ms
 5  be2009.mag21.fra03.atlas.cogentco.com (154.54.74.146)  4.089 ms be2028.mag21.fra03.atlas.cogentco.com (154.54.74.138)  3.963 ms be2009.mag21.fra03.atlas.cogentco.com (154.54.74.146)  4.294 ms
 6  tata.fra03.atlas.cogentco.com (130.117.15.146)  4.216 ms tata.fra03.atlas.cogentco.com (130.117.15.150)  4.099 ms  4.083 ms
 7  if-6-2.thar1.F2C-Frankfurt.as6453.net (195.219.50.174)  4.457 ms if-9-2.tcore1.FNM-Frankfurt.as6453.net (195.219.50.42)  4.388 ms if-7-2.tcore1.FNM-Frankfurt.as6453.net (195.219.50.2)  4.247 ms
 8  if-2-2.thar1.F2C-Frankfurt.as6453.net (195.219.156.130)  4.463 ms  4.522 ms  4.560 ms
 9  * * fra-5-6k.fr.eu (213.251.130.105)  3.670 ms
10  * * fra-5-6k.fr.eu (213.251.130.105)  3.735 ms
11  rbx-g2-a9.fr.eu (91.121.131.130)  11.859 ms  11.799 ms rbx-g1-a9.fr.eu (91.121.131.197)  11.751 ms
12  * * ldn-1-6.uk.eu (213.251.130.74)  14.937 ms
13  bhs-g2-6k.qc.ca (198.27.73.207)  92.480 ms * *
14  bhs-g1-6k.qc.ca (198.27.73.205)  91.243 ms bhs-g2-6k.qc.ca (198.27.73.207)  92.462 ms bhs-4a-6k.qc.ca (198.27.73.222)  90.564 ms
15  * bhs-4b-6k.qc.ca (198.27.73.228)  109.397 ms *
16  * * *
17  * * *

I'm somewhat rusty with linux etc. - having to remember stuff I used to do 15+ years ago!

[jedimstr]

Seems to get across the pond:

Code:

[root@euve33599 cpuminer-2.3.2]# traceroute ca1.miningpool.co
traceroute to ca1.miningpool.co (192.99.9.229), 30 hops max, 60 byte packets
 1  static-ip-85-25-32-149.inaddr.ip-pool.com (85.25.32.149)  0.032 ms  0.010 ms  0.009 ms
 2  149.14.12.37 (149.14.12.37)  0.357 ms 149.14.12.17 (149.14.12.17)  0.415 ms 149.14.12.13 (149.14.12.13)  0.480 ms
 3  te2-6.ccr01.sxb01.atlas.cogentco.com (154.54.74.245)  0.490 ms te4-8.ccr01.sxb01.atlas.cogentco.com (154.54.62.201)  0.587 ms  0.601 ms
 4  te0-7-0-9.mpd22.fra03.atlas.cogentco.com (154.54.75.17)  3.892 ms te0-7-0-15.ccr21.fra03.atlas.cogentco.com (154.54.62.169)  3.919 ms te0-7-0-27.ccr22.fra03.atlas.cogentco.com (154.54.75.9)  23.630 ms
 5  be2009.mag21.fra03.atlas.cogentco.com (154.54.74.146)  4.089 ms be2028.mag21.fra03.atlas.cogentco.com (154.54.74.138)  3.963 ms be2009.mag21.fra03.atlas.cogentco.com (154.54.74.146)  4.294 ms
 6  tata.fra03.atlas.cogentco.com (130.117.15.146)  4.216 ms tata.fra03.atlas.cogentco.com (130.117.15.150)  4.099 ms  4.083 ms
 7  if-6-2.thar1.F2C-Frankfurt.as6453.net (195.219.50.174)  4.457 ms if-9-2.tcore1.FNM-Frankfurt.as6453.net (195.219.50.42)  4.388 ms if-7-2.tcore1.FNM-Frankfurt.as6453.net (195.219.50.2)  4.247 ms
 8  if-2-2.thar1.F2C-Frankfurt.as6453.net (195.219.156.130)  4.463 ms  4.522 ms  4.560 ms
 9  * * fra-5-6k.fr.eu (213.251.130.105)  3.670 ms
10  * * fra-5-6k.fr.eu (213.251.130.105)  3.735 ms
11  rbx-g2-a9.fr.eu (91.121.131.130)  11.859 ms  11.799 ms rbx-g1-a9.fr.eu (91.121.131.197)  11.751 ms
12  * * ldn-1-6.uk.eu (213.251.130.74)  14.937 ms
13  bhs-g2-6k.qc.ca (198.27.73.207)  92.480 ms * *
14  bhs-g1-6k.qc.ca (198.27.73.205)  91.243 ms bhs-g2-6k.qc.ca (198.27.73.207)  92.462 ms bhs-4a-6k.qc.ca (198.27.73.222)  90.564 ms
15  * bhs-4b-6k.qc.ca (198.27.73.228)  109.397 ms *
16  * * *
17  * * *

I'm somewhat rusty with linux etc. - having to remember stuff I used to do 15+ years ago!

What do your direct pings look like to the pool?

[atchoum6760]

Hi !
It's possible using zipzap.

THK

[Androidicus]

jedimstr:

Right, ping to ca1.miningpool.com from my location/network responds fine with 129ms avg round trip.

Ping from VPS (in Putty) - hangs but reports on kill that 200 pkts sent 0 rcvd and the time it ran for...

So, in spite of S4Y support saying that nothing is blocked and I agree with what you say about potential upstream closed doors, access to mining pool hosts/ips seem to be killed or blocked.

Pinging google.co.uk works fine from the VPS...

I can understand hosting provider wanting to kill/block CPU intensive processes but can't see how they keep on top of all the mining pool hosts/ips unless they they are sniffing the line and blocking ips based upon traffic type/protocol?

I'm wondering if I can use one of my other VPS hosts as a proxy to route these misbehaving VPS through? The ip traffic is minimal so shouldn't affect the VPS running the proxy?

Brainache!   

[aliceross222]

cgminer is still the best miner available today

[paulus51]

yep it is the best CPU miner ! top i hope there wil be a even faster then this fast cpu miner so tune it more pooler ! great job !

[pluto34]

the best ! just wanted to say thanks 

[Gazza1]

Has anyone tried the AVX2 version of this?  Is it faster than using AVX1?

[pooler]

Has anyone tried the AVX2 version of this?  Is it faster than using AVX1?

There is no "AVX2 version". There is only one binary which includes implementations for various microarchitectures and instruction sets. If the CPU and the OS both support AVX2, then the miner automatically takes advantage of AVX2 (as long as you're not using some old version of it, of course).
If you compare a Haswell core with a Sandy Bridge or Ivy Bridge core running at the same clock frequency, the former can mine almost twice as fast as the latter.

[01835113]

Hello. My pc is mining a new coin (aliencoin) with 0.16 - 0.18 of difficult to 1500-1900 hases per second, for the last 12 hours and it found nothing. It is mining in solo mode. is this normal?

[Gazza1]

Has anyone tried the AVX2 version of this?  Is it faster than using AVX1?

There is no "AVX2 version". There is only one binary which includes implementations for various microarchitectures and instruction sets. If the CPU and the OS both support AVX2, then the miner automatically takes advantage of AVX2 (as long as you're not using some old version of it, of course).
If you compare a Haswell core with a Sandy Bridge or Ivy Bridge core running at the same clock frequency, the former can mine almost twice as fast as the latter.

Very good to know thanks man