BiblePay - TestNet Thread - Pool Testing for Proof of Bible Hash Pool (PoBh) - page 16.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: happy_merchant on August 12, 2017, 07:13:05 AM

Also, there were a couple times tonight that logging in to the pool website failed. No errors or anything, you just click login and the page reloads but you're not logged in. It's currently happening at 5:11 AM PST.

Oh my another morning of IT issues! Thanks for all the help btw.
So, on the long miner name itself, I added a length restriction of 19 chars to the page and deleted your worker, so please recreate it.
I dont know why the hashPS join subsystem was calculating your hashes wrong. Im still tweaking the shares anyway, so its moot to even fix that. Let me try to get that working so we can test that new system.
The pool backfilled the block_distribution back in automatically without your worker, but after you recreate it you should be back on, but yes, if this happened in prod, I would need a procedure to back out the money also from the users, and in testnet you still got credited.

Regarding the inability to log in, by the time I woke up, the system was back up. Ill look at the logs. Something is causing the microsoft app pool to crash, and then when the 'down' elapse period is exceeded, it brings itself back up. I assume mining is still occurring at that time.

happy_merchant

member

Activity: 70

Merit: 10

Also, there were a couple times tonight that logging in to the pool website failed. No errors or anything, you just click login and the page reloads but you're not logged in. It's currently happening at 5:11 AM PST.

happy_merchant

member

Activity: 70

Merit: 10

Another weird thing that I've been wondering for a while now. The network_khashps reported by getmininginfo seems to be off. Right now for example it's saying 465 kh/s. Adding the values from the pool, it should be around 60-70 kh/s. It's possible there's a miner or two on the test chain who aren't in the pool, but it's definitely not 400 kh/s worth of non-pool miners since the pool is finding every block.

happy_merchant

member

Activity: 70

Merit: 10

Code:

1f60b28d-cd84-4a53-b9df-aa486e911660	Anonymous	925	19998.0000	36.1035		8/12/2017 2:24:18 AM	24674.53	0.00146318753300487	8/12/2017 2:24:18 AM	Anonymous
51becfe1-2bde-498c-b485-181c00f78081	bible_pay	925	19998.0000	28.7325		8/12/2017 2:24:18 AM	19636.9		0.00146318753300487	8/12/2017 2:24:18 AM	lastleg: 24382 (19637)
2e1d36d9-fe36-4bdf-b1c6-16eff6aae895	testbible	925	19998.0000	18.7215		8/12/2017 2:24:18 AM	12795.02	0.00146318753300487	8/12/2017 2:24:18 AM	testbible: 17191 (12795)
86c24031-52d0-4b0a-9ce9-47552a481be8	happy_merchant	925	19998.0000	19914.4426	8/12/2017 2:24:18 AM	13610314.54	0.00146318753300487	8/12/2017 2:24:18 AM	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: 9013 (13610315)

38d49a58-7f7f-4805-9719-29e829785535	Anonymous	924	19998.0000	36.1035		8/12/2017 2:24:18 AM	24674.53	0.00146318753300487	8/12/2017 2:24:18 AM	Anonymous
a0fa143e-9273-4e43-938e-e0af8de565b2	bible_pay	924	19998.0000	28.7325		8/12/2017 2:24:18 AM	19636.9		0.00146318753300487	8/12/2017 2:24:18 AM	lastleg: 24382 (19637)
0f0c56cd-daf2-4676-876c-f9f54e8bced4	testbible	924	19998.0000	18.7215		8/12/2017 2:24:18 AM	12795.02	0.00146318753300487	8/12/2017 2:24:18 AM	testbible: 17191 (12795)
817abd92-0d98-4027-b659-ebfe0a9c62b8	happy_merchant	924	19998.0000	19914.4426	8/12/2017 2:24:18 AM	13610314.54	0.00146318753300487	8/12/2017 2:24:18 AM	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: 9013 (13610315)

Alright, I'm not sure what's going on here, but I can assure you that hashrate is not correct. getmininginfo is reporting 9190 hashps.

It started reporting like that right after I created the miner named "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxx". That's 100 'x' characters, which looks like the cap on worker names.

--edit--
Possibly related, this is being reported on the account page for the worker id:

Code:

Username:	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	Threads:	32762	HPS:	10609.6932326281

The thread count is clearly off, it's running at 4 threads.

--edit--
The miner also seems to be dropping a large amount of blocks. It didn't register at all for blocks 931-936.

It is getting credited the disproportionate share of the reward for the blocks where it does get recorded, though.

--edit--
I swapped to an alternate account and created a worker id "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy yyyyyyyyyyyyyyyyyyyyy", but I wasn't able to reproduced what happened above. It functioned normally.

--edit--
Created another worker id with 100 'z's on my original account and it had the same issue as 'xxx...'. Weird. I see someone's cleaning up the mess though so you probably already noticed it.

--edit--
Now my happy_merchant00 worker id looks like it's doing it. Maybe it wasn't related to the long worker names. I tried entering some unicode gibberish worker ids and they all seemed to get converted ASCII letters and question marks so I figured they were being handled okay, but maybe they caused a problem. Also some punctuation-only ids including just spaces.

tiras

full member

Activity: 221

Merit: 100

bible_pay , I realize can ignore this q, but can you give ETA for a live pool ? is it a week , month or longer ? Huh

happy_merchant

member

Activity: 70

Merit: 10

Quote from: bible_pay on August 11, 2017, 08:25:00 AM

Oh ok, well I do know that the current version of the pool doesnt work as well with one thread (although I dont want to encourage a huge number of threads as that would saturate the pool) but anyway, with one thread, I can see falling out of the block, as if that one thread gets tied up with work it could miss a block. Maybe try 4 threads or so?

Ah, I see, that actually could be the issue then. It did start happening around the time I swapped from 8 threads to 1 thread. I'll give that a shot.

--edit--
My alt account was dropping blocks too, so I bumped it up from 1 thread to 4 threads starting at block 912.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: happy_merchant on August 11, 2017, 08:16:37 AM

Quote from: bible_pay on August 11, 2017, 07:44:24 AM

Yeah, the current pool does try to take account HPS on miners that pool hop, but the synthetic HPS of the pool is not always accurate per block- but I think over time it would be a good average. The payout for 773 was based on 8763 hash ps, but your _alt miner generally did about 10500 hash ps. I wonder if you worked on at least 50% of the block or if you really got lucky. I also wonder, how many threads are you running on this miner?

Was only mining on happy_merchant_alt for less than 5 minutes out of the 55 minutes for that block, so it definitely wasn't 50%. Just running 1 thread on my pool miner.

Quote from: bible_pay on August 11, 2017, 07:49:44 AM

I took a look at the logs, and I believe the issue is on the pool side predominantly, but what happens occasionally, is the threads on the miner side get tied up with work that is too hard to solve for longer than the duration of the block, and 0 shares are submitted by the miner that count toward the block, even if the miner submitted the solution, the stats didnt update in time before the block was solved and paid.

I don't know if it's relevant, but it hasn't happened since I swapped pool accounts. It was happening pretty frequently before, but now it's been over 40 blocks without dropping any. The miner is identical, I just changed the worker_id. Also, I didn't notice it happening before I spammed all those withdrawal transactions, so I'm wondering if maybe something in that account got corrupted. Going to keep mining on my alt account for a while to verify that it's not happening, then I'll try swapping back again.

Oh ok, well I do know that the current version of the pool doesnt work as well with one thread (although I dont want to encourage a huge number of threads as that would saturate the pool) but anyway, with one thread, I can see falling out of the block, as if that one thread gets tied up with work it could miss a block. Maybe try 4 threads or so?

happy_merchant

member

Activity: 70

Merit: 10

Quote from: bible_pay on August 11, 2017, 07:44:24 AM

Yeah, the current pool does try to take account HPS on miners that pool hop, but the synthetic HPS of the pool is not always accurate per block- but I think over time it would be a good average. The payout for 773 was based on 8763 hash ps, but your _alt miner generally did about 10500 hash ps. I wonder if you worked on at least 50% of the block or if you really got lucky. I also wonder, how many threads are you running on this miner?

Was only mining on happy_merchant_alt for less than 5 minutes out of the 55 minutes for that block, so it definitely wasn't 50%. Just running 1 thread on my pool miner.

Quote from: bible_pay on August 11, 2017, 07:49:44 AM

I took a look at the logs, and I believe the issue is on the pool side predominantly, but what happens occasionally, is the threads on the miner side get tied up with work that is too hard to solve for longer than the duration of the block, and 0 shares are submitted by the miner that count toward the block, even if the miner submitted the solution, the stats didnt update in time before the block was solved and paid.

I don't know if it's relevant, but it hasn't happened since I swapped pool accounts. It was happening pretty frequently before, but now it's been over 40 blocks without dropping any. The miner is identical, I just changed the worker_id. Also, I didn't notice it happening before I spammed all those withdrawal transactions, so I'm wondering if maybe something in that account got corrupted. Going to keep mining on my alt account for a while to verify that it's not happening, then I'll try swapping back again.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: happy_merchant on August 10, 2017, 09:01:46 AM

Alright, so my miner apparently dropped out of the pool for blocks 642-643 and 659-660. Here's the verbose debug log for blocks 658-661

https://pastebin.com/qdB4v9dX (block 658)
https://pastebin.com/G6kawJYc (block 659)
https://pastebin.com/qG5VSDf2 (block 660)
https://pastebin.com/npy6NbBB (block 661)

https://file.io/ODsv3P (entire log)

Nothing really jumps out at me from the logs. Doesn't look like other miners are having the same issue, so it's a little weird.

I took a look at the logs, and I believe the issue is on the pool side predominantly, but what happens occasionally, is the threads on the miner side get tied up with work that is too hard to solve for longer than the duration of the block, and 0 shares are submitted by the miner that count toward the block, even if the miner submitted the solution, the stats didnt update in time before the block was solved and paid.

I think its probably more productive for us to test out the shares based payment and see if this results in a more frequent and accurate HPS reading and then we can re-test this again overnight. Im going to try to work on the shares today.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: happy_merchant on August 11, 2017, 02:16:51 AM

I made a second account to test some stuff out. One thing that I noticed is that I seemed to get paid in full for doing very little work on block 773. According to my logs, I connected to the pool on happy_merchant_alt at 1:45:16. Block 773 took 55 minutes 5 seconds to mine. So, I worked on the block for roughly 10% of the block time, but I received credit as though I had worked on the entire block:

Code:

82624506-2b5f-436e-a5e1-bf6c4ee5101b	jc12345			773	19999.0000	8211.6667	8/11/2017 1:49:45 AM	27192.68	0.301980800376851	8/11/2017 1:49:45 AM	jc12345.1: 30898 (27193)
bd593ffa-497a-4b32-982c-19ef459d90ae	bible_pay		773	19999.0000	5367.8276	8/11/2017 1:49:45 AM	17775.39	0.301980800376851	8/11/2017 1:49:45 AM	lastleg: 27541 (17775)
beca7599-b7af-40fb-ba50-3ca1a7a23955	testbible		773	19999.0000	3773.2580	8/11/2017 1:49:45 AM	12495.03	0.301980800376851	8/11/2017 1:49:45 AM	testbible: 16941 (12495)
f9b00f4c-1515-43c5-861d-a05f5ca4db55	happy_merchant_alt	773	19999.0000	2646.2477	8/11/2017 1:49:45 AM	8762.97		0.301980800376851	8/11/2017 1:49:45 AM	happy_merchant_alt00: 12539 (8763)

45f169b3-51c1-4a0c-8f5c-ee8b09a1afd6	jc12345			772	19999.0000	6589.6708	8/11/2017 12:54:40 AM	24509.38	0.268863219343847	8/11/2017 12:54:40 AM	jc12345.1: 30855 (24509)
e5fa7538-29a6-40de-9818-51d12ba68463	bible_pay		772	19999.0000	6359.3726	8/11/2017 12:54:40 AM	23652.82	0.268863219343847	8/11/2017 12:54:40 AM	lastleg: 27602 (23653)
605dd1aa-8b70-4cee-905c-3e530b8f401b	testbible		772	19999.0000	4357.7661	8/11/2017 12:54:40 AM	16208.12	0.268863219343847	8/11/2017 12:54:40 AM	testbible: 16923 (16208)
d80c2584-34de-4df7-8ba0-94a1273df69a	happy_merchant		772	19999.0000	2692.1905	8/11/2017 12:54:40 AM	10013.23	0.268863219343847	8/11/2017 12:54:40 AM	happy_merchant00: 12911 (10013)

Code:

MINING_CREDIT	773	e35c1d44-0b03-4476-b9b8-34888baecc36	f9b00f4c-1515-43c5-861d-a05f5ca4db55	2646.2477	2646.2477	8/11/2017 1:49:45 AM

I had been working on block 773 on my original account at the same IP address up till then, so I don't know if that influenced somehow.

--edit--
Actually, looking at subsequent blocks, the HPS was a little lower so maybe mining time was taken into consideration for the calculation? Just didn't seem to make much difference in the payout. Realistically I doubt it's something that could be effectively abused in any case.

Yeah, the current pool does try to take account HPS on miners that pool hop, but the synthetic HPS of the pool is not always accurate per block- but I think over time it would be a good average. The payout for 773 was based on 8763 hash ps, but your _alt miner generally did about 10500 hash ps. I wonder if you worked on at least 50% of the block or if you really got lucky. I also wonder, how many threads are you running on this miner?

In any case, I am working on adding a share based system in, instead of the synthetic HPS reading to see if that works better, and Im trying to make it to where I can switch over to it but yet have both columns in all the reports. Something like TotalShares and SharesSolved or something per row.

Im still looking at the other posts with the logs you sent.

happy_merchant

member

Activity: 70

Merit: 10

I made a second account to test some stuff out. One thing that I noticed is that I seemed to get paid in full for doing very little work on block 773. According to my logs, I connected to the pool on happy_merchant_alt at 1:45:16. Block 773 took 55 minutes 5 seconds to mine. So, I worked on the block for roughly 10% of the block time, but I received credit as though I had worked on the entire block:

Code:

82624506-2b5f-436e-a5e1-bf6c4ee5101b	jc12345			773	19999.0000	8211.6667	8/11/2017 1:49:45 AM	27192.68	0.301980800376851	8/11/2017 1:49:45 AM	jc12345.1: 30898 (27193)
bd593ffa-497a-4b32-982c-19ef459d90ae	bible_pay		773	19999.0000	5367.8276	8/11/2017 1:49:45 AM	17775.39	0.301980800376851	8/11/2017 1:49:45 AM	lastleg: 27541 (17775)
beca7599-b7af-40fb-ba50-3ca1a7a23955	testbible		773	19999.0000	3773.2580	8/11/2017 1:49:45 AM	12495.03	0.301980800376851	8/11/2017 1:49:45 AM	testbible: 16941 (12495)
f9b00f4c-1515-43c5-861d-a05f5ca4db55	happy_merchant_alt	773	19999.0000	2646.2477	8/11/2017 1:49:45 AM	8762.97		0.301980800376851	8/11/2017 1:49:45 AM	happy_merchant_alt00: 12539 (8763)

45f169b3-51c1-4a0c-8f5c-ee8b09a1afd6	jc12345			772	19999.0000	6589.6708	8/11/2017 12:54:40 AM	24509.38	0.268863219343847	8/11/2017 12:54:40 AM	jc12345.1: 30855 (24509)
e5fa7538-29a6-40de-9818-51d12ba68463	bible_pay		772	19999.0000	6359.3726	8/11/2017 12:54:40 AM	23652.82	0.268863219343847	8/11/2017 12:54:40 AM	lastleg: 27602 (23653)
605dd1aa-8b70-4cee-905c-3e530b8f401b	testbible		772	19999.0000	4357.7661	8/11/2017 12:54:40 AM	16208.12	0.268863219343847	8/11/2017 12:54:40 AM	testbible: 16923 (16208)
d80c2584-34de-4df7-8ba0-94a1273df69a	happy_merchant		772	19999.0000	2692.1905	8/11/2017 12:54:40 AM	10013.23	0.268863219343847	8/11/2017 12:54:40 AM	happy_merchant00: 12911 (10013)

Code:

MINING_CREDIT	773	e35c1d44-0b03-4476-b9b8-34888baecc36	f9b00f4c-1515-43c5-861d-a05f5ca4db55	2646.2477	2646.2477	8/11/2017 1:49:45 AM

I had been working on block 773 on my original account at the same IP address up till then, so I don't know if that influenced somehow.

--edit--
Actually, looking at subsequent blocks, the HPS was a little lower so maybe mining time was taken into consideration for the calculation? Just didn't seem to make much difference in the payout. Realistically I doubt it's something that could be effectively abused in any case.

happy_merchant

member

Activity: 70

Merit: 10

Quote from: bee_irl on August 10, 2017, 12:52:26 PM

Edit: seems like a normal fork or reorg. Were you watching the network to see if that happened?

A blockchain fork? It's not like one miner in a pool can be off mining down the wrong blockchain since work is delegated by the pool server.

At least, that'd normally be the case. Biblehash is a little unique and involves a reference to the previous block in the chain which requires miners to run their own full nodes, so I suppose it might be possible that a user in the pool would be attempting to mine while referencing an orphan block, which would probably result in all their shares being rejected. I don't know if the pool checks to make sure all users are synced properly. I don't think that's the case here though since all the hashes from the logs seem to match up with the test blockchain.

bee_irl

newbie

Activity: 21

Merit: 0

Quote from: happy_merchant on August 09, 2017, 11:37:36 PM

Ah, you're right, that was around the same time.

It also happened again quite a bit later at block 604 with the same error as block 584/585:

Code:

2017-08-09 23:33:45 UpdateTip: new best=000015cb5f14b102bd89e9cd1c1e835e9ee56754895a7b6208272c40cac135fa  height=604  log2_work=26.525747  tx=2109  date=2017-08-09 23:33:43 progress=0.002907  cache=0.4MiB(1967tx)
2017-08-09 23:33:45  

 ** TestBlockValidity FAILED - pindexNew->pprev != chainActive.Tip() (assert(pindexNew->pprev == chainActive.Tip())); ** 

2017-08-09 23:33:45 

BiblepayMiner -- runtime error: CreateNewBlock: TestBlockValidity failed:  (code 0)
2017-08-09 23:33:45 ProcessNewBlock : ACCEPTED
2017-08-09 23:38:45 UpdateTip: new best=00001db3d3ff8196dc01a228037e4c88254b44aa730e222b7e256426e207cb25  height=605  log2_work=26.533668  tx=2110  date=2017-08-09 23:38:43 progress=0.002908  cache=0.4MiB(1968tx)
2017-08-09 23:38:45 ProcessNewBlock : ACCEPTED
2017-08-09 23:58:15 UpdateTip: new best=00001744716e7698fcaae5352b51c16dde765c7c7a26d1ecbd333790e62ca92b  height=606  log2_work=26.542772  tx=2111  date=2017-08-09 23:58:13 progress=0.002910  cache=0.4MiB(1969tx)
2017-08-09 23:58:15 ProcessNewBlock : ACCEPTED

