Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 80. (Read 243468 times)

Pool is using the defaults, which are probably ASIC.

Yes, I will need to update this parameter to KH/S.

Its just an upgrade to keep you from crashing, so at your leisure.

yeah, that's not good. It's a limitation in the code for the old pool not the miner software.

Hopefully just a quick fix as I am also trying to make a "hard" account on NOMP pool

I want to create miner "harder" way, but it's not possible.
When I put BBP receiving address as miner name it give me this result:

I see 2 workers, one is mine. However I doubt I am doing Mega Hash so something isn't configured right on the pool end. The pool needs some tweaks but is currently doing alright
I actually am doing Mega Hash per second..... 78690 kh/s is after all 78.69 Mega Hash per second.... silly me lol

there is 1 worker and 220mhash? should not it be khash?

Mandatory from block nº?

some windows 10 users are stating the 1006 is crashing right away.
the error message is:

0xc00000fd stack_overflow

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **



I am proud to announce our new NOMP pool is now opening in Beta mode.

You must use the BBP external miner to mine against our NOMP pool (as nomp requires stratum).

Note, that ABN's are going to be supported, however today all the shares temporarily pay the same amount (as ABN is not configured on the server side yet).

The goal today is to ensure the shares are being accepted in prod, the miners do not crash in stratum mode, the miners continually receive new work, and that we can actually solve blocks in prod.  Also, we need to ensure payouts work correctly from the NOMP side.

Regarding payouts:  NOMP pays every 15 minutes, but does require each solved block to be fully matured; here is an example of how your payout would work:
Miner A solves block 100,000.  NOMP records this miners shares and BBP address in the database (even if you stop mining, NOMP will remember your work).
At block 100,120, NOMP will see the block has matured.  Within 30 minutes, it will distribute all of the payouts (for every share that participated in that block).
So from a high level, you will be paid about 12 hours later for shares you solved.

WEB SITE URL:

http://nomp.biblepay.org

I have added some preliminary instructions on how to mine against NOMP on the home page.  Please see the wiki.

Basic configuration from our external miner:

https://wiki.biblepay.org/Nomp_mining
(See the Easy setup section)


As soon as ABN is configured on the server, I will post and explain how you can see your ABN status and ABN payout information, etc.

BiblePay - External CPU Miner
1.0.0.6-Mandatory upgrade for Miners

- Prevent crash during big blocks

Binaries:

https://github.com/biblepay/cpuminer/tree/master/binaries

Yeah, if you are trying to mine the same block that is too big for the miner, it will continually crash until the block passes.

I got the same thing at the same time. Segmentation faults, bus errors. Miners did core dump (cannot find the dump file....) and then couldn't be restarted for almost half an hour without aborting. Strangely, after restarting the wallet the miners were fine until I unlocked the wallet. Then they immediately crashed again.

I see I am late to the party... oh well lol

Wow, first block in a while that took over 1 hour to mine.
Did not require ABN (could not find CPK) to mine this block.
https://chainz.cryptoid.info/bbp/block.dws?152520.htm
Good job BSVGwonbfwEYf26iwP8WB8ftC8Ghh74h9o

Ok, I think I see the problem- that big transaction is bigger than the buffer for the external miner.

I think thats why we all crashed at the same time - everyone was trying to mine it at the same time.

So, I am very close to deploying NOMP (I think within 24 hours I should have a test setup ready for prod)- at the same time, we need an upgrade for the miner anyway; so Ill increase the buffer to the size of our block size.

I think this will need to be done by tomorrow by noon.

In the mean time the core client should be mining OK.

Im starting to look at some of these external miner issues - but I have a lot going on- but I think you found the problem Sun - I believe our buffer is 65K - and if we sent out transactions bigger than that, I think that would crash the external miner.

Thats pretty huge.

Will look.  For some reason the CSS isnt showing up on bitcointalk and its hard to see quotes.

my miner crashed too about 3.5 hours

https://chainz.cryptoid.info/bbp/tx.dws?1162443.htm

Can the miner handle a tx this big? 71kB!

says it was a heap corruption

Faulting application name: bbpminer-x86.exe, version: 0.0.0.0, time stamp: 0x5da4aacd
Faulting module name: ntdll.dll, version: 10.0.17763.802, time stamp: 0x125ac1e8
Exception code: 0xc0000374
Fault offset: 0x00000000000fb049
Faulting process id: 0xc60
Faulting application start time: 0x01d585e05653251f
Faulting application path: C:\bbp\bbpminer-x86.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5df0bfb2-9e13-4ecc-bde0-6b60db36bff6
Faulting package full name:
Faulting package-relative application ID:

added khash/W and khash/GHz
all x5650 line and v1 xeons have same khash/ghz = about 4.2
all v2 xeons same about 4.65
does not matter if it is 24xx or 26xx line

so you can easily compute hashrate for any cpu . best v2 xeon e5 2697v2 will have ~670khash/s and 2.57 khash/W
v1(or x5650) vs v2 xeons is only 10% difference, so if you have cheap or free electricity, you can save money and buy g6/g7 servers, they are really cheap, dual x5650 machine for ~100$


1. Lenovo C30
Dual Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
2x 135W
32 threads @ 2.90GHz
Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-154-generic x86_64)
128GB (8x 16GB @ 1600MHz)
Total: 391.81 khash/s
khash/W = 1.45
khash/GHz = 4.22

2. Lenovo C30
Dual Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
2x 135W
32 threads @ 2.90GHz
Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-31-generic x86_64)
96GB (6x 16GB @ 1600MHz)
Total: 390.72 khash/s
khash/W = 1.45
khash/GHz = 4.21

