[OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 #

[3phase]

How long of a round are you currently going on? I don't have miners at Eligius atm.

I just didn't see any "LP: New work pushed" with Phoenix on Eligius for an hour or so (hundreds of shares accepted in the meantime). I thought WTF?

So I switched a miner to Slush pool, watched the new block messages appearing there, but no such messages on my Eligius miners. I let it run for an hour again to be sure.

Switched them all from Eligius, no use mining if no blocks can be  found.

[1713238357]

1713238357

[1713238357]

1713238357

[1713238357]

1713238357

[1713238357]

1713238357

[1713238357]

1713238357

[Luke-Jr]

It seems like Eligius will NOT find a block, unless something gets corrected. I am mining at Slush also, I get the new block notifications there, but no such notifications on Eligius.

Thanks for the heads-up (in the future, IRC/phone is much faster to get my attention). I think I have a semi-fix for this issue for when we deploy 4 (on new hardware). In the meantime, 3 is caught up again. Shares were still counted as usual, and there were no negative side effects (though could have been if it went on too long).

[anodyne]

So maybe "maximum reward" is the amount of BTC we will be awarded in the future, if the pool has a few lucky rounds?

Yes

Isn't it the opposite... the pool had lucky rounds before, and the maximum reward is the amount you get back from the overhead if the current round ends right now?

Edit: I got that backwards. I blame it on just having gotten out of bed with a fever... 


Anyway, even though the pool stats won't admit it yet, it seems that a block was produced, and that outstanding EU payments are included: http://blockexplorer.com/b/134863 (4 confirmations atm)

[shamathana]

I'm still waiting my unpaid EU balance. The US one was received promptly when Luke-Jr said it would, but nothing yet for EU.

it took quite a while, but mine are all through now.

[zenmetsu]

btw,

if anyone else is experiencing network wonkiness trying to connect to eligius, you might want to consider a proxy.  if you have servers at one site that are connecting reliably and another site that is failing to connect to mining.eligius.st even though ping works, you can try setting up an ssh tunnel to eligius through your working hosts.  this has helped a few individuals and I have no idea what is going on from a network perspective on the server end.

if you do not have a remote host that is working, and you are experiencing connectivity issues and you are sure that the pool is up (according to the website), you can try doing what I did...

Install Tor, get it running, say, on the default port 9050... then fire off socat like this in another terminal:
socat TCP4-LISTEN:8399,fork SOCKS4A:localhost:mining.eligius.st:8337,socksport=9050

once socat is up (there will not be output to the console), simply direct your miners to localhost:8399 and you should get in without problems.  I have been running like this for several hours now and have seen zero negative impact to hashrate or invalid counts.  This has completely eliminated my issue of idle miners.

[anodyne]

I had one miner failing to connect intermittently and realized that one was connected to mining.eligius.st, while the other machine has been pointed to s3.mining.etc... since the change from EU server. So, I pointed the first one to that address as well, and I haven't noticed any connection problems since then.

If it has anything to do with the local connections or the redirection on the server end is beyond me, though.

[Man From The Future]

I had one miner failing to connect intermittently and realized that one was connected to mining.eligius.st, while the other machine has been pointed to s3.mining.etc... since the change from EU server. So, I pointed the first one to that address as well, and I haven't noticed any connection problems since then.

If it has anything to do with the local connections or the redirection on the server end is beyond me, though.

All now appear to point to teh same IP, ending in .78.7, although a while ago one pointed to .78.8. :S

luke-jr, which is the correct server?

[bogeyman]

I'm still waiting my unpaid EU balance. The US one was received promptly when Luke-Jr said it would, but nothing yet for EU.

it took quite a while, but mine are all through now.

I received mine EU balance yesterday. Just wait for the next block...

[Mr2001]

Any idea why the pool has missed its chance to pay me on the last three blocks?

http://imgur.com/YBhX9.png

[Luke-Jr]

Any idea why the pool has missed its chance to pay me on the last three blocks?

Payouts are processed 50 BTC (+ txn fees) at a time, choosing the addresses which have been waiting the longest first. Since our last 3 blocks were rather long, the pool rewarded over 50 BTC per block, and there's a bit of a backlog. When we get to short blocks, it will catch up again.

[fxgmblr]

Any idea why the pool has missed its chance to pay me on the last three blocks?

Payouts are processed 50 BTC (+ txn fees) at a time, choosing the addresses which have been waiting the longest first. Since our last 3 blocks were rather long, the pool rewarded over 50 BTC per block, and there's a bit of a backlog. When we get to short blocks, it will catch up again.

how much is the transaction fee?

[Yeti]

Depends on the transactions that are to be included in the block. These are transaction fees that Bitcoin users pay, i.e. the pool receives them and pays them to miners.

[strictlyfocused]

btw,

if anyone else is experiencing network wonkiness trying to connect to eligius, you might want to consider a proxy.  if you have servers at one site that are connecting reliably and another site that is failing to connect to mining.eligius.st even though ping works, you can try setting up an ssh tunnel to eligius through your working hosts.  this has helped a few individuals and I have no idea what is going on from a network perspective on the server end.

if you do not have a remote host that is working, and you are experiencing connectivity issues and you are sure that the pool is up (according to the website), you can try doing what I did...

Install Tor, get it running, say, on the default port 9050... then fire off socat like this in another terminal:
socat TCP4-LISTEN:8399,fork SOCKS4A:localhost:mining.eligius.st:8337,socksport=9050

once socat is up (there will not be output to the console), simply direct your miners to localhost:8399 and you should get in without problems.  I have been running like this for several hours now and have seen zero negative impact to hashrate or invalid counts.  This has completely eliminated my issue of idle miners.

You sir are a gentlemen and a scholar.  I managed to use your instructions and I can now mine any pool over any port I feel like behind a rather restrictive firewall.

[Luke-Jr]

You sir are a gentlemen and a scholar.  I managed to use your instructions and I can now mine any pool over any port I feel like behind a rather restrictive firewall.

Do note that port 80 works on Eligius

[strictlyfocused]

You sir are a gentlemen and a scholar.  I managed to use your instructions and I can now mine any pool over any port I feel like behind a rather restrictive firewall.

Do note that port 80 works on Eligius

Got to give credit where credit is due! No more long-pool errors while connected to eligius over port 80!  Thanks Luuke Jr!! 

[Luke-Jr]

We seem to be over the migration successfully. Eligius-Ti (aka Eligius-3) will be shutting down within the next 48 hours (possibly 24 hours) and given the usual sendmany payout. Please migrate your miners to Eligius-Su at your convenience (though if you choose to hold out for one last block on Ti, feel free). All DNS names are now pointed to Su except for Ti-specific names (s3, srv3, ti, cyan, 3). Once again, the recommended domain for mining is mining.eligius.st, and there is also test.mining.eligius.st if you prefer the most-experimental pool in the future.

Due to moving DB engines, all stats are now only available for the new Eligius-Su pool except for my raw JSON data.

If you have any trouble, please let us know on IRC!

[josell]

Is the site shutdown?

[zenmetsu]

You sir are a gentlemen and a scholar.  I managed to use your instructions and I can now mine any pool over any port I feel like behind a rather restrictive firewall.

Glad that I could help.  Some people might use this to mine behind firewalls or, at their own peril, on business machines.  As Luke stated, port 80 works as well.  I still have the intermittent problems if I try port 80 so I'm sticking to my solution for the time being.

I really want to see this pool succeed.  I somewhat dislike proportional pools because they are quite easy for pool-hoppers to take advantage of.  I showed a few friends 'the light' this evening and they are moving their 2GH/s rigs over from btcguild for a few days to see how it pans out.  Hopefully they will stick around.  The more power, the better!

[Luke-Jr]

I just deleted all of Eligius-Ti's DNS entries, following it finding a block. If you really want to keep mining on Ti, you must use ghost.mining.eligius.st-- but don't do that unless you have a lot of hashpower and are prepared to lose all the work if it crashes! Everyone should be on Eligius-Su now.

There has been some trouble with the new bitcoind, so please call me (whois eligi.us) IM me (luke ... dashjr.org) if any of the following occur:

• Pool isn't responding to work
• No longpolls notices even when the Bitcoin network has new blocks
• Estimates stop increasing as you get more shares

On the other hand, the new bitcoind has some improvements, including aggressive connecting to other nodes on the network which should hopefully eliminate invalid blocks.

If anyone would like to help work out these bugs, please meet me on IRC.

[josell]

I still having faith and love for this pool, however, i'm frustrated about its inestability, which workers hate.