Prohashing Mining Pool Forums

I am aware that the pool is having a large reject rate at the moment. I believe this is due to the pool switching coins so frequently that there are many stale shares being submitted and rejected. I am working on changing the configuration in order to reduce these rejected, and I will keep everyone updated in this post.

We have determined that there is resource contention on our database server, which is causing shares to be queued and submitted all at once (thus getting rejected for being stale). We are working to reduce load on the database server in order to mitigate the issue. As usual I will keep you updated on the progress.

The database issue has been resolved, and rejected shares are now minimal. We have also fixed the issue that caused some miners to be unable to connect. Check your "earnings" page and if you don't see a high efficiency please let me know.

hello,
congratulations for your work and sorry for my bad english.
I'm trying your pool for two days, working with 4 zeus thunder for about 120/140 mh / s of hashing power.
I have a high number of rejected for duplicate shares, about 30%.
How can solve?
Bye.

Hi,
just wondered about high rejected shares and low mhs...
maby its only the different coins your pool, this pool is ussing campared to other pools.
??difficulty and poolCoinhashrate....??
I will see, cause a few days ago, hashes were flying and low were recected
Maby stats need time to increase

Lg

I also have Zeus miners, and have tried to reproduce the problem without success, so I don't think it's a site-related issue. I'm going to ask if Kristof might be able to help you. He has some experience with mining equipment and has been helpful to me in the past.

Is anyone else having this problem? If this is a site-wide problem, then I can investigate it.

The rejected shares on Thursday were caused by the database being overloaded, but that issue was resolved. I edited this post to state that I added a few more indexes to some tables. The CPU load on postgres is averaging 15%, and it averages 9% at idle. Disk writes are only at 1MB/s, while the CacheCade on the RAID can support 500 times that. Memory usage is at 13GB, which is nothing unusual. Free space is at 7TB. Rejected shares is at 3.3%. Rejected shares normally stand around 2-3%, so that seems about normal.

Here are the acceptance rate statistics from 8:51am:

"iconalist";"2014-10-12 08:51:19-04";1
"hagie";"2014-10-12 08:51:19-04";1
"NacochataZ";"2014-10-12 08:51:19-04";1
"chris";"2014-10-12 08:51:19-04";1
"kscotta";"2014-10-12 08:51:19-04";1
"bsombsom";"2014-10-12 08:51:19-04";1
"Virosa";"2014-10-12 08:51:19-04";1
"kscotta4";"2014-10-12 08:51:19-04";1
"gamersglory";"2014-10-12 08:51:19-04";1
"gridseed";"2014-10-12 08:51:19-04";1
"kscotta6";"2014-10-12 08:51:19-04";1
"macbackfat";"2014-10-12 08:51:19-04";1
"dmacke00";"2014-10-12 08:51:19-04";1
"Marci99";"2014-10-12 08:51:19-04";1
"Mick2K";"2014-10-12 08:51:19-04";1
"kscotta5";"2014-10-12 08:51:19-04";1
"LordCoder";"2014-10-12 08:51:19-04";1
"Dstroyr";"2014-10-12 08:51:19-04";1
"javika";"2014-10-12 08:51:19-04";1
"kscotta3";"2014-10-12 08:51:19-04";1
"tmpwhore";"2014-10-12 08:51:19-04";1
"tcm8982";"2014-10-12 08:51:19-04";1
"Sanverk";"2014-10-12 08:51:19-04";1
"kscotta1";"2014-10-12 08:51:19-04";1
"Xander52";"2014-10-12 08:51:19-04";1
"cashmoney";"2014-10-12 08:51:19-04";1
"drpra";"2014-10-12 08:51:19-04";1
"Pickaxe";"2014-10-12 08:51:19-04";1
"glmwpg";"2014-10-12 08:51:19-04";1
"rustybeamer";"2014-10-12 08:51:19-04";0.996336996336996
"Janus67";"2014-10-12 08:51:19-04";0.996078431372549
"dreamxlord";"2014-10-12 08:51:19-04";0.995525727069351
"wcmwcm";"2014-10-12 08:51:19-04";0.995257731958763
"gmultani12";"2014-10-12 08:51:19-04";0.995169082125604
"Oleg76";"2014-10-12 08:51:19-04";0.994949494949495
"Wcrooker";"2014-10-12 08:51:19-04";0.99438202247191
"prelude";"2014-10-12 08:51:19-04";0.994011976047904
"rcadams";"2014-10-12 08:51:19-04";0.994011976047904
"zaner";"2014-10-12 08:51:19-04";0.993827160493827
"gigigo";"2014-10-12 08:51:19-04";0.993710691823899
"steve";"2014-10-12 08:51:19-04";0.993464052287582
"ktoth";"2014-10-12 08:51:19-04";0.993023255813953
"banjags";"2014-10-12 08:51:19-04";0.992831541218638
"adrenaline_x";"2014-10-12 08:51:19-04";0.992395437262357
"domninique";"2014-10-12 08:51:19-04";0.9921875
"professordank";"2014-10-12 08:51:19-04";0.990990990990991
"liati";"2014-10-12 08:51:19-04";0.990566037735849
"cryptocoalminer";"2014-10-12 08:51:19-04";0.990196078431373
"poltimco";"2014-10-12 08:51:19-04";0.989795918367347
"TheTrolley";"2014-10-12 08:51:19-04";0.989150090415913
"djuiw";"2014-10-12 08:51:19-04";0.988826815642458
"vintbtc";"2014-10-12 08:51:19-04";0.988543371522095
"Sithra";"2014-10-12 08:51:19-04";0.987951807228916
"trychlik";"2014-10-12 08:51:19-04";0.987931034482759
"lowtek";"2014-10-12 08:51:19-04";0.987341772151899
"fonker";"2014-10-12 08:51:19-04";0.986394557823129
"krjalone";"2014-10-12 08:51:19-04";0.986013986013986
"mruges";"2014-10-12 08:51:19-04";0.982731554160126
"JRminer";"2014-10-12 08:51:19-04";0.978021978021978
"kscotta2";"2014-10-12 08:51:19-04";0.976744186046512
"mahorobanara";"2014-10-12 08:51:19-04";0.970588235294118
"geekeh";"2014-10-12 08:51:19-04";0.96551724137931
"Nacochata";"2014-10-12 08:51:19-04";0.960199004975124
"beukhof1";"2014-10-12 08:51:19-04";0.957746478873239
"dexubdg";"2014-10-12 08:51:19-04";0.954264524103832
"brettbarth";"2014-10-12 08:51:19-04";0.916666666666667
"svstp";"2014-10-12 08:51:19-04";0.876288659793814
"Tompinara";"2014-10-12 08:51:19-04";0.842105263157895
"buechling";"2014-10-12 08:51:19-04";0.839779005524862
"Cobra98";"2014-10-12 08:51:19-04";0.833333333333333
"icekohl";"2014-10-12 08:51:19-04";0.8125
"lashworth";"2014-10-12 08:51:19-04";0.769230769230769
"beachgames";"2014-10-12 08:51:19-04";0.701388888888889

ok.

I know what this problem is. There is a specific version of a specific fork of bfgminer that has a bug in it that causes every share to be rejected. You appear to be using it.

Is it possible for you to switch to cgminer? There is a cgminer version for scrypt (3.7.2) which we use and which works perfectly.

ok, now i do a test.