Bitcoin Forum
September 27, 2016, 08:38:14 PM *
News: Due to DDoS attacks, there may be periodic downtime.
 
   Home   Help Search Donate Login Register  
Poll
Question: What type of pool payouts do you prefer?
Bitcoins - 3151 (80.4%)
Bank transfer / USD - 407 (10.4%)
Gold/silver coins and bars - 359 (9.2%)
Total Voters: 3915

Pages: « 1 ... 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 [181] 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 ... 1104 »
  Print  
Author Topic: [40+ PH] SlushPool (slushpool.com); World's First Mining Pool  (Read 3855373 times)
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 03, 2011, 11:42:41 PM
 #3601

Quote from: slush
I report those issues to phoenix developers via PM and I still don't have any response. However I know there are some pool users affected by those bugs and I'm pretty sure that you are one of them.

I'd like to be more specific. From all ~6000 connected miners only few (up to 20) of them have some troubles and _all_ of those are using phoenix. All other miners are performing better than without LP support. I wanted to fix phoenix before I enabled LP support on live pool, unfortunately because of missing interest from side of phoenix developers I decided to release new pool version and ask those affected users to change their miners. Phoenix is pretty good miner, but it has some really weird bugs which affect 0.1% of users and there's nothing what I can do for that on my side...

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1475008694
Hero Member
*
Offline Offline

Posts: 1475008694

View Profile Personal Message (Offline)

Ignore
1475008694
Reply with quote  #2

1475008694
Report to moderator
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 03, 2011, 11:45:31 PM
 #3602

when will the :8331 backend be shutdown? should I switch all mine back to :8332 in the next couple days?

8331 will be still working, I'll be using those miners for stress-tests for new pool features which are coming. So if you want to help me with that, leave your miner(s) connected here. Otherwise you can connect to "production" pool at 8332 at any time. At this moment, both "beta" and "production" are running same pool version...

pekv2
Hero Member
*****
Offline Offline

Activity: 770



View Profile
October 03, 2011, 11:52:06 PM
 #3603

Is this pool located in the UK?

Yes, in London.

Quote
I don't know what is going on but I am being hammered with rejected shares, only in ten minutes I had more than 25 rejected.

It is probably because of failed LP broadcast. You've problem with LP connectioins (as described in phoenix forum thread). When LP connection fails, miner don't know about new bitcoin block and he's still submitting shares from old job, which leads in wall of rejected...

If you read my bug reports in phoenix thread, some phoenix instances have very weird connection problems. Unfortunately it is more than week when I report those issues to phoenix developers via PM and I still don't have any response. However I know there are some pool users affected by those bugs and I'm pretty sure that you are one of them.

Generally I have following advices:
1) Changing phoenix to something more stable, at least until they fixed those weird connection bugs. From my experience poclbm is much more stable and is following protocol standards much better than phoenix.
2) Disable LP for those workers on profile page and after few minutes restart miners. Your miners will work in the same way as on pool version without LP.

Quote
I swapped to deepbit as a test, been mining for an hour, I've only got one rejected so far.

There are small differences between my pool and deepbit implementation, which probably lead to this:
a) My pool is officially supporting miner extension "X-Roll-NTime", so miner can use one job up to one minute, because he can modify "ntime" parameter of job.
b) Pool is rejecting submits from jobs older than 5 minutes even when there wasn't new bitcoin block.  I don't know how old jobs deepbit accepts, but this 5 minutes timeout (originally 60 second in X-Roll-NTime specs) is there because miners need to reload merkle tree time to time and 60 seconds are pretty good compromise.

Unfortunately one of phoenix bug is that he's sometimes reusing *very* old jobs for no reasons, so those shares are rejected. This was also reported and also without response...

Short summary: Turn off LP or change miner to poclbm, both ways will probably solve your issues.

Slush, let me start of with a huge Thank you, for the great writeup of explanation in this thread and in gui mining thread.

I've been using poclbm since day one of me mining, dating back quite a few months ago.

I am looking into problems reported for the model of my router and modem see if I cannot find something atleast in any forums for a fix or something.

As of 20 min ago, I'm back on guiminer v2011-08-24, 20 min of mining I haven't received one error or rejected, I will take your suggestion if errors occur again and disable LP.

I'm sending a donation your way. I really really appreciate your help.

Thank you.
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 03, 2011, 11:58:18 PM
 #3604

I'm sending a donation your way. I really really appreciate your help.

Thank you :-).

pekv2
Hero Member
*****
Offline Offline

Activity: 770



View Profile
October 04, 2011, 12:09:41 AM
 #3605

Sent!  Smiley
vapourminer
Hero Member
*****
Offline Offline

Activity: 802

what is this "brake pedal" you speak of?


View Profile
October 04, 2011, 12:30:14 AM
 #3606

when will the :8331 backend be shutdown?

8331 will be still working, I'll be using those miners for stress-tests for new pool features which are coming. So if you want to help me with that, leave your miner(s) connected here.

Ill leave em all parked at :8331 then. running cgminer with failover to another pool if something happens so no worries here.
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 05, 2011, 05:14:03 PM
 #3607

Recently I added important features to pool (long polling and ntime rolling), but support of those features is really weak in some old miners. If you see walls of rejected shares on your miners, please update them to latest version - some of you are using really old miners which does not correctly handle all pool features.

Note for Phoenix users: If you are already using latest Phoenix and you still see walls of rejected shares, you're probably affected by known bugs in Phoenix (see post above or in phoenix thread). Please downgrade to phoenix 1.5 or switch to another miner (I recommend poclbm or GUIminer with poclbm core).

Expected stale ratio is far under 1%. It also depends on connection quality and latency to pool servers. If you see higher stale ratio, please report it by PM or by email to info@bitcoin.cz. I will need your worker login, exact version of miner and ideally copy of miner log (together with your timezone) to investigate that issue on my side.

RobertRibbeck
Full Member
***
Offline Offline

Activity: 221


View Profile
October 05, 2011, 06:20:34 PM
 #3608

Recently I added important features to pool (long polling and ntime rolling), but support of those features is really weak in some old miners. If you see walls of rejected shares on your miners, please update them to latest version - some of you are using really old miners which does not correctly handle all pool features.

Note for Phoenix users: If you are already using latest Phoenix and you still see walls of rejected shares, you're probably affected by known bugs in Phoenix (see post above or in phoenix thread). Please downgrade to phoenix 1.5 or switch to another miner (I recommend poclbm or GUIminer with poclbm core).

Expected stale ratio is far under 1%. It also depends on connection quality and latency to pool servers. If you see higher stale ratio, please report it by PM or by email to info@bitcoin.cz. I will need your worker login, exact version of miner and ideally copy of miner log (together with your timezone) to investigate that issue on my side.

Thanks Slush
version 1.50 is still buggy but at least it's better

Please "Clear your browser cookies" then use http://bitcoinpyramid.com/r/3360 to Join BitCoin Pyramid
  use my referral & I'll refund a % of your first deposit back to your account
  Deposit .5 BTC or more and I'll give back 50% of what I receive

First Deposit of 1 BTC will get 75% of what I get back
FoxMURDER
Jr. Member
*
Offline Offline

Activity: 49


View Profile
October 05, 2011, 07:16:30 PM
 #3609

Hey slush ... after what seemed as few restarts on the 'beta' pool i'm now getting quite a few rejects ... while still getting accepts
Code:
[5.10.11 21:08:22] api.bitcoin.cz accepted block 7380 from Cayman (#1)
[5.10.11 21:08:34] api.bitcoin.cz accepted block 7381 from Cayman (#1)
[5.10.11 21:09:05] api.bitcoin.cz rejected block 20 from Cayman (#1)
[5.10.11 21:09:06] api.bitcoin.cz rejected block 21 from Cayman (#1)
[5.10.11 21:09:11] api.bitcoin.cz accepted block 7382 from Cayman (#1)
[5.10.11 21:09:24] api.bitcoin.cz accepted block 7383 from Cayman (#1)
[5.10.11 21:09:34] api.bitcoin.cz accepted block 7384 from Cayman (#1)
[5.10.11 21:09:36] api.bitcoin.cz accepted block 7385 from Cayman (#1)
[5.10.11 21:09:39] api.bitcoin.cz accepted block 7386 from Cayman (#1)
[5.10.11 21:10:06] api.bitcoin.cz rejected block 22 from Cayman (#1)
[5.10.11 21:10:12] api.bitcoin.cz accepted block 7387 from Cayman (#1)
[5.10.11 21:10:13] api.bitcoin.cz accepted block 7388 from Cayman (#1)
[5.10.11 21:10:36] api.bitcoin.cz rejected block 23 from Cayman (#1)
[5.10.11 21:11:18] api.bitcoin.cz accepted block 7389 from Cayman (#1)
[5.10.11 21:11:20] api.bitcoin.cz accepted block 7390 from Cayman (#1)
[5.10.11 21:11:36] api.bitcoin.cz rejected block 24 from Cayman (#1)
[5.10.11 21:11:52] api.bitcoin.cz accepted block 7391 from Cayman (#1)
[5.10.11 21:12:04] api.bitcoin.cz accepted block 7392 from Cayman (#1)
mhash: 399,3/397,8 | accept: 7392 | reject: 24 | hw error: 4
the same goes for my cgminer ...
Code:
[2011-10-05 21:09:39.777347] Share c2ea6e52 rejected from GPU 0 thread 1
[2011-10-05 21:09:46.569505] Share 1e13455e accepted from GPU 0 thread 0
[2011-10-05 21:09:51.408267] Share 18927acb accepted from GPU 0 thread 1
[2011-10-05 21:10:01.744574] Share dbec8742 accepted from GPU 0 thread 1
[2011-10-05 21:10:08.810689] LONGPOLL detected new block on network, waiting on fresh work
[2011-10-05 21:10:10.067928] Share 85c6f20b rejected from GPU 0 thread 1
[2011-10-05 21:10:19.045439] Share 9ca6686c rejected from GPU 0 thread 1
[2011-10-05 21:10:22.067179] Share 0b7a6c8e accepted from GPU 0 thread 0
--- SNIP ---
[2011-10-05 21:14:27.277004] Share d3a0a91f accepted from GPU 0 thread 1
[2011-10-05 21:14:38.154782] LONGPOLL detected new block on network, waiting on fresh work
[2011-10-05 21:14:46.392136] Share 9525f355 rejected from GPU 0 thread 0
[2011-10-05 21:14:52.611063] Share c16f8599 rejected from GPU 0 thread 0
[2011-10-05 21:15:06.256101] Share bfb7882f accepted from GPU 0 thread 0
--- SNIP ---
 A:1165  R:21
are you aware of that?
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 05, 2011, 07:35:46 PM
 #3610

Hey slush ... after what seemed as few restarts on the 'beta' pool i'm now getting quite a few rejects ... while still getting accepts

Thanks, there was really small glitch on beta. It's fixed now.

slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 05, 2011, 11:03:11 PM
 #3611

I did few pool restarts today because of fine tuning LP, you probably got some connection errors and rejects. Everything is stable now.

I also disabled LP for some miners (user agents) which didn't handle LP correctly. Namely Ufasoft miner, which don't follow LP specification. I reported it to ufasoft and he already fixed that in development version. So I'll enable LP for ufasoft soon again.

jaybones
Member
**
Offline Offline

Activity: 80


View Profile
October 06, 2011, 01:44:22 AM
 #3612

Im new to the mining thing, but i think these changes you made is preventing me to mine all together.
I'm using GUIMiner - V2011-8-24 with Nvidia gtx 560 ti.
with flag -cuda -gpugrid 384

for past 4 days i was mining fine.
i came home from work with all kinda stales and rejects..

I tried stopping and starting it back up but now all i get are rejects

I'm Accepted 48(48) past past 10min

Is there a newer Version of GuiMiner?

thanks
jay
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 06, 2011, 02:11:44 AM
 #3613

Im new to the mining thing, but i think these changes you made is preventing me to mine all together.
I'm using GUIMiner - V2011-8-24 with Nvidia gtx 560 ti.
with flag -cuda -gpugrid 384

for past 4 days i was mining fine.
i came home from work with all kinda stales and rejects..

I tried stopping and starting it back up but now all i get are rejects

I'm Accepted 48(48) past past 10min

What means Accepted 48(48)? Isn't that "all shares were accepted"? I'm watching logs and all your last 6 shares are accepted without a problem.

I few times restarted pool because of today updates. Maybe those rejects in your log are old?

Edit:
Copy&paste from Q&A of GuiMiner:
Quote
Q: What does it mean in the summary panel when the shares say something like 1000 (150) accepted?
A: That means 1000 shares total were accepted, including 150 in the last hour.

So yes, all those shares are accepted.

jaybones
Member
**
Offline Offline

Activity: 80


View Profile
October 06, 2011, 02:26:10 AM
 #3614

Yea,
I just restarted it again.
i turn off LP and cleared out my log. 

Things look ok again..

Thanks for quick response.

I'm still very new to this and Wish GUIMiner had better log then Console..

or maybe i just to find out how to monitor what i'm doing better..

jay
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 06, 2011, 02:29:56 AM
 #3615

jaybones: LP should work nicely in your miner. Consider to turn it again at least for test. Those stales were probably from previous pool restarts. Please tell me then if LP works for you, what was your stale ratio (and on how much shares it calculated that ratio).

Edit: I'm trying the same version of GUIMiner and don't see any issues with LP. Let's turn it on again and tell me if it works for you, too.

jaybones
Member
**
Offline Offline

Activity: 80


View Profile
October 06, 2011, 03:54:48 AM
 #3616

OK,
LP back on.
i'm going to bed. before i goto work tomorrow i'll check if i get any stale's..
as of right now i'm 0(0)
I let u know.  thanks.
jay
pekv2
Hero Member
*****
Offline Offline

Activity: 770



View Profile
October 06, 2011, 04:03:09 AM
 #3617

OK,
LP back on.
i'm going to bed. before i goto work tomorrow i'll check if i get any stale's..
as of right now i'm 0(0)
I let u know.  thanks.
jay

I was waiting for this to come up.

Sorry bud, your gonna have to count the rejected in the console. The newest GUIminer does not detect stales 0(0) on the gui side of the app.

Last post.
https://bitcointalk.org/index.php?topic=3878.msg559232#msg559232

&

https://bitcointalk.org/index.php?topic=3878.msg479302#msg479302
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 06, 2011, 04:07:44 AM
 #3618

pekv2: Does pool work for you now somehow? With LP on/off?

pekv2
Hero Member
*****
Offline Offline

Activity: 770



View Profile
October 06, 2011, 04:21:22 AM
 #3619

pekv2: Does pool work for you now somehow? With LP on/off?

LP is off, and is doing great. I was gone for a couple hours, came back, one of my cards stopped mining as I think it got to hot in the room. Warmer day today vs last 7 days. Cranked the box fan, and 120mm fan up. Doing wonders.

Code:
2011-10-05 19:37:41: Listener for "XFX Card": api2.bitcoin.cz:8332 05/10/2011 19:37:41, Verification failed, check hardware!

Edit:

I haven't troubleshooted my network for LP yet, I'm gonna get on it this week.

jaybones
Member
**
Offline Offline

Activity: 80


View Profile
October 06, 2011, 11:40:14 AM
 #3620

Well Slush,
Its morning about to head to work..
Looks like with LP on  i got 1 error.
Code:
2011-10-06 02:41:08: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}

This only thing that popup in last 7 hours.
So everything looks Good  Smiley


later,
jay
Pages: « 1 ... 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 [181] 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 ... 1104 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!