Yeah, that sounds like a plan!
Whup it with yer stick and frag it.
Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 192. (Read 499709 times)
August 19, 2011, 10:30:59 PM
August 19, 2011, 10:27:03 PM
It's ok 
There's always plenty of work to do either way, so it's not like I'll be idle!
Maybe I should game to get the block solved. It's about to be the longest block yet. Stupid block... and the difficulty even went DOWN and it's taking this long. I needs mah beatin' stick.
There's always plenty of work to do either way, so it's not like I'll be idle! Maybe I should game to get the block solved. It's about to be the longest block yet. Stupid block... and the difficulty even went DOWN and it's taking this long. I needs mah beatin' stick.
August 19, 2011, 10:24:43 PM
Sorry I can't help.
My rig is at the office and I don't know how to use SSH.
My rig is at the office and I don't know how to use SSH.
August 19, 2011, 10:19:13 PM
So it looks like things are stable. Can you guys report how your stale rate is a this point? Any improvement? I have a few things I'm going to be working on in that area going forward, assuming no more surprise problems crop up.
August 19, 2011, 07:24:48 PM
It may take a few hours for the bad DNS information to make it's way out of the system. It should resolve itself at some point, just depends on how long your local DNS holds it's information before checking for an update.
August 19, 2011, 07:23:20 PM
So everything is working properly now?
My workers have all failed over to deepbit. If this is not going to resolve by itself, I'll have to go onsite and restart the workers.
August 19, 2011, 06:08:06 PM
Hrmm.. DNS didn't propagate properly (mostly my fault), but the problem has been fixed now. So the hashrate is going to drop for about 90 minutes until it propagates the correct information.
I need a vacation. I'm glad it's Friday.
I need a vacation. I'm glad it's Friday.
August 19, 2011, 03:58:45 PM
I'm getting "ERROR: Cannot connect to Bitcoin: connect timed out" on both the ip and domain
I'm working now, thanks
August 19, 2011, 03:55:54 PM
Yeah the box was having some trouble with dual gateways to the same little place called the interwebz. Should be fixed now.
Is anyone having a problem as of this post?
Is anyone having a problem as of this post?
August 19, 2011, 03:50:41 PM
I'm getting "ERROR: Cannot connect to Bitcoin: connect timed out" on both the ip and domain
August 19, 2011, 03:19:29 PM
both working now
August 19, 2011, 02:52:55 PM
us.eclipsemc.com:8337 Problems communicating with bitcoin RPC 2 2
When should it start working again?
Yes, I know I'm an idiot, but...
208.110.68.114:8337 Problems communicating with bitcoin RPC 2 2
When should it start working again?
Yes, I know I'm an idiot, but...
208.110.68.114:8337 Problems communicating with bitcoin RPC 2 2
August 19, 2011, 02:47:06 PM
So it's not some kernel funkiness with eth1. I've brought up another IP and I will be changing the DNS to reflect the new IP. You should not have to do anything on your end, and your DNS provider will eventually update the IP on it's own. I will keep both IPs active for several days before cutting off the old IP.
If you guys want to switch to the new IP before your DNS propegates, the new IP is: 208.110.68.114
If you guys want to switch to the new IP before your DNS propegates, the new IP is: 208.110.68.114
August 19, 2011, 02:26:18 PM
Yeah, network cable was one of the first things 
The problem is following the eth interface (not the NIC)... after elminating everything else, it's either the IP address (some esoteric routing thing somewhere), the switches uplink port itself (unlikely) or something wonky in the kernel in relation to eth1. My last step before changing the IP to see if it's a routing issue I'm not seeing anywhere (I can't imagine this is the case, given the nature of the problem) was to swap the eth0 and eth1 addresses. We will see how it goes for the next hour or so.
The problem is following the eth interface (not the NIC)... after elminating everything else, it's either the IP address (some esoteric routing thing somewhere), the switches uplink port itself (unlikely) or something wonky in the kernel in relation to eth1. My last step before changing the IP to see if it's a routing issue I'm not seeing anywhere (I can't imagine this is the case, given the nature of the problem) was to swap the eth0 and eth1 addresses. We will see how it goes for the next hour or so.
August 19, 2011, 02:01:11 PM
Looking much better
us.eclipsemc.com:8337 [206.437 MH/s (~191 MH/s)] [Rej: 1/136 (0.74%)]
us.eclipsemc.com:8337 [212.942 MH/s (~239 MH/s)] [Rej: 0/155 (0.00%)]
us.eclipsemc.com:8337 [206.437 MH/s (~191 MH/s)] [Rej: 1/136 (0.74%)]
us.eclipsemc.com:8337 [212.942 MH/s (~239 MH/s)] [Rej: 0/155 (0.00%)]
August 19, 2011, 01:20:46 PM
Just to keep ya'll updated, it's definitely not a hardware issue. I've isolated it to either the switch or a kernel issue.
There may be one more reboot coming, but hopefully not. I'm gettin' out my big poking stick now... doubles as a beatin' stick, too.
There may be one more reboot coming, but hopefully not. I'm gettin' out my big poking stick now... doubles as a beatin' stick, too.
erm, change the n/w cable as well?...you never know.
August 19, 2011, 01:06:52 PM
Just to keep ya'll updated, it's definitely not a hardware issue. I've isolated it to either the switch or a kernel issue.
There may be one more reboot coming, but hopefully not. I'm gettin' out my big poking stick now... doubles as a beatin' stick, too.
There may be one more reboot coming, but hopefully not. I'm gettin' out my big poking stick now... doubles as a beatin' stick, too.
August 19, 2011, 12:03:42 PM
leme know if you need any heckling
or anything else from someone that still doesn't know squat about Linux OR Bitcoin for that matter
or anything else from someone that still doesn't know squat about Linux OR Bitcoin for that matter
August 19, 2011, 11:56:57 AM
It's not better... eth1 is still dropping packets for some inexplicable reason.
I'm going to be rebooting the server a couple times to see if I can manage to track down the issue.
I'm going to be rebooting the server a couple times to see if I can manage to track down the issue.
August 19, 2011, 11:41:20 AM
stopped and restarted my miners after the server came back up
us.eclipsemc.com:8337 [207.112 MH/s (~177 MH/s)] [Rej: 10/118 (8.47%)]
us.eclipsemc.com:8337 [212.796 MH/s (~258 MH/s)] [Rej: 12/147 (8.16%)]
are we sure this is better?
my CPU miner is showing zero rejects though
us.eclipsemc.com:8337 [207.112 MH/s (~177 MH/s)] [Rej: 10/118 (8.47%)]
us.eclipsemc.com:8337 [212.796 MH/s (~258 MH/s)] [Rej: 12/147 (8.16%)]
are we sure this is better?
my CPU miner is showing zero rejects though
Jump to: