Last 4 blocks found are all still processing reward...
Anything we should be worried about?
Anything we should be worried about?
No, I just forgot (again) to setup maintenance in crontab after some changes. Blocks are already processed, sorry.
Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 974. (Read 4382653 times)
October 10, 2011, 12:49:33 PM
No, I just forgot (again) to setup maintenance in crontab after some changes. Blocks are already processed, sorry.
October 10, 2011, 12:16:36 PM
Last 4 blocks found are all still processing reward...
Anything we should be worried about?
Anything we should be worried about?
October 08, 2011, 12:53:59 PM
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.
Quote
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. October 08, 2011, 12:04:46 PM
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%" :-).
October 08, 2011, 12:02:10 PM
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.
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.
October 08, 2011, 10:58:48 AM
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 
.
. October 08, 2011, 06:44:21 AM
Still been getting this Error..
Everything still runs fine.
jay
Quote
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}
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
October 06, 2011, 07:48:39 PM
np at all, thanks.
October 06, 2011, 07:40:59 PM
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.
October 06, 2011, 07:18:58 PM
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')
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')
October 06, 2011, 09:32:49 AM
Good news, guys! Thanks :-)
October 06, 2011, 06:40:14 AM
Well Slush,
Its morning about to head to work..
Looks like with LP on i got 1 error.
This only thing that popup in last 7 hours.
So everything looks Good
later,
jay
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
October 05, 2011, 11:21:22 PM
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.
October 05, 2011, 11:07:44 PM
pekv2: Does pool work for you now somehow? With LP on/off?
October 05, 2011, 11:03:09 PM
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
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://bitcointalksearch.org/topic/m.559232
&
https://bitcointalksearch.org/topic/m.479302
October 05, 2011, 10:54:48 PM
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
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
October 05, 2011, 09:29:56 PM
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.
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.
October 05, 2011, 09:26:10 PM
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
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
October 05, 2011, 09:11:44 PM
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
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.
A: That means 1000 shares total were accepted, including 150 in the last hour.
So yes, all those shares are accepted.
October 05, 2011, 08:44:22 PM
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
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
Jump to: