Topic: [9 TH] Bitparking Pool, DGM 0%,vardiff,stratum,Merge Mining - page 38. (Read 163898 times)

Correct, transaction fees are currently used to build the pool reserves.

With regards to transaction fees I've not yet enabled the payment of these to users - the pool still keeps them - but I expect to do that in the next day or two once the orphan code has settled.

So fees are still kept by pool right?

The fact is my post is clearly time stamped, from the time I posted the "yellowed" out image, to the date  & time stamp in my last post.

Miner
https://github.com/TheSeven/Modular-Python-Bitcoin-Miner

Given that there are miners mining with 100+ GH/s I don't think that's true. Again, what miner are you using. Do you have backup pools configured. Can you paste, PM or email the command line and/or configuration file you use for the pool. There's obviously something wrong with either your setup or the pool's setup such that it doesn't like something your mining software is doing and it'd be good to work out what it is.

K the answer is a 'couple of hours', that is the apparent maximum the service is stable under a 4GH/s load...

2013-06-22 09:31:08.745   [200]   Hcfs_Stratum:    Stratum connection died:
2013-06-22 09:31:17.492   [200]   Hcfs_Stratum:    Stratum worker authorization timed out
2013-06-22 09:31:17.583   [200]   Worker_H01_03:    Exhausted keyspace!
2013-06-22 09:31:18.442   [350]   Worker_H01_04:    Found share: Hcfs_Stratum:000000021d00fba9f051baf49ea5c93b9597043ccd7b056dca8417ae0000009e00000000ddc4737 59cc28122b661db3a921ba97a15b145ce0b301186ce355c0d7805939051c4fe3b1a00de15:70fd37e9
2013-06-22 09:31:18.443   [200]   Worker_H01_04:    Hcfs_Stratum rejected share 70fd37e9 (difficulty 2.64623): Connection is not active
2013-06-22 09:31:19.499   [350]   Worker_FRA_07:    Found share: Hcfs_Stratum:000000021d00fba9f051baf49ea5c93b9597043ccd7b056dca8417ae0000009e0000000044993ac bea503dddad109fa02ba167228acc57c6079c60f14f152e69f066a55751c4fe311a00de15:d7a50408
2013-06-22 09:31:19.500   [200]   Worker_FRA_07:    Hcfs_Stratum rejected share d7a50408 (difficulty 1.21972): Connection is not active
2013-06-22 09:31:20.193   [200]   Worker_H01_10:    Exhausted keyspace!
2013-06-22 09:31:20.526   [200]   Worker_H01_09:    Exhausted keyspace!
2013-06-22 09:31:20.617   [200]   Worker_H01_11:    Exhausted keyspace!
2013-06-22 09:31:20.747   [200]   Worker_H01_07:    Exhausted keyspace!
2013-06-22 09:31:20.782   [200]   Worker_H01_08:    Exhausted keyspace!
2013-06-22 09:31:22.464   [200]   Worker_H02_01:    Exhausted keyspace!
2013-06-22 09:31:24.280   [350]   Worker_FRA_04:    Found share: Hcfs_Stratum:000000021d00fba9f051baf49ea5c93b9597043ccd7b056dca8417ae0000009e000000008e47716 0f0fe7087894e5d89188d0dc980da78a99701a93e2d39abfc5144cf2f51c4fe341a00de15:af40df20
2013-06-22 09:31:24.283   [200]   Worker_FRA_04:    Hcfs_Stratum rejected share af40df20 (difficulty 23.14465): Connection is not active
2013-06-22 09:31:26.158   [350]   Worker_FRA_04:    Found share: Hcfs_Stratum:000000021d00fba9f051baf49ea5c93b9597043ccd7b056dca8417ae0000009e000000008e47716 0f0fe7087894e5d89188d0dc980da78a99701a93e2d39abfc5144cf2f51c4fe341a00de15:9ddfae31
2013-06-22 09:31:26.159   [200]   Worker_FRA_04:    Hcfs_Stratum rejected share 9ddfae31 (difficulty 2.20841): Connection is not active
2013-06-22 09:31:26.364   [350]   Worker_H01_04:    Found share: Hcfs_Stratum:000000021d00fba9f051baf49ea5c93b9597043ccd7b056dca8417ae0000009e00000000ddc4737 59cc28122b661db3a921ba97a15b145ce0b301186ce355c0d7805939051c4fe3b1a00de15:5cac7d39
2013-06-22 09:31:26.364   [200]   Worker_H01_04:    Hcfs_Stratum rejected share 5cac7d39 (difficulty 1.82548): Connection is not active
2013-06-22 09:31:29.974   [200]   Worker_H02_02:    Exhausted keyspace!

Its about 500 shares low now and it was about 400 shares low 4 hours ago.  Does that sound about like the queue delay then if I am at 800Mhs?

There is a number of delays between a share being submitted and stats being shown on the stats page. The page itself is cached by the webserver for a number of seconds to reduce load. This means it is always behind. When you submit a share the share the result of that submit (rejected, accepted) goes into a queue. That share is submitted to the database when the queue is processed. This can take some time depending on pool load, database activities, etc. Once it's processed from the queue the web server can report it. This has been the apparent discrepancy in the times that others have reported issues.

I have been civil, and this is a poor attempt at deflection

What mining software are you using? Do you have backup pools configured with it? Do you have any logs you can provide to look into it?

I have also noted some lag on the stats page where a few refreshes inside of a minute or so will show just about everything changing except my shares, and then If I keep refreshing eventually the shares will jump by a significant portion.

I get quite a few emails and requests for support, it's helpful if you answer questions in a civil tone with the information requested so we can move towards a solution. If you're not willing to do this I suggest you mine elsewhere.

Why in your GUI can we not get  access to the orphaned data(block number)?

You know I'm on strat because we HAVE discussed this.. that is why you 'retired' some servers.

This most recent orphan was caused by a bitcoind issue that an emergency patch was supplied for. The issue caused the bitcoin daemon that the pool daemon was hidden behind to crash due to OOM and the pool daemon no longer received updates. It's unfortunate but not much could be done about bitcoind bugs.

2013-06-20 11:52   08:03:57   0.02035677   19,905   orphaned

This is the first I've heard of this. Are you on getwork or stratum?

'unknown-work' means work is being submitted to the pool that it didn't serve. What mining software are you using? Do you have backup pools configured with it? Do you have any logs you can provide to look into it?

This is the first I've heard of this. Are you on getwork or stratum?

Stratum worker authorization timed out

2013-06-21 18:31:22.532   [400]       *USERID*_Stratum2:    Successfully subscribed to Stratum service

2013-06-21 18:31:25.196   [350]   Worker_H01_12:    Found share:
2013-06-21 18:31:26.153   [200]   Worker_H01_03:    *USERID*_Stratum2 rejected share d90a6a63 (difficulty 1.54167): timed out
......
2013-06-21 18:31:27.354   [350]   Worker_FRA_03:    Found share: *USERID*_Stratum2:00000002724d64614a9b4728e0935112926ff809d2b5478e2f3984490000003a00000000b9bb6c2 19d3945c0836d8f309f98b421428ac9cc1b6b6b5f868d1a37a113d2dd51c42b511a00de15:b9352787
2013-06-21 18:31:27.355   [200]   Worker_FRA_03:    *USERID*_Stratum2 rejected share b9352787 (difficulty 10.32996): Connection is not active

I would like to know the % of orphans other pools have, because I still have the feeling that this pool has a fairly high ratio.

I would like to know the % of orphans other pools have, because I still have the feeling that this pool has a fairly high ratio.