Pages:
Author

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

hero member
Activity: 807
Merit: 500
Do our names get encoded into the solved block? If not, can it?

I feel the urge to be a little vein Smiley
Luke-Jr has mentioned BFGMiner's ability to do this in a few places (including the BFGMiner thread, obviously).  Note the correct word is vane, but if you are willing to use BFGMiner, then you should, theoretically be able to do this.  Since the pool is anonymous, it wouldn't make sense for the pool to do it for you even if it was a normal thing.
hero member
Activity: 896
Merit: 532
Former curator of The Bitcoin Museum
Do our names get encoded into the solved block? If not, can it?

I feel the urge to be a little vein Smiley
legendary
Activity: 1540
Merit: 1001
Could you put a total worker hash rate in the API?  Right now there is a value for each worker, but it's not raw, which makes adding it up difficult.  Adding a new row for totals would be great.

Also, could you change the "last work submitted" to a value that isn't subjective to your server?  Right now it returns a date/time stamp.  Apparently your server is about 2 mins different from mine, because the timestamp works out to 2+ mins old, when on your web server, it says a few seconds.  (active workers).

Thanks.
full member
Activity: 150
Merit: 100
Errr' Im brain dead today....using wrong password for logon. My fault.
hero member
Activity: 896
Merit: 532
Former curator of The Bitcoin Museum
None that I can see. It all seems to be a go-er
legendary
Activity: 1260
Merit: 1000
Stats should be fixed now.  There was a minor hiccup but stat processing caught up pretty quickly.  As for not being able to login, I'm not seeing any problems there. Are you still having problems?
full member
Activity: 150
Merit: 100
Ya something is f'd up. Hash rate is all wrong and can't log on to EMC forum.
hero member
Activity: 896
Merit: 532
Former curator of The Bitcoin Museum
Something strange just happened.

I got an SMS telling me one of my rigs failed. I got 3 rigs called alpha, beta and gamma.

Now it said last activity from beta was an hour ago, but when I logged in he was quite happily hashing away on us1

. I restarted cgminer and its all good again.

This happened to anyone else?
newbie
Activity: 32
Merit: 0
Connectivity from the people having trouble at home should be fixed.  The routing table got set to a class A address somehow.  It should work now... sorry about that! I  have no idea how that would have even happened.

awesome!  confirmed it works now!
legendary
Activity: 1260
Merit: 1000
Connectivity from the people having trouble at home should be fixed.  The routing table got set to a class A address somehow.  It should work now... sorry about that! I  have no idea how that would have even happened.
legendary
Activity: 1260
Merit: 1000
Yeah, and Paypal, though that's no longer and option. 
full member
Activity: 181
Merit: 100
Is this the first pool to offer dwolla as a direct payout?
hero member
Activity: 588
Merit: 500
wow some luck you have there
legendary
Activity: 1260
Merit: 1000
I think we have a first ever:  Block 204499 ...  EMC orphaned itself. 

Two servers found a similar solution almost at the same time.  I guess that was bound to happen eventually, crazy though.
newbie
Activity: 42
Merit: 0
Try to US3 as opposed to US1.  Also send me you IP address via PM.

Code:
Tracing route to eclipsemc.com [96.43.135.180]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     8 ms     8 ms     6 ms  L100.DLLSTX-VFTTP-77.verizon-gni.net [71.97.84.1]
  3    11 ms    10 ms     9 ms  G0-9-0-1.DLLSTX-LCR-21.verizon-gni.net [130.81.129.46]
  4     8 ms    10 ms     8 ms  so-5-0-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.34]
  5     9 ms     9 ms    10 ms  152.63.4.13
  6   154 ms   222 ms   219 ms  te3-4.ccr01.dfw03.atlas.cogentco.com [154.54.12.205]
  7    78 ms   215 ms   220 ms  te7-1.ccr02.dfw03.atlas.cogentco.com [154.54.25.6]
  8    11 ms    14 ms    12 ms  te0-4-0-3.ccr22.dfw01.atlas.cogentco.com [154.54.82.29]
  9    21 ms    22 ms    21 ms  te0-3-0-6.mpd22.mci01.atlas.cogentco.com [154.54.46.213]
 10    26 ms    23 ms    19 ms  te2-1.mag02.mci01.atlas.cogentco.com [154.54.30.166]
 11    23 ms    22 ms    22 ms  38.104.86.74
 12    22 ms    22 ms    21 ms  DC2SW1.KCMODATACENTER.com [96.43.134.54]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.