3. Lenovo C30
Dual Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
2x 115W
40 threads @ 3.10GHz
Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-164-generic x86_64)
128GB (8x 16GB @ 1600MHz)
Total: 574.62 khash/s
khash/W = 2.50
khash/GHz = 4.63

4. Lenovo C30
Dual Intel(R) Xeon(R) CPU E5-2650L v2 @ 1.70GHz
2x 70W
40 threads @ 1.90GHz
Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-142-generic x86_64)
32GB (8x 4GB @ 1333MHz)
Total: 355.55 khash/s
khash/W = 2.54
khash/GHz = 4.68

5. HP DL160 G6
Dual Intel(R) Xeon(R) CPU L5520  @ 2.27GHz
2x 60W
16 threads @ 2.40GHz
Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-154-generic x86_64)
8GB (2x 4GB @ 1066MHz)
Total: 161.14 khash/s
khash/W = 1.34
khash/GHz = 4.20

6. Intel SR1625URSAS
Dual Intel(R) Xeon(R) CPU X5650  @ 2.67GHz
2x 95W
24 threads @ ~2.75GHz
Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64)
8GB (2x 4GB @ 1333MHz)
Total: 274.16 khash/s
khash/W = 1.44
khash/GHz = 4.15

7. IBM System x3550 M3
Dual Intel(R) Xeon(R) CPU X5660  @ 2.80GHz
2x 95W
24 threads @ ~2.90GHz
Ubuntu 17.10 (GNU/Linux 4.13.0-16-generic x86_64)
8GB (2x 4GB @ 1333MHz)
Total: 288.88 khash/s
khash/W = 1.52
khash/GHz = 4.15

8. HP DL360e G8
Dual Intel(R) Xeon(R) CPU E5-2420 v2 @ 2.20GHz
2x 80W
running @ 2.50Ghz
Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64)
24GB (12x 2GB @ 1333Mhz)
Total: 281.21 khash/s
khash/W = 1.76
khash/GHz = 4.69

9. laptop Thinkpad P52s
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
15W
8 threads somewhere @ 2.5-2.8GHz
Win10 Enterprise
16GB (2x 8GB @ 2400MHz)
Total: 133.21 khash/s
khash/W = 8.88
khash/GHz = ~6.28

10. HP DL360e G8
Dual Intel(R) Xeon(R) CPU E5-2450L 0 @ 1.80GHz
2x 70W
32 threads running @ 2.00GHz
Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-142-generic x86_64)
32GB (8x 4GB @ 1333MHz)
Total: 267.78 khash/s
khash/W = 1.91
khash/GHz = 4.18

11. HP DL380p G8
Dual Intel(R) Xeon(R) CPU E5-2650L v2 @ 1.70GHz
2x 70W
40 threads running @ 1.90GHz
Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-142-generic x86_64)
48GB (12x 4GB @ 1333MHz)
Total: 353.54 khash/s
khash/W = 2.53
khash/GHz = 4.65

12. Dell T3600
Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz
130W
8 threads running @ 3.67GHz
Win10 Pro
16GB (4x 4GB @ 1333MHz)
Total: 120.24 khash/s
khash/W = 0.92
khash/GHz = 4.09

more machines coming soon...
also i will do test linux vs win on same machine

same case...
look like is the "gsc_errors" problem ? Even disable GSC transaction in biblepay.conf still have problem

My windows wallet v1.4.5.0 has crashed twice the past 2-3 days,
just checked log and nothing popped out to me,
Ill add debug=1 this time and report back if it happens again
Config file only has disablegsctransmission=1

hmm few minutes ago, all miners on all wallets on all PCs crashed... also on wallet copies... so it must have something to do with data from wallets

few logs from misc pcs:
[2042803.452824] traps: bbpminer_linux[7947] trap stack segment ip:7fa3781c245b sp:7fa378142ad0 error:0 in libc-2.23.so[7fa378144000+1c0000]
[159775.469343] traps: bbpminer_linux[1710] trap stack segment ip:7f9a2aee345b sp:7f9a2ae63ad0 error:0 in libc-2.23.so[7f9a2ae65000+1c0000]
[159780.299285] traps: bbpminer_linux[1801] trap stack segment ip:7ff438eea45b sp:7ff438e696e0 error:0 in libc-2.23.so[7ff438e6c000+1c0000]
[159792.120281] traps: bbpminer_linux[1711] general protection ip:7f0b6c6ab512 sp:7f0b6c625bd0 error:0 in libc-2.23.so[7f0b6c627000+1c0000]

Bus error               (core dumped) ./bbpminer_linux ...
Segmentation fault      (core dumped) ./bbpminer_linux ...
Bus error               (core dumped) ./bbpminer_linux ...

[1613129.400148] biblepay-miner[8442]: segfault at 50370 ip 00007f9639a72d44 sp 00007f9509efacd0 error 4 in libpthread-2.23.so[7f9639a69000+18000]
[2042899.987031] traps: bbpminer_linux[17172] general protection ip:7fccc235b512 sp:7fccc22d5bd0 error:0 in libc-2.23.so[7fccc22d7000+1c0000]
...
btw wallets are still running and all have ok abn

edit: i cant start miners, they crash immediately...
getblockforstratum showing some long hex and no error

mining info showing on two wallets:
  "abninfo": "ABN: OK; ",
  "gsc_errors": "low abn weight 124936",

  "abninfo": "ABN: OK; ",
  "gsc_errors": "low abn weight 0",

but abn is ok
  "weight": 560430.9543402777,
and
  "weight": 1419968.982430556,

edit2: now i can start miners again, maybe chain moved to another block or what... maybe there was some weird block around 152537