Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 156. (Read 499835 times)

I'm seeing the same, although first the login form is sending me to https://www.eclipsemc.com/confirm_login_test.php which gives 404.  If I edit the form to go to confirm_login.php I get the Google Auth failed error.

Not a huge problem, I expect it will be fixed soon, and the extra security options are appreciated, thanks.

[/quote]

I reported this via PM here; I don't think I have your email address.  I am locked out of my account, having never enabled Google Auth or in fact ever having heard of it until coming here and reading the above after finding myself locked out with a "Google Authentication Failed" message.
[/quote]

same shit here

I clicked the Google Auth radio button and saved my changes.  Then, I clicked the Set GA Token link and it brings me to a blank page except for "data cannot be empty! back."

Thanks for spending the time for us to be able to secure our accounts.

I reported this via PM here; I don't think I have your email address.  I am locked out of my account, having never enabled Google Auth or in fact ever having heard of it until coming here and reading the above after finding myself locked out with a "Google Authentication Failed" message.

Good idea Krusaderx!  The IPs are unlikely to change any time soon, unless we somehow run into a problem like we had several months back with one ip failing to route properly every now and then (it was very strange) - should likely be static for awhile.

In other news, in addition to adding Yubikey as a 2nd factor authenticator, I have now activated Google Authenticator for those of you who don't want/don't have a hardware token to use.  You can now download the Google Authenticator from your favorite market (Either Android Market, Apple Market or BlackBerry Store), install it on your mobile device and use it as a 2nd factor authenticator.

See this link for more information: http://support.google.com/accounts/bin/answer.py?hl=en&answer=1066447

To activate GA, you will need to go to My Account, click the Google Auth radio button and save your changes. Then you will need to generate a GA token, with the link right below the 2F Auth for Google Authenticator.  You will be presented with a QR code that you scan into Google Authenticator and it will automatically configure everything you need.

I've tested it out, but I am tired and it's late, so it's entirely possible I missed something.  For anyone brave enough to give it a try, let me know what you think.  If for some reason you get locked out of your account through a bug, send me an email and I will unlock your account as soon as I wake up.  I am going to bed now though! 

Quite a day for blocks! 

An idea for IP vs DNS; set up w/ the IP as your primary, and then w/ DNS as your backup.  For the foreseeable future, you'll go right to the pool by IP, but if Inaba has to switch IPs for whatever reason (sweet hosting deal?), you'll fall-back to resolving DNS to find the pool.  If you notice that you're on your backup pool, you'll know to update the IP on your primary.

This protects you from unreliable DNS most of the time, and in the unlikely event of Inaba changing IPs, you will at least have a shot of finding the pool via DNS.

@Inaba: Thanks, I will report back, if the problem persists!

@NetworkerZ: The solution is so dead simple, that it simply didn't make it into my consideration but you are right, if one doesn't want to rely on DNS as  an additional source of failure, that would be the solution. Let's hope, Inaba doesn't try to change IPs without prior notice....

not sure exactly, when blackhat mentioned having trouble I just glanced at the 2hrs of reported hashes that were still visible and saw there was 2 instances were it had reconnected. It was not long at all though or I would heard it taking a break on the job. Would have never of noticed if not for it being mentioned. Been running fine for me.

If you don't want to wait for DNS reply, just insert the IP of Eclipse into the hosts file!

Btw. Found another BLock again ;-) 10 blocks in 13 hours!

Greetz
NetworkerZ

Avg Luck: 42.57%! First time above median I think.

Yes I noticed.... must be because I went solo 1.5 days ago.. since then the pool has hit about 18 blocks

Blackhat: I have made some changes to DNS.  Let me know if that does not clear up the problem.  It may take a while for it to propagate to you, though.  Google (8.8.8. still has old info as of this post time.

stoppots: Can you elaborate on what you mean by disconnects?  How long do they last?

looks like I have had 2 disconnects in the past couple of hours, not sure tho man, I hadn't noticed till I looked just now

might try pointing to these addys instead

For US residents:
us.eclipsemc.com

For EU residents:
eu.eclipsemc.com

For Pacific Rim / Asia / Australia
pacrim.eclipsemc.com

NB: Same thing happens on us.eclipsemc.com an eu.eclipsemc.com, so the miners are affected, too.

Before I get asked: Yes, I've checked all other possibilites that could be on my side, so I'm pretty sure that it's out of my control. My servers (miners) are situated in germany.

Man hittin blocks like crazy

I'm having severe connection issues, probably with the DNS Servers that host eclipsemc.com.

After around ~15 seconds, I get this error:

www:~# ping www.eclipsemc.com
ping: unknown host www.eclipsemc.com

This can be reproduced on various servers around here, and even with google DNS (8.8.8..

This error has caused an 8 hr outage for the second time, and that's not good. Is there anything that can be done? Can I be of any help with this?

Thanks in advance.

Among other statistical things, it's also dependent on the 'bitcoind' connection to the rest of the bitcoin network, the number of connections it has and also issues like the network delay from 'bitcoind' to those it's connected to.
It also doesn't help if the miner that generated the block is slow to notify the pool or the pool has ANY delay in notifying the 'bitcoind'
So basically, each pool will have different expectations.

I've completely re-written the block solve notification code.  There should be no more false alerts (or lack thereof on actual alerts) on block solves.  Knock on wood ...  Sorry to those who ended up getting several emails/SMS's that were duplicates.  Had a couple hiccups but should be smoothed out now.

*EDIT*

Now the alerts are really, really working.  I finally found the bug that was plaguing the alerts... jeez.  It was a long standing bug, too, apparently, because that part of the code I haven't touched in months.  I can't believe it's taken this long to become so pervasive.  Anyway, it's stomped now.

My changes have the added bonus of making block processing about 20x faster, too... yay!  Block processing should be almost instantaneous now.

With the huge volume of blocks your pool finds can you give a probabilty of invalid blocks occuring in close succession based on your past results?