Code:
Tracing route to us3.eclipsemc.com [69.195.155.234]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     7 ms     6 ms  L100.DLLSTX-VFTTP-77.verizon-gni.net [71.97.84.1]
  3    10 ms    10 ms    12 ms  G0-9-0-1.DLLSTX-LCR-21.verizon-gni.net [130.81.129.46]
  4     9 ms    10 ms     8 ms  so-5-0-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.34]
  5    75 ms    13 ms    11 ms  152.63.4.13
  6    12 ms     9 ms    10 ms  te3-4.ccr01.dfw03.atlas.cogentco.com [154.54.12.205]
  7    12 ms    16 ms    12 ms  te0-3-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.82.17]
  8    12 ms    14 ms    12 ms  te0-1-0-0.ccr22.dfw01.atlas.cogentco.com [154.54.46.170]
  9    24 ms    22 ms    21 ms  te0-3-0-6.mpd22.mci01.atlas.cogentco.com [154.54.46.213]
 10    23 ms    21 ms    23 ms  te2-1.mag02.mci01.atlas.cogentco.com [154.54.30.166]
 11    21 ms    24 ms    22 ms  38.104.86.74
 12    61 ms    22 ms    21 ms  DC3SW1.KCMODATACENTER.COM [96.43.134.34]
 13    23 ms    24 ms    24 ms  69.195.155.234

Trace complete.
legendary
Activity: 1260
Merit: 1000
Try to US3 as opposed to US1.  Also send me you IP address via PM.
newbie
Activity: 32
Merit: 0
That's pretty strange.  Can you run a traceroute on it?

here are a traceroute of eclipsemc.com and us1

Code:
linux~ # traceroute eclipsemc.com
traceroute to eclipsemc.com (96.43.135.180), 30 hops max, 60 byte packets
 1  orion (192.168.5.1)  0.162 ms  0.186 ms  0.220 ms
 2  * * *
 3  10.170.169.161 (10.170.169.161)  12.519 ms  12.529 ms  12.529 ms
 4  216.113.122.17 (216.113.122.17)  12.875 ms  12.881 ms  12.882 ms
 5  216.113.123.222 (216.113.123.222)  33.327 ms  33.337 ms  33.342 ms
 6  216.113.125.38 (216.113.125.38)  31.200 ms  31.104 ms  31.088 ms
 7  10gigabitethernet1-1.core1.mci1.he.net (72.52.92.2)  40.967 ms  35.352 ms  40.483 ms
 8  10gigabitethernet1-1.core1.mci2.he.net (184.105.213.2)  41.748 ms  41.417 ms  41.419 ms
 9  joe-s-data-center-llc.10gigabitethernet1-4.core1.mci1.he.net (216.66.79.14)  39.271 ms  34.789 ms  38.432 ms
10  DC2SW1.KCMODATACENTER.COM (96.43.134.38)  39.281 ms  41.079 ms  41.950 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
Code:
linux~ # traceroute us1.eclipsemc.com
traceroute to us1.eclipsemc.com (208.110.68.114), 30 hops max, 60 byte packets
 1  orion (192.168.5.1)  0.153 ms  0.179 ms  0.217 ms
 2  * * *
 3  10.170.169.165 (10.170.169.165)  13.785 ms  13.800 ms  13.794 ms
 4  216.113.122.37 (216.113.122.37)  14.246 ms  14.256 ms  14.268 ms
 5  216.113.124.118 (216.113.124.118)  37.166 ms  37.188 ms  37.184 ms
 6  216.113.125.38 (216.113.125.38)  32.848 ms  32.736 ms  32.702 ms
 7  10gigabitethernet1-1.core1.mci1.he.net (72.52.92.2)  42.560 ms  35.772 ms  40.002 ms
 8  10gigabitethernet1-1.core1.mci2.he.net (184.105.213.2)  42.213 ms  41.771 ms  41.774 ms
 9  wholesale-internet-inc.10gigabitethernet1-3.core1.mci2.he.net (216.66.78.90)  39.527 ms  36.818 ms  51.145 ms
10  69.30.209.1 (69.30.209.1)  51.153 ms  46.915 ms  46.920 ms
11  us1.eclipsemc.com (208.110.68.114)  46.874 ms  41.374 ms  36.434 ms
legendary
Activity: 1260
Merit: 1000
That's pretty strange.  Can you run a traceroute on it?
newbie
Activity: 42
Merit: 0
Everything seems to be up and running at the moment. Are you still having issues?

i've actually been having problems going to the website itself from my home connection.. but i can connect to the pools...  it just seems to be the web service i cant reach..  but I can from work ..  and other friend on the same provider also works.. 

this is the resolved ip for eclipsemc.com: 96.43.135.180

im getting connection timeouts over port 80:
Connecting to 96.43.135.180:80... failed: Connection timed out.

Yea I am having the same issue connecting to the Site from my home connection but I can access the pool servers ok
hero member
Activity: 560
Merit: 500
Pages:
Jump to: