[ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9

[shakes1118]

Code:

user@testmachine:/root/bminer-v5.3.0-e337b9a$ netstat -ntlp|grep bminer
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp6       0      0 :::1880                 :::*                    LISTEN      8775/bminer

Code:

user@testmachine:/root/bminer-v5.3.0-e337b9a$ lsof -nP -i|grep bminer|grep 1880
COMMAND  PID  USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
bgminer 8775 miner  231u  IPv6 354336      0t0  TCP *:1880 (LISTEN)

Hey realbminer,

I believe there is a minor bug in bminer.
It seems when running under linux with IPv4 and IPv6 installed, the API starts only on IPv6.
This seems to occur when the '-api' parameter is set to '-api 0.0.0.0:1880'.
This rig was freshly installed with a minimal version of ubuntu 16.04.3.
I've also experienced the same issue on other versions of linux including CentOS.

I CAN access it via IPv6, however, the availability of IPv6 on some other machines is limited in my environment AND, going forward there are some API connections I'd like to use that would need IPv4 compatibility.


Before anyone starts in on me about opening the API access, I require access to the API on the local network. It's well protected.

Oh, I also have a request: Please add the device name for each device on the default API webpage. When there are multiple types of GPUs it can be difficult to tell what type each is. Especially with many rigs.

Thank you for your time and work.

[1713914822]

1713914822

[1713914822]

1713914822

[1713914822]

1713914822

[1713914822]

1713914822

[d0n4ald]

so does ---nofee work in bminer? or does a cut still go to the dev?

should i switch to dstm? and is its 2% fee non removable?

[jperser]

After readings 41 pages of posts, I have decide to not use bminer and go back to dstm 0.5.8 for the following reasons:

1. The management API does not include pool information.  I change pools from time to time based on profit/difficulty.  I have a app that monitors the management API and reminds me which coin I am mining.  Every other mining software I have encountered includes this.  Not knowing what coin I am mining is a deal breaker.

2. There is a private connection to bmine every 10-15 minutes.  Too often, unknown, closed source.  This a major security risk for me.  I could spent the time to hack into this.  But there is not point until #1 is addressed.

3. The actual hashrate is in question.  The tests so far all have some minor flaws to be conclusive.  I not blaming the person doing the test.  It just doesn't hold up to statistical rigor.  I could devise and run a test that will provide evident supporting my claims (including margin of error), but no point for me until #1 is addressed.

4. 2% devfee seems high.  A 1% to 1.5% would be more enticing.  But if I was inclined to investigate #2, I would also do a man-in-the-middle attack and redirect the devfee to my wallet  .  I have no interest in doing this.  But there is a difference between supporting the devs and being raped by them.

5. To many newbies posting here (including myself) makes it fell like a scam.  Hey, Spiralx, what do you call a person who buys a 7x1070 Ti and a 6x1060 (3gb) rig, never posts anything about "what to mine?", "what software to use?", "how to make a wallet work?", no support questions, no opinions about coins/hardware, an instant expert on his large hardware investment, then makes only 2 posts?  Oh yeah, both posts are praising biminer?

[ivdezine]

I just switched over to it but 2 things I'm noticing. 1) even though I put in the slushpool stratum server URL in the miner.bat file, when it starts it immediately connects to "zec-eu1.nanopool.org:6666" and 2) my rate monitoring on slushpool is not changing at all.

I realize there's a dev fee baked in, but how long does that mine actively for the dev and when will it actually start mining to my pool/wallet settings?

Here's the connection line from the beginning of the logfile:
[INFO] [2018-02-11T22:34:42-05:00] Connected to zec-eu1.nanopool.org:6666

My config (with address removed):
SET ADDRESS=MYZCASHADDRESS

SET USERNAME=%ADDRESS%.w

SET POOL=sec.slushpool.com:4444

SET SCHEME=stratum

START "Bminer: When Crypto-mining Made Fast" bminer.exe -uri %SCHEME%://%USERNAME%@%POOL% -api 127.0.0.1:1880 -logfile

any help/info would be appreciated.

And yes, I did google for this but didn't find much...

[johntey]

Hello,

How to get the previous version? 5.3.0 always crash on my machine.

Thanks for advance.

[cryptoyes]

After some testing, I can confirm that bminer is definitely computing more invalid solutions than ewbf and dstm. These are not stales, but actually invalid:

Code:

[WARN] [2018-02-12T09:53:27+02:00] Rejected share #49 ([20,"invalid solution"])

I get stales too:

Code:

[WARN] [2018-02-12T09:53:45+02:00] Rejected share #42 ([21,"job not found"])

[cryptoyes]

I'm also getting these too often:

Code:

[WARN] [2018-02-12T10:04:44+02:00] Get error: End of file, resetting in 5 seconds

I don't get it for all my miners, but most of them are getting it at some point ... what exactly does that mean?

... and then there's this, again, pretty often:

Code:

[FATA] [2018-02-12T10:05:49+02:00] Irrecoverable errors from watchdog: Client hasn't received Accepted Shares for 5 minutes

[ltc_bilic]

@realbminer

Today there was a problem with the zenmine.pro mining pool,...don't know what was up but after investigating I've found out that bminer still has some sort of connection problems...see the picture below,...all this time the GPU was at full load,...although it didn't had a proper connection to the pool and I couldn't see it on the minning pool. Then I've switched to ewbf/dstm, both miners connected immediately and are working properly?

I use following in a batch file:

Code:

-max-temperature 80 -max-network-failures 5 -gpucheck 0 -watchdog=false

...

This is a huge issue! I've lost at least half of the hashrate because of this bug.

Why are you using 'max-network-failures 5' & 'watchdog=false'? Shouldn't you leave it at the default so it will continue to try to recover the connection, especially if you are complaining of a bug saying it's not connecting?

The documentation on bminer.me states:

-max-network-failures   Default: -1   Description: Number of consecutive attempts that Bminer tries to recover from network failures. Set to -1 to keep on recovering.
-watchdog                           Default: true   Description: Automatic restart to recover from hung GPUs. Bminer exits itself in case of errors if watchdog is disabled.

I've already tested this, you can read it in message if you read it properly unfortunately it still doesn't work. I have to use watchdog=false because on systems with 8+ gpus you cannot run this miner properly, because the cpu usage in the beginning is too high - first 2-4 min that the miner needs to initialize it self to max speed,...then the cpu lowers to normal state 40-60% on low cost G3930. I've reported this bug already and few others too.

Now what's even more bizarre regarding this connectivity issue:
- yesterday: half of the mining farm was still working with bminer properly, the other half still had connection issues, so i switched back to ewbf with problematic rigs
- today: even the other half couldn't connect,...so switching back to ewbf/dstm permanently until this issue is properly addressed.

[MagicSmoker]

To anyone still mining on zenmine.pro, you are getting scammed (that 0% fee is fooling a lot of people) ... https://bitcointalk.org/index.php?topic=2750121

Interesting... I had more or less the same experience with vast underpayment with them, too, despite them finding blocks fairly consistently. I've learned to not trust any pool that doesn't charge a fee.

About 20 minutes ago I pointed a rig at http://zhash.pro/ to try them out. Although you have convinced me to mine some ZEC at Flypool - which has, indeed, proven to be very trustworthy - I still want to mainly mine ZEN. Hopefully Zcash.pro doesn't disappoint.

About 12 hours into my informal evaluation of zhash.pro and both the first payout rolled in as predicted while average hashrate reported at the pool - with difficulty fixed at 8192 - has remained steady at about 1860 Sols/s. So far, so good, then. Ping time isn't the lowest for me - 137ms average - but doesn't seem to be an issue with the difficulty vs. hashrate I am running.

[cryptoyes]

I've already tested this, you can read it in message if you read it properly unfortunately it still doesn't work. I have to use watchdog=false because on systems with 8+ gpus you cannot run this miner properly, because the cpu usage in the beginning is too high - first 2-4 min that the miner needs to initialize it self to max speed,...then the cpu lowers to normal state 40-60% on low cost G3930. I've reported this bug already and few others too.

What you're experiencing is the (bad) nvidia driver allocating GPUs. That's not bminer's fault (you can start any gpu app and you'll see the same). That delay is particularly long in Linux, but I don't believe you when you say it's 2-4 minutes. I use G3930 systems too and the delay is 80-90 seconds with 13 GPUs.

Your other connectivity issues can't be the miner's fault. The pool or your own connection happened to have issues.

Regarding the other posts: I'm still a amused by the trust people put in tests done with a single card ...

I don't defend bminer - the developer is way too shady, sorry (see here) - but some things are unrelated and can be explained.

[realbminer]

5.4.0 has released.

• Fix a reconnection issue in the network layer.
• Show additional statistics in console.
• Allow cross-domain requests to access the API.
• Fix the compatibility issue with docker.
• Introduce the option -share-check to make the time of recovering from no accepted shares configurable.

Happy mining!

[xyburcoin]

5.4.0 has released.

• Show additional statistics in console.
• Allow cross-domain requests to access the API.
• Fix the compatibility issue with docker.
• Introduce the option -shareCheck to make the time of recovering from no accepted shares configurable.

Happy mining!

Thanks

[cryptoyes]

Ok, this is fu**ing ridiculous ... you need to remove that shady private connection to your website:

Code:

[WARN] [2018-02-13T05:13:02Z] Failed to read from the network: Get : dial tcp: lookup api.bminer.me on 192.168.1.1:53: read udp 192.168.1.22:42393->192.168.1.1:53: i/o timeout

Your server went down and the miner stopped mining. This is seriously not cool. Besides being shady AF, you are also costing us money. My miners just wasted 1h ...

Find a way to remove this shady and ridiculous private connection. Otherwise, EVERYONE SHOULD STAY AWAY FROM THIS MINER! Your rigs can go down whenever @realbminer wishes, or when his server goes down, etc.

// Yes, my internet connection was solid when this was happening.

[Spiralx]

5. To many newbies posting here (including myself) makes it fell like a scam.  Hey, Spiralx, what do you call a person who buys a 7x1070 Ti and a 6x1060 (3gb) rig, never posts anything about "what to mine?", "what software to use?", "how to make a wallet work?", no support questions, no opinions about coins/hardware, an instant expert on his large hardware investment, then makes only 2 posts?  Oh yeah, both posts are praising biminer?

I don't need to post dumb questions on this forum because I use reddit and I did my own research before making mining rigs when I built them months ago. It's also wrong to say both my posts are praising Bminer, my first post was simply asking for Acrefawn to add bminer support to his watchdog script and thanking him for being responsive when I donated for the premium version. Laughable assumption to think this forum is the only source of information and nobody can own mining rigs without asking stupid questions here.

I did however end up switching back to DSTM for now though since I decided an extra 1-2% hash rate isn't really worth the risks of using a somewhat shady miner.

[Andrey09]

5.4.0 has released.

• Fix a reconnection issue in the network layer.
• Show additional statistics in console.
• Allow cross-domain requests to access the API.
• Fix the compatibility issue with docker.
• Introduce the option -share-check to make the time of recovering from no accepted shares configurable.

Happy mining!

Tnx.

Need additional statistics in console :

-------------------------------------------------------------------------------- (Strings)
[Info] Total: xxx Sol/s xxx N/s Avr.speed: xxx Sol/s Share A/R x/x Uptime: xxx d:h:m    (A/R means Accept/Reject)
-------------------------------------------------------------------------------- (Strings)

Need additional statistics in api browser what card caused reject share. Accept/Reject card by card.

[Scorpio777]

5.4.0 has released.

• Fix a reconnection issue in the network layer.
• Show additional statistics in console.
• Allow cross-domain requests to access the API.
• Fix the compatibility issue with docker.
• Introduce the option -share-check to make the time of recovering from no accepted shares configurable.

Happy mining!

Tnx.

Need additional statistics in console :

-------------------------------------------------------------------------------- (Strings)
[Info] Total: xxx Sol/s xxx N/s Avr.speed: xxx Sol/s Uptime: xxx d:h:m
-------------------------------------------------------------------------------- (Strings)

Agree. And thanks realbminer for nice update

[unique83]

Ok, this is fu**ing ridiculous ... you need to remove that shady private connection to your website:

Code:

[WARN] [2018-02-13T05:13:02Z] Failed to read from the network: Get : dial tcp: lookup api.bminer.me on 192.168.1.1:53: read udp 192.168.1.22:42393->192.168.1.1:53: i/o timeout

Your server went down and the miner stopped mining. This is seriously not cool. Besides being shady AF, you are also costing us money. My miners just wasted 1h ...

Find a way to remove this shady and ridiculous private connection. Otherwise, EVERYONE SHOULD STAY AWAY FROM THIS MINER! Your rigs can go down whenever @realbminer wishes, or when his server goes down, etc.

// Yes, my internet connection was solid when this was happening.

Dude are you fucking retarded or what? You keep pissing on BMiner, yet you are still using it. There is something seriously wrong with you. If you dont like it GTFO and use some other miner and stop being such an asshole.

[LaserBadger]

Using this miner

How much hash/sol would a 1080Ti give in comparison to a rx580/590 ?

[MagicSmoker]

Find a way to remove this shady and ridiculous private connection. Otherwise, EVERYONE SHOULD STAY AWAY FROM THIS MINER! Your rigs can go down whenever @realbminer wishes, or when his server goes down, etc.
...

Dude are you fucking retarded or what? You keep pissing on BMiner, yet you are still using it. There is something seriously wrong with you. If you dont like it GTFO and use some other miner and stop being such an asshole.

Whoa there, weiner-dog... If people don't make a big deal out of secret, encrypted connections made every 15 minutes by a miner program then what incentive is there for the dev to explain it, much less stop doing it?

Complaints like this are not about being an asshole, rather, it's to encourage a bit more transparency and accountability from the dev.

Frankly, I won't use a miner that does this secret squirrel shit, either, even if it is slightly - and I do mean, /slightly/ - faster than the competition.

So if bminer wants my business then he needs to A) improve stability - if your miner is 3% faster than the competition but it crashes with no outward appearance of doing so it isn't faster anymore; B) stop messaging home base every 15 minutes for "licensing information and updates" - what license, and why check for updates every 15 minutes when they aren't released but every month or so?; C) lower the devfee - I know dstm and ewbf charge 2% and the dev thinks he's entitled to the same, but that's not how capitalism works - when you are a newcomer to a field with entrenched competition you can't expect to immediately charge the same as said competition and thrive.

[FloppyPurpleGherkin]

Find a way to remove this shady and ridiculous private connection. Otherwise, EVERYONE SHOULD STAY AWAY FROM THIS MINER! Your rigs can go down whenever @realbminer wishes, or when his server goes down, etc.
...

Dude are you fucking retarded or what? You keep pissing on BMiner, yet you are still using it. There is something seriously wrong with you. If you dont like it GTFO and use some other miner and stop being such an asshole.

Whoa there, weiner-dog... If people don't make a big deal out of secret, encrypted connections made every 15 minutes by a miner program then what incentive is there for the dev to explain it, much less stop doing it?

Complaints like this are not about being an asshole, rather, it's to encourage a bit more transparency and accountability from the dev.

Frankly, I won't use a miner that does this secret squirrel shit, either, even if it is slightly - and I do mean, /slightly/ - faster than the competition.

So if bminer wants my business then he needs to A) improve stability - if your miner is 3% faster than the competition but it crashes with no outward appearance of doing so it isn't faster anymore; B) stop messaging home base every 15 minutes for "licensing information and updates" - what license, and why check for updates every 15 minutes when they aren't released but every month or so?; C) lower the devfee - I know dstm and ewbf charge 2% and the dev thinks he's entitled to the same, but that's not how capitalism works - when you are a newcomer to a field with entrenched competition you can't expect to immediately charge the same as said competition and thrive.

Very much agree.