[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[jaybones]

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]

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]

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]

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]

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

[pekv2]

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]

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 


later,
jay

[slush]

Good news, guys! Thanks :-)

[pekv2]

Totally new error for me. Never seen it before. I'm sure it will be fine though.

Code:

2011-10-06 18:53:47: Listener for "XFX Card": api2.bitcoin.cz:8332 06/10/2011 18:53:47, Unhandled exception Failed to submit share
2011-10-06 19:01:07: Listener for "XFX Card": api2.bitcoin.cz:8332 06/10/2011 19:01:07, Unhandled exception (1040, 'Too many connections')
2011-10-06 19:01:32: Listener for "XFX Card": api2.bitcoin.cz:8332 06/10/2011 19:01:32, Unhandled exception (1040, 'Too many connections')

[slush]

Yes, there was database lockup because of failed periodic backup, so pool was down for few minutes, until monitoring woke me up. I stopped it manually, pool is running in normal mode again. Tomorrow I'll investigate what exactly happen. I'm really sorry for this issue.

[pekv2]

np at all, thanks.

[jaybones]

Still been getting this Error..

2011-10-07 04:58:10: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 06:12:03: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 09:26:31: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 09:56:01: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 10:26:17: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 12:30:13: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 14:22:42: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 16:31:02: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 17:26:17: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 18:09:11: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 18:32:19: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 18:32:24: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 18:41:41: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-07 19:20:17: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-08 04:59:59: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-08 05:50:01: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}
2011-10-08 07:00:02: Listener for "Nivida miner": Server sent: {"result": false, "id": "1", "error": null}

Everything still runs fine.

jay

[slush]

jaybones: I found that problem, I'm working on fix. It's actually race condition in bitcoind, so it was harder to find it out, but pool will be fixed soon .

[dbrane]

Slush, after the recent changes I'm getting higher-than-normal number of rejects (around 32.5%) and occasionally LP errors, with a peculiar pattern:

08/10/2011 14:27:29, Setting server (dbrane.monster @ api.bitcoin.cz:8332)     
api.bitcoin.cz:8332 08/10/2011 14:27:30, LP connected to api.bitcoin.cz:8332   
api.bitcoin.cz:8332 08/10/2011 15:27:30, long poll: IO error                   
api.bitcoin.cz:8332 08/10/2011 15:27:31, LP connected to api.bitcoin.cz:8332   
api.bitcoin.cz:8332 08/10/2011 16:27:32, long poll: IO error                   
api.bitcoin.cz:8332 08/10/2011 16:27:33, LP connected to api.bitcoin.cz:8332   
api.bitcoin.cz:8332 08/10/2011 17:27:33, long poll: IO error                   
api.bitcoin.cz:8332 08/10/2011 17:27:34, LP connected to api.bitcoin.cz:8332   

Looks like I'm experiencing connection issues 27 minutes past the hour every hour - is there anything which might explain it on your end?

Cheers.

[dbrane]

Slush, after the recent changes I'm getting higher-than-normal number of rejects (around 32.5%) and occasionally LP errors, with a peculiar pattern:

Err, that should have read "around 2.5%" :-).

[slush]

Slush, after the recent changes I'm getting higher-than-normal number of rejects (around 3.25%)

There was next big update of pool today, but some errors appeared, so I had to revert those changes. Unfortunately it mean there was outage around 15.00 UTC today. That might explain that higher rate. Now it should be back in normal.
 

and occasionally LP errors, with a peculiar pattern:

It looks like something is cutting longpolling connection between your computer and pool. For example my phone operator is closing tcp connections every ~10 minutes, but I don't expect that you're mining thru mobile phone .  Pool isn't closing LP connection in any fixed period like this, so - no, I don't think it's on my side.

[digital]

Last 4 blocks found are all still processing reward...

Anything we should be worried about?

[slush]

Last 4 blocks found are all still processing reward...
Anything we should be worried about?

No, I just forgot (again) to setup maintenance in crontab after some changes. Blocks are already processed, sorry.

[Iyeman]

How is merged mining coming along?

[slush]

How is merged mining coming along?

Pool is doing merged mining already, we have around 160 NMC blocks at this time. Unfortunately there were many technical issues to solve, so I didn't finish anything else than mining itself. I'm now working on GUI for entering namecoin wallets and then will need to finish rewarding system. Everything will be very simple at first moment, but it will be soon .

Official announcement will probably come later today.