[CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers

[caminilegroup]

So I have noticed a problem using slush's proxy that started sometime yesterday. I keep getting not connected error.

I can verify it is only on btc guild, I move to another pool and it is mining away, have I been black listed or is there a glitch somewhere?

[1713485779]

1713485779

[1713485779]

1713485779

[1713485779]

1713485779

[wtfvanity]

... GHash.IO's ... BTC Guild isn't going to compete with someone like that.

You have that backwards. What you meant, is that they do not compete with you. Not that you won't compete with them.

[twmz]

eleuthria,

Have you considered lowering PPLNS fees to attract more miners?

GHash.IO appears to be growing at an alarming rate.

https://blockchain.info/pools?timespan=24hrs

P.S. That chart based on faulty data and so usually quite inaccurate.  Use this one instead:

http://blockorigin.pfoe.be/chart.php

[eleuthria]

So I have noticed a problem using slush's proxy that started sometime yesterday. I keep getting not connected error.

I can verify it is only on btc guild, I move to another pool and it is mining away, have I been black listed or is there a glitch somewhere?

Definitely a problem on your end.  A significant number of users use the slush stratum proxy with BTC Guild and the speed has been stable/growing consistently for weeks.  Either you have a bad username and it's kicking you off, or you're not authorizing a worker and it's disconnecting you after a while of holding open an idle connection.  Other problem would be routing issues on your end between you and Chicago.

[caminilegroup]

So I have noticed a problem using slush's proxy that started sometime yesterday. I keep getting not connected error.

I can verify it is only on btc guild, I move to another pool and it is mining away, have I been black listed or is there a glitch somewhere?

Definitely a problem on your end.  A significant number of users use the slush stratum proxy with BTC Guild and the speed has been stable/growing consistently for weeks.  Either you have a bad username and it's kicking you off, or you're not authorizing a worker and it's disconnecting you after a while of holding open an idle connection.  Other problem would be routing issues on your end between you and Chicago.

I'm fixing to test, I am changing my router to my business firewall, hopefully it was just an apple airport being pissy problem

[mdude77]

So I have noticed a problem using slush's proxy that started sometime yesterday. I keep getting not connected error.

I can verify it is only on btc guild, I move to another pool and it is mining away, have I been black listed or is there a glitch somewhere?

Definitely a problem on your end.  A significant number of users use the slush stratum proxy with BTC Guild and the speed has been stable/growing consistently for weeks.  Either you have a bad username and it's kicking you off, or you're not authorizing a worker and it's disconnecting you after a while of holding open an idle connection.  Other problem would be routing issues on your end between you and Chicago.

I'm fixing to test, I am changing my router to my business firewall, hopefully it was just an apple airport being pissy problem

Using the latest version of the proxy?  Older versions always gave me a hassle at some point.

M

[superduh]

eleuthria, you've been mentioned http://www.coinion.com/2013/12/11/child-labor-bitcoin-mines-exposed/

[caminilegroup]

So I have noticed a problem using slush's proxy that started sometime yesterday. I keep getting not connected error.

I can verify it is only on btc guild, I move to another pool and it is mining away, have I been black listed or is there a glitch somewhere?

Definitely a problem on your end.  A significant number of users use the slush stratum proxy with BTC Guild and the speed has been stable/growing consistently for weeks.  Either you have a bad username and it's kicking you off, or you're not authorizing a worker and it's disconnecting you after a while of holding open an idle connection.  Other problem would be routing issues on your end between you and Chicago.

I'm fixing to test, I am changing my router to my business firewall, hopefully it was just an apple airport being pissy problem

Using the latest version of the proxy?  Older versions always gave me a hassle at some point.

M

Latest, what is weird is it is only doing it on btc guild. Made sure my firewall is set correctly. I even did a fresh install of ubuntu 12.04 and did the git route, still, same results with ubuntu 13.10.

Does it only on btcguild, bitminter, multipool, slush, and bitparking no problems. My next step is to install windows xp on a vm and try it that way, although I hate using windows for anything networking related, and I'm a sysadmin, lol

[caminilegroup]

Ok, fresh install ubuntu server 13.10, compiled bfgminer. I hate to say this, but I don't think it is on my end.

https://lh3.googleusercontent.com/-Xv1FfZ_-pqU/UqjqV0izK5I/AAAAAAAAQa8/cgG904lOfnU/s0/Screen%2520Shot%25202013-12-11%2520at%25204.42.03%2520PM.png

Connected and mining on another pool.

https://lh6.googleusercontent.com/-In8OvraLbA4/UqjrdeGYFyI/AAAAAAAAQbI/baPrXMucnxA/s0/Screen%2520Shot%25202013-12-11%2520at%25204.47.01%2520PM.png

[eleuthria]

Good evening,
  It *is* on your end, otherwise I'd have an inbox with a couple hundred emails and a pool with a ton of speed missing.  My only guess is your system doesn't like the redirect DNS, since you're connecting to the verification server, it's sending you the redirect, and then 1 second later it's complaining about not responding with the old pool URL in there.

  Try connecting directly to the redirection server?

[caminilegroup]

Good evening,
  It *is* on your end, otherwise I'd have an inbox with a couple hundred emails and a pool with a ton of speed missing.  My only guess is your system doesn't like the redirect DNS, since you're connecting to the verification server, it's sending you the redirect, and then 1 second later it's complaining about not responding with the old pool URL in there.

  Try connecting directly to the redirection server?

Still shows dead. Even tried 198.245.63.145 and it will connect then drop. Changed my dns to google and still the same. My last share was 20 hours ago, so it happened last night and I can't get for the life of me try to get it to connect.

[eleuthria]

Good evening,
  It *is* on your end, otherwise I'd have an inbox with a couple hundred emails and a pool with a ton of speed missing.  My only guess is your system doesn't like the redirect DNS, since you're connecting to the verification server, it's sending you the redirect, and then 1 second later it's complaining about not responding with the old pool URL in there.

  Try connecting directly to the redirection server?

Still shows dead. Even tried 198.245.63.145 and it will connect then drop. Changed my dns to google and still the same. My last share was 20 hours ago, so it happened last night and I can't get for the life of me try to get it to connect.

198.245.63.145 is the verification server.  You're only on that server for the very first submission.  Set your miner to connect to the URL it's redirecting you to instead and see if that fixes it.

[caminilegroup]

Good evening,
  It *is* on your end, otherwise I'd have an inbox with a couple hundred emails and a pool with a ton of speed missing.  My only guess is your system doesn't like the redirect DNS, since you're connecting to the verification server, it's sending you the redirect, and then 1 second later it's complaining about not responding with the old pool URL in there.

  Try connecting directly to the redirection server?

Still shows dead. Even tried 198.245.63.145 and it will connect then drop. Changed my dns to google and still the same. My last share was 20 hours ago, so it happened last night and I can't get for the life of me try to get it to connect.

198.245.63.145 is the verification server.  You're only on that server for the very first submission.  Set your miner to connect to the URL it's redirecting you to instead and see if that fixes it.

You're talk about "stratum-lb-usa48.btcguild.com:3333", tried it, same result connect then dead.

[eleuthria]

Good evening,
  It *is* on your end, otherwise I'd have an inbox with a couple hundred emails and a pool with a ton of speed missing.  My only guess is your system doesn't like the redirect DNS, since you're connecting to the verification server, it's sending you the redirect, and then 1 second later it's complaining about not responding with the old pool URL in there.

  Try connecting directly to the redirection server?

Still shows dead. Even tried 198.245.63.145 and it will connect then drop. Changed my dns to google and still the same. My last share was 20 hours ago, so it happened last night and I can't get for the life of me try to get it to connect.

198.245.63.145 is the verification server.  You're only on that server for the very first submission.  Set your miner to connect to the URL it's redirecting you to instead and see if that fixes it.

You're talk about "stratum-lb-usa48.btcguild.com:3333", tried it, same result connect then dead.

Are you sure you're using the right worker name?  Not using a '.' instead of a '_'? or something like that.  There is absolutely nothing wrong on the servers (~24,000 connected users).  Nothing has changed in weeks either.

[caminilegroup]

Good evening,
  It *is* on your end, otherwise I'd have an inbox with a couple hundred emails and a pool with a ton of speed missing.  My only guess is your system doesn't like the redirect DNS, since you're connecting to the verification server, it's sending you the redirect, and then 1 second later it's complaining about not responding with the old pool URL in there.

  Try connecting directly to the redirection server?

Still shows dead. Even tried 198.245.63.145 and it will connect then drop. Changed my dns to google and still the same. My last share was 20 hours ago, so it happened last night and I can't get for the life of me try to get it to connect.

198.245.63.145 is the verification server.  You're only on that server for the very first submission.  Set your miner to connect to the URL it's redirecting you to instead and see if that fixes it.

You're talk about "stratum-lb-usa48.btcguild.com:3333", tried it, same result connect then dead.

Are you sure you're using the right worker name?  Not using a '.' instead of a '_'? or something like that.  There is absolutely nothing wrong on the servers (~24,000 connected users).  Nothing has changed in weeks either.

Yep, triple checked, even copied and pasted it from the support page just to be sure.

If I try and ping stratum-lb-usa48.btcguild.com, it does return "us-stratum-loadbalancer.btcguild.com (50.31.189.48)" but I get timeouts, but this could also be because you are blocking ping request on that server for security reasons.

[OtaconEmmerich]

I'm having problems connecting too, maybe it's some DNS server or something being wacky. I also had issues connecting to the website (I got forced into a redirect via cloudfire for a good 10 seconds) Also Bitcointalk.org was down for a while for me.

[mtbitcoin]

I'm having problems connecting too, maybe it's some DNS server or something being wacky. I also had issues connecting to the website (I got forced into a redirect via cloudfire for a good 10 seconds) Also Bitcointalk.org was down for a while for me.

I concur. Had the same issues earlier on the day too.

[kendog77]

eleuthria,

Are any stats on pool luck available on the web interface? Are the 24 hour earning stats accurate?

[eleuthria]

eleuthria,

Are any stats on pool luck available on the web interface? Are the 24 hour earning stats accurate?

There's a giant graph on the PPLNS Stats page for luck.  24 hour earnings for PPS are accurate except for the first 24 hours after a difficulty change.  24 hour earnings for PPLNS are accurate, except they're on an ~8 hour delay (uses the last 24 hours worth of closed shifts since open shifts are not done getting paid).

I'm having problems connecting too, maybe it's some DNS server or something being wacky. I also had issues connecting to the website (I got forced into a redirect via cloudfire for a good 10 seconds) Also Bitcointalk.org was down for a while for me.

I concur. Had the same issues earlier on the day too.

There was a 5 minute outage roughly last night due to a backup script on the DB server eating up all the space on the drive.  Most mining software should have automatically reconnected. 

[caminilegroup]

Since there is no manual cash out for NMC, how do I get my entire balance? I have exhausted all efforts to try and mine but it it keeps dropping. I'm willing to try specific ip's if you want to pass them my way but I don't know what else to do at this point.

Here is my traceroute:

TRACEROUTE (using port 111/tcp)
HOP RTT       ADDRESS
1   0.40 ms   192.168.1.1
2   9.27 ms   10.131.56.1
3   10.12 ms  70.169.88.92
4   23.73 ms  70.169.88.8
5   23.34 ms  btnrbbrc01-pos0200.rd.br.cox.net (68.1.1.213)
6   34.37 ms  68.1.5.135
7   ... 9
10  132.57 ms 198.27.73.181
11  67.84 ms  bhs-g1-6k.qc.ca (198.27.73.5)
12  417.69 ms bhs-1-6k.qc.ca (198.27.73.12)
13  67.27 ms  ks4000816.ip-198-245-63.net (198.245.63.145)

I can access port 3333, sorry about the port scan btw

Starting Nmap 6.40-2 ( http://nmap.org ) at 2013-12-12 10:43 CST
NSE: Loaded 110 scripts for scanning.
NSE: Script Pre-scanning.
Initiating Ping Scan at 10:43
Scanning stratum.btcguild.com (198.245.63.145) [4 ports]
Completed Ping Scan at 10:43, 0.06s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 10:43
Completed Parallel DNS resolution of 1 host. at 10:43, 0.10s elapsed
Initiating SYN Stealth Scan at 10:43
Scanning stratum.btcguild.com (198.245.63.145) [1000 ports]
Discovered open port 554/tcp on 198.245.63.145
Discovered open port 21/tcp on 198.245.63.145
Discovered open port 22/tcp on 198.245.63.145
Discovered open port 8333/tcp on 198.245.63.145
Discovered open port 7070/tcp on 198.245.63.145
Completed SYN Stealth Scan at 10:43, 2.24s elapsed (1000 total ports)
Initiating Service scan at 10:43
Scanning 5 services on stratum.btcguild.com (198.245.63.145)
Completed Service scan at 10:45, 85.62s elapsed (5 services on 1 host)
Initiating OS detection (try #1) against stratum.btcguild.com (198.245.63.145)
Retrying OS detection (try #2) against stratum.btcguild.com (198.245.63.145)
Initiating Traceroute at 10:45
Completed Traceroute at 10:45, 3.01s elapsed
Initiating Parallel DNS resolution of 10 hosts. at 10:45
Completed Parallel DNS resolution of 10 hosts. at 10:45, 0.14s elapsed
NSE: Script scanning 198.245.63.145.
Initiating NSE at 10:45
Completed NSE at 10:45, 5.14s elapsed
Nmap scan report for stratum.btcguild.com (198.245.63.145)
Host is up (0.034s latency).
rDNS record for 198.245.63.145: ks4000816.ip-198-245-63.net
Not shown: 990 closed ports
PORT     STATE    SERVICE      VERSION
21/tcp   open     tcpwrapped
22/tcp   open     ssh          OpenSSH 5.9p1 Debian 5ubuntu1.1 (Ubuntu Linux; protocol 2.0)
| ssh-hostkey: 1024 38:e0:3f:cb:2e:53:37:64:db:4d:61:3b:cb:4f:6f:f9 (DSA)
| 2048 ae:4a:36:3c:5f:b7:d2:69:2e:30:7d:f9:7d:23:ae:9b (RSA)
|_256 4c:f7:9a:13:45:03:ba:76:74:ca:dd:7d:b5:e1:90:0f (ECDSA)
25/tcp   filtered smtp
135/tcp  filtered msrpc
139/tcp  filtered netbios-ssn
445/tcp  filtered microsoft-ds
554/tcp  open     tcpwrapped
3333/tcp filtered dec-notes
7070/tcp open     tcpwrapped
8333/tcp open     unknown
OS fingerprint not ideal because: Host distance (13 network hops) is greater than five
No OS matches for host
Network Distance: 13 hops
TCP Sequence Prediction: Difficulty=213 (Good luck!)
IP ID Sequence Generation: Incremental
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

TRACEROUTE (using port 111/tcp)
HOP RTT       ADDRESS
1   0.40 ms   192.168.1.1
2   9.27 ms   10.131.56.1
3   10.12 ms  70.169.88.92
4   23.73 ms  70.169.88.8
5   23.34 ms  btnrbbrc01-pos0200.rd.br.cox.net (68.1.1.213)
6   34.37 ms  68.1.5.135
7   ... 9
10  132.57 ms 198.27.73.181
11  67.84 ms  bhs-g1-6k.qc.ca (198.27.73.5)
12  417.69 ms bhs-1-6k.qc.ca (198.27.73.12)
13  67.27 ms  ks4000816.ip-198-245-63.net (198.245.63.145)

NSE: Script Post-scanning.
Initiating NSE at 10:45
Completed NSE at 10:45, 0.00s elapsed
Read data files from: /usr/local/bin/../share/nmap
OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 109.11 seconds
           Raw packets sent: 1087 (49.616KB) | Rcvd: 1037 (43.244KB)