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

First, I have to admit that I haven't been following the threads for a while.  So I really don't know what's been going on.
I've been using the us.eclipsemc.com server for several months.
Quite recently I could no longer connect.  I switched over to the eu server until the us server came back up but shortly thereafter I couldn't connect to it either.
I looked at the eclipse faq and saw that I was supposed to be using us1, us2 or us3.  I switched to us2 and was able to connect again.
Last night about 9:15 I lost connection again and still can't ping any of the servers but I don't see any mention of it in the forums.
I wondered if Comcast is blocking me but I don't know why they would or how I would test that.
Anyone have any idea what might be my problem?  I mean besides being an idiot.

This is the unluckiest time ever 

all I can say is look another longass(16hr) block of death( I foretold that one ) lol....is killing us =/

Is luck the percentile? ( exp (-shares/difficulty))

If so then shares = difficulty (which is the average shares) is 36.8% luck.

But 36.8% is not average luck. If you take the different luck values and calculate the average, it should be 50%.

Thanks... faq updated

I guess I didn't kill enough people tonight.  It was kind of a crappy night.

Yeah, 40% = average shares.

I figured it out.

Command line for diablominer:

diablominer-windows.exe -o us3.eclipsemc.com -u account_worker -p workerpassword -r 8337

Of course, you can add any flags as required to optimize your hardware performance.

I swear I tried that originally before I gave up, but I must have had a typo somewhere, or maybe I was trying to use my account password instead of the worker password.  But it's all good now

So 40% luck (whish is the average) is when shares = difficulty?

hopefully the BF3 session helps finish this block off :>

I would join, if I had enough RAM =P
AHAHA, stubborn blocks Ill tell ya!

So what's the proper command line for Diablominer to connect?  I will add it to the FAQ.

Since this block is taking so long, I'm going to fire up BF3 if anyone wants to join me.  Hopefully we can scare the block into submission.

Man, seems I was right when I said "round of death" so far almost 8hrs into this one...hahaha

Yes, I have used it to connect. 

Yeah, someone aksed me in a German Forum how to connect to your pool with fpgaminer. Could be useful if you add this info to the FAQ!

Greetz
NetworkerZ

As far as I know, you can.  I've never used Diablominer, but I'm pretty sure at least a few people are.

Can I use Diablominer to connect to this pool?

I thought it was simply a case of using the username and password with -u -p but it didn't seem to be connecting when I tried.  Sounds like a nice pool otherwise though.

Wow, our avg. luck is 200000 higher then the difficulty  Let's hope we'll have some good rounds soon!

Greetz
NetworkerZ

Seems there was an attack on the network.  The data center mitigated it at the ingress point... I'm waiting on more details now, I guess they are/were scrambling to filter the packets.  Thing should be back to normal for now.

Completely agree - I believe you are right that it's 69.30.209.1

Enigma

Down again..

For reference, here's a trace route from me when the server is reachable
------------------------------------------------------------
1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     2 ms     1 ms     1 ms  xx-xxx-xx-xxx.uvs.livnmi.sbcglobal.net [xx.xxx.xx.xxx]
  3    24 ms    23 ms    22 ms  xx-xxx-xxx-x.lightspeed.livnmi.sbcglobal.net [xx.xxx.xxx.x]
  4    26 ms    25 ms    26 ms  75.26.64.xxx
  5    26 ms    25 ms    24 ms  75.26.64.xx
  6    24 ms    24 ms    24 ms  12.83.32.133
  7    31 ms    31 ms    31 ms  cgcil03jt.ip.att.net [12.122.84.53]
  8     *        *        *     Request timed out. (I believe this is 192.205.37.178)
  9    34 ms    32 ms    32 ms  te0-5-0-7.ccr22.ord01.atlas.cogentco.com [154.54.44.165]
 10    44 ms    44 ms    44 ms  te0-0-0-3.ccr22.mci01.atlas.cogentco.com [154.54.30.101]
 11    45 ms    45 ms    44 ms  te0-1-0-0.mpd22.mci01.atlas.cogentco.com [154.54.30.154]
 12    45 ms    44 ms    44 ms  everest.demarc.cogentco.com [38.104.86.2]
 13    46 ms    45 ms    44 ms  69.30.209.1
 14    46 ms    47 ms    44 ms  208.110.68.114

Another Failed Trace Route to US3:
------------------------------------------------------------

traceroute to us3.eclipsemc.com (208.110.68.116), 30 hops max, 38 byte packets
 1  192.168.0.1 (192.168.0.1)  1.054 ms  0.676 ms  0.935 ms
 2  XX-XXX-XX-XXX.uvs.livnmi.sbcglobal.net (XX.XXX.XX.XXX)  2.250 ms  1.637 ms  1.947 ms
 3  XX-XXX-XXX-X.lightspeed.livnmi.sbcglobal.net (XX.XXX.XXX.X)  23.880 ms  23.647 ms  23.929 ms
 4  75.26.64.XXX (75.26.64.XXX)  25.876 ms  26.754 ms *
 5  75.26.64.XX (75.26.64.XX)  26.895 ms  25.437 ms  24.977 ms
 6  12.83.32.133 (12.83.32.133)  24.975 ms  24.616 ms  24.970 ms
 7  cgcil03jt.ip.att.net (12.122.84.53)  31.958 ms  31.626 ms  31.978 ms
 8  192.205.37.178 (192.205.37.178)  32.944 ms 192.205.37.174 (192.205.37.174)  32.509 ms 192.205.37.178 (192.205.37.178)  32.688 ms
 9  te0-0-0-1.ccr22.ord01.atlas.cogentco.com (154.54.1.97)  32.579 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com (154.54.5.1)  32.681 ms te0-0-0-1.ccr21.ord01.atlas.cogentco.com (154.54.1.1)  33.658 ms
10  te0-5-0-1.mpd22.ord01.atlas.cogentco.com (154.54.44.177)  32.559 ms te0-1-0-0.mpd22.ord01.atlas.cogentco.com (154.54.6.177)  32.684 ms te0-0-0-3.ccr22.mci01.atlas.cogentco.com (154.54.30.101)  45.642 ms
11  te0-2-0-0.mpd22.mci01.atlas.cogentco.com (154.54.30.158)  45.632 ms  48.633 ms te0-4-0-5.mpd22.mci01.atlas.cogentco.com (154.54.45.157)  45.966 ms
12  everest.demarc.cogentco.com (38.104.86.2)  44.694 ms  45.689 ms  45.966 ms
13  * * *
14  * * *
15  * 208.110.68.116 (208.110.68.116)  47.308 ms *
[root@miner23 ~]#

Yeah, it seems there's an upstream router down near 69.30.209.1 ... seems to be going in and out.  I think maybe a card on a router is going bad.  I submitted a support ticket, but I'm not sure it's part of my datacenters maintenance domain.

Thought you could use an update... currently down / no connection..

I could ping any site on the internet during this time - except for:
us.eclipsemc.com
us2.eclipsemc.com
us3.eclipsemc.com
www.eclipsemc.com

Miner:
--------------------------------------------------
[30/01/2012 23:46:03] Result: aa848d59 accepted
[30/01/2012 23:46:12] Result: b704819c rejected
[30/01/2012 23:46:23] Disconnected from server
[30/01/2012 23:46:27] Warning: work queue empty, miner is idle
[30/01/2012 23:46:28] Result: fda366a9 rejected
[30/01/2012 23:46:31] Result: 5bc08ece accepted
[30/01/2012 23:46:36] Failed to connect, retrying...
[30/01/2012 23:46:47] Failed to connect, retrying...
[30/01/2012 23:47:02] Failed to connect, retrying...
[30/01/2012 23:47:17] Failed to connect, retrying...
[30/01/2012 23:47:32] Failed to connect, retrying...
[30/01/2012 23:47:47] Failed to connect, retrying...
[30/01/2012 23:48:02] Failed to connect, retrying...
[30/01/2012 23:48:12] Connected to server
[30/01/2012 23:48:40] Disconnected from server
[30/01/2012 23:48:46] Warning: work queue empty, miner is idle
[30/01/2012 23:48:51] Failed to connect, retrying...
[30/01/2012 23:49:06] Failed to connect, retrying...
[30/01/2012 23:49:24] Failed to connect, retrying...
[30/01/2012 23:49:36] Failed to connect, retrying...
[30/01/2012 23:49:51] Failed to connect, retrying...
[30/01/2012 23:50:06] Failed to connect, retrying...
[30/01/2012 23:50:19] Connected to server
[30/01/2012 23:50:24] Disconnected from server
[30/01/2012 23:50:30] Warning: work queue empty, miner is idle
[30/01/2012 23:50:35] Result: ea144189 rejected
[30/01/2012 23:50:43] Failed to connect, retrying...
[30/01/2012 23:50:50] Failed to connect, retrying...
[30/01/2012 23:51:05] Failed to connect, retrying...
[30/01/2012 23:51:20] Failed to connect, retrying...
[30/01/2012 23:51:35] Failed to connect, retrying...
[30/01/2012 23:51:50] Failed to connect, retrying...
[30/01/2012 23:52:05] Failed to connect, retrying...
[30/01/2012 23:52:20] Failed to connect, retrying...
[30/01/2012 23:52:35] Failed to connect, retrying...

Trace Route: (Looks Like it falls apart once I get on cogentco's network)
--------------------------------------------------
Tracing route to us.eclipsemc.com [208.110.68.114]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     2 ms     1 ms     1 ms  xx-xxx-xx-xxx.uvs.livnmi.sbcglobal.net [xx.xxx.xx.xxx]
  3    24 ms    23 ms    22 ms  xx-xxx-xxx-x.lightspeed.livnmi.sbcglobal.net [xx.xxx.xxx.x]
  4    26 ms    25 ms    26 ms  75.26.64.xxx
  5    26 ms    25 ms    24 ms  75.26.64.xx
  6    24 ms    24 ms    24 ms  12.83.32.133
  7    33 ms    32 ms    34 ms  cgcil03jt.ip.att.net [12.122.84.53]
  8     *        *        *     Request timed out.
  9    33 ms    32 ms    32 ms  te0-5-0-7.ccr22.ord01.atlas.cogentco.com [154.54.44.165]
 10    45 ms    44 ms    44 ms  te0-0-0-3.ccr22.mci01.atlas.cogentco.com [154.54.30.101]
 11    46 ms    44 ms    44 ms  te0-1-0-0.mpd22.mci01.atlas.cogentco.com [154.54.30.154]
 12     *        *       46 ms  everest.demarc.cogentco.com [38.104.86.2]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17    45 ms     *        *     208.110.68.114
 18     *        *        *     Request timed out.
 19     *       45 ms     *     208.110.68.114
 20    45 ms     *        *     208.110.68.114
 21    46 ms     *        *     208.110.68.114
 22     *        *       46 ms  208.110.68.114

Hope the tracert helps.