Went ahead and enabled debugmaster, will check in the morning to see if it happens again tonight.

Edit: seems like a normal fork or reorg. Were you watching the network to see if that happened?

happy_merchant

member

Activity: 70

Merit: 10

Alright, so my miner apparently dropped out of the pool for blocks 642-643 and 659-660. Here's the verbose debug log for blocks 658-661

https://pastebin.com/qdB4v9dX (block 658)
https://pastebin.com/G6kawJYc (block 659)
https://pastebin.com/qG5VSDf2 (block 660)
https://pastebin.com/npy6NbBB (block 661)

https://file.io/ODsv3P (entire log)

Nothing really jumps out at me from the logs. Doesn't look like other miners are having the same issue, so it's a little weird.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: happy_merchant on August 10, 2017, 12:05:38 AM

A minor issue on the website, since I spammed all those withdrawals the transaction history page doesn't seem to be updating any longer. It stops on block 547 after listing a few hundred of the withdrawals. BBP from mining is still being credited and I can still make withdrawals, though, so it looks like it's just a display error.

It just shows the last 512 transactions in the transaction log to keep the pages list short, however it was ordered by UPDATED not UPDATED Desc, so that change will be in the *next* pool release, however in the mean time, I deleted the 1200 transactions < .05 BBP from your account so you should be able to see the list now.

happy_merchant

member

Activity: 70

Merit: 10

A minor issue on the website, since I spammed all those withdrawals the transaction history page doesn't seem to be updating any longer. It stops on block 547 after listing a few hundred of the withdrawals. BBP from mining is still being credited and I can still make withdrawals, though, so it looks like it's just a display error.

happy_merchant

member

Activity: 70

Merit: 10

Ah, you're right, that was around the same time.

It also happened again quite a bit later at block 604 with the same error as block 584/585:

Code:

2017-08-09 23:33:45 UpdateTip: new best=000015cb5f14b102bd89e9cd1c1e835e9ee56754895a7b6208272c40cac135fa  height=604  log2_work=26.525747  tx=2109  date=2017-08-09 23:33:43 progress=0.002907  cache=0.4MiB(1967tx)
2017-08-09 23:33:45  

 ** TestBlockValidity FAILED - pindexNew->pprev != chainActive.Tip() (assert(pindexNew->pprev == chainActive.Tip())); ** 

2017-08-09 23:33:45 

BiblepayMiner -- runtime error: CreateNewBlock: TestBlockValidity failed:  (code 0)
2017-08-09 23:33:45 ProcessNewBlock : ACCEPTED
2017-08-09 23:38:45 UpdateTip: new best=00001db3d3ff8196dc01a228037e4c88254b44aa730e222b7e256426e207cb25  height=605  log2_work=26.533668  tx=2110  date=2017-08-09 23:38:43 progress=0.002908  cache=0.4MiB(1968tx)
2017-08-09 23:38:45 ProcessNewBlock : ACCEPTED
2017-08-09 23:58:15 UpdateTip: new best=00001744716e7698fcaae5352b51c16dde765c7c7a26d1ecbd333790e62ca92b  height=606  log2_work=26.542772  tx=2111  date=2017-08-09 23:58:13 progress=0.002910  cache=0.4MiB(1969tx)
2017-08-09 23:58:15 ProcessNewBlock : ACCEPTED

Went ahead and enabled debugmaster, will check in the morning to see if it happens again tonight.

marte1982

member

Activity: 129

Merit: 10

Hi dev...when pool go online..i mean mainnet? thanks for your support

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

The pool now recovers from errors where the user tries to hit pages and is no longer logged in.

I added the requested anonymous user feature, if you go to account and click 'cloak' user and save the record.

Regarding my testnet pool miner crashing, I added a global csection that *may* fix that, now I am burning it in tonight, good night.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Topic: BiblePay - TestNet Thread - Pool Testing for Proof of Bible Hash Pool (PoBh) - page 16. (Read 13217 times)