doublec (OP)
Legendary
 Offline
Activity: 1078
Merit: 1005
|
 |
June 13, 2013, 11:53:18 AM |
|
above your comment in the Bitminter vs. Eligius thread. Any explanation why the orphan rate is much higher than expected. There are 8 orphan out of 188 blocks since the DGM-switch. This equals 4.2% ophans, much more than normal! Now it matters, because you are not paying orphan blocks anymore. Taking your numbers, the effective Bitparking fee is 4,7%.
I've mentioned this before but not all those orphans were real orphans but were the result of the pool paying out on stale submissions that solved a block. I flagged them as orphans in the pool accounting system as it's the only way to note in the reserves that a payment was made but no income received. The bug causing this was fixed before the switch to the pool not paying for orphans. Since the switch there have been two orphan blocks, both genuine close races. The most recent one I think our block was submitted something like 10 seconds after the racing block - not much you can do about that. |
|
|
|
|
|
|
|
|
|
No Gods or Kings. Only Bitcoin
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
Lucko
|
|
June 13, 2013, 11:57:57 AM |
|
What about TX fees? Are already paid out?
EDIT: Did you notice the last news on the page is 2013-02-14. All news after that are gone...
|
|
|
|
|
doublec (OP)
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
June 13, 2013, 12:00:35 PM |
|
What about TX fees? Are already paid out?
No, transactions fees are not yet paid out. |
|
|
|
|
|
demkd
|
|
June 14, 2013, 08:17:50 AM |
|
Bitcoin withdraw failed with "Fatal error: Error fetching URL"
Daemon is down?
|
|
|
|
|
doublec (OP)
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
June 14, 2013, 08:43:16 AM |
|
Bitcoin withdraw failed with "Fatal error: Error fetching URL"
Daemon is down?
Yes, back up now. |
|
|
|
|
|
Zalfrin
|
|
June 14, 2013, 03:29:23 PM |
|
getwork seems to have gone down again. I've switched back over to stratum-proxy for now.
|
|
|
|
|
not.you
Legendary
Offline
Activity: 1726
Merit: 1018
|
|
June 14, 2013, 03:39:37 PM |
|
Is getwork down? My getworkers are not working  |
|
|
|
|
|
Zalfrin
|
|
June 14, 2013, 04:06:42 PM |
|
Is getwork down? My getworkers are not working Check the main page, the 0 MH/s rate directed at the getwork port indicates it is down.  You can try using stratum_proxy, though it is quite buggy for me. Not as efficient as connecting straight to the getwork port, but better than nothing. Theoretically, it ought to be MORE efficient I believe, but I get a lot of errors from the proxy. |
|
|
|
|
bitcoinmike
Newbie
Offline
Activity: 24
Merit: 0
|
|
June 14, 2013, 08:02:47 PM |
|
This is not working for me either. I just tried. Bitcoin withdraw failed with "Fatal error: Error fetching URL"
Daemon is down?
Yes, back up now. |
|
|
|
|
SirMintALot
Full Member
Offline
Activity: 140
Merit: 100
In POS we trust
|
|
June 14, 2013, 10:23:10 PM |
|
Stratum isn't working correctly too:  Bitparking is pool 1 |
BTC: 142BHpdq4wey7PC3Cp5QiUoshF19u3yvHN LTC: LbiEUDYjohwpXnv1Gd4LvdGr1Jr1M5Usjc NMC: N3eeYkWqeLFWBJRmS3WyU1zz6WgKkjEVtb
IXC: xtR8uc2EFGWFJgrVEgZZ5yvRsWKhwAg8ZH DVC: 18oVWfSqHjvhJEuHHxsDpCfBeDMuLWyh5p CLR: CGZGWW16sooX69PJBEtJH2Xmo4KFupkow7
PPC: PLJ5uzFw21FkKdSrmfccT3MqubSfSB4soE YAC: Y7FM89AiFhWKBcXh2BzzRaw4eUAYkreXbs LBW: 5ygEWM7dMjeUV2sBeppTvkTTXCkeREKqf2
I0C: jatiogvXJYhK7auegbjPnQRV3kQgFvz482 JPU: JE7fhhPfP1Kjyd1hj8zevNsf7THeMqHo6A NVC: 4Hvecu2fzC2rCwYbKBeYXr8y9pdAZLFZHH
|
|
|
|
mitty
|
|
June 14, 2013, 10:24:06 PM |
|
Looks like the site is down as well; "502 Bad Gateway"
|
|
|
|
|
not.you
Legendary
Offline
Activity: 1726
Merit: 1018
|
|
June 14, 2013, 10:30:11 PM |
|
Looks like somebody gave 'er the 'ol reboot.
|
|
|
|
|
SirMintALot
Full Member
Offline
Activity: 140
Merit: 100
In POS we trust
|
|
June 14, 2013, 10:40:24 PM |
|
It's alive again  |
BTC: 142BHpdq4wey7PC3Cp5QiUoshF19u3yvHN LTC: LbiEUDYjohwpXnv1Gd4LvdGr1Jr1M5Usjc NMC: N3eeYkWqeLFWBJRmS3WyU1zz6WgKkjEVtb
IXC: xtR8uc2EFGWFJgrVEgZZ5yvRsWKhwAg8ZH DVC: 18oVWfSqHjvhJEuHHxsDpCfBeDMuLWyh5p CLR: CGZGWW16sooX69PJBEtJH2Xmo4KFupkow7
PPC: PLJ5uzFw21FkKdSrmfccT3MqubSfSB4soE YAC: Y7FM89AiFhWKBcXh2BzzRaw4eUAYkreXbs LBW: 5ygEWM7dMjeUV2sBeppTvkTTXCkeREKqf2
I0C: jatiogvXJYhK7auegbjPnQRV3kQgFvz482 JPU: JE7fhhPfP1Kjyd1hj8zevNsf7THeMqHo6A NVC: 4Hvecu2fzC2rCwYbKBeYXr8y9pdAZLFZHH
|
|
|
doublec (OP)
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
June 14, 2013, 10:46:07 PM |
|
Looks like somebody gave 'er the 'ol reboot.
Yes, the bitcoind crashed. I'm having a few problems with the recent upgrade to bitcoind 0.8.2. I'm running under the debugger at the moment to try and see what's going on. Worst case I may need to rollback the last update. |
|
|
|
|
|
pat1900
|
|
June 14, 2013, 11:21:00 PM |
|
Yes, the bitcoind crashed. The amazing thing is that the pool server remembered those few shares that got lost during the crash. That's why after the server recovered the hashrate went up for a moment despite my rig automatically switched to a different pool: 22:30: {"hashrate":540.609,"pps":0.00000000,"score":4312, ... 22:31: {"hashrate":544.634,"pps":0.00000000,"score":4318, ... 22:32: {"hashrate":533.885,"pps":0.00000000,"score":4318, ... By the way, I wish the payout process from the "crashed" exchange.bitparking.com could run as smoothly as doublec's pool software ... http://bitcointalk.org/index.php?topic=165153.80 |
USD: 0.000 BTC ▶ EUR: 0.000 BTC ▶
|
|
|
doublec (OP)
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
June 15, 2013, 12:08:16 AM |
|
The amazing thing is that the pool server remembered those few shares that got lost during the crash.
That's why after the server recovered the hashrate went up for a moment despite my rig automatically switched to a different pool:
Share's are kept in a queue and if they fail to transmit to the database server they wait until the database becomes available again. When restarting the pool services this results in a bunch of shares in the queue getting submitted when the database server comes up again and it often shows up as an increase in hash rate like that. |
|
|
|
|
doublec (OP)
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
June 15, 2013, 04:24:34 AM |
|
There was a pool restart just now as I rolled back to bitcoin 0.8.1 to see if the recent upgrade is the cause of the instabilities.
|
|
|
|
|
|
aggster
|
|
June 15, 2013, 10:17:06 AM |
|
please could you lower your withdraw fees, its far higher than other pools and takes an eternity using my single gpu, especially with the difficulty rising so rapidly.
|
|
|
|
|
doublec (OP)
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
June 15, 2013, 10:46:51 AM |
|
please could you lower your withdraw fees, its far higher than other pools and takes an eternity using my single gpu, especially with the difficulty rising so rapidly.
What withdraw fee? There isn't one. |
|
|
|
|
|
Armchair Miner
|
|
June 15, 2013, 11:03:29 AM |
|
I was (as of a few minutes ago) still getting "stratum disconnect" messages as reported above on this page. At the same time, the ASICMINER USB Erupters report a few HW errors through cgminer. The rate of HW errors comes to about 10% which is way above the usual 1.5%.
Just restarted and am watching the screen. Will report if the situation changes.
|
|
|
|
|
