Quote from: divinesnail01 on April 02, 2014, 04:23:35 AM

I'm going slightly nuts here, and would appreciate some additional assistance.

I'm running 3 cubes - 3rd one arrived about a week ago. 2 of them usually run at 38 (high clock) and one of them runs at 30 (low clock) because I don't like how the power leads heat up on that power supply, and I haven't bought a new one yet.

Last Thursday, I was showing 100GH/s at my pool - less than I expected, but reasonable.

Since then, I'm seeing what I consider to be really odd behavior in my proxy(ies). Specifically, they will run with the usual scrolling display for 10 - 15 seconds, and then stop. About 45 seconds later they'll start scrolling again.

I've tried Linux (Ubuntu 10.04 LTS and 12.04 LTS) on virtual machines on 2 different hosts. I've actually lost count of how many iterations of linux machines I've tried. I've tried Windows XP, Windows 7, and Windows 8 on three different machines - all of which have had the cubes running at 38-39 GH/s each in the past. I've tried multi-homing the Linux virtual machines - one interface "outside" on the public internet, and the second interface "inside" for the cubes to connect to so as to bypass any congestion that my firewall might be adding.

I've been wanting to blame my ISP (Comcast business - no love lost there), so tonight I built an Ubuntu 12.04 LTS machine on an Amazon EC2 cloud instance, and it is doing the very same thing - running for 10 -15 seconds, and then pausing. Here's the strange part - the proxy running on the local machine and the proxy running on the EC2 pause and restart at exactly the same time.

Say what!!!???!!!

So I'm officially stumped.

Tonight I'm down to about 13GH/s on the two "faster" cubes, and and about 12 on the slower one. That's (almost?) not worth feeding electricity to.

I would be immensely appreciative of someone who has some experience with multiple cubes helping me to walk back through this. I can't believe that it's connectivity issues with the pool - I'd be hearing about it in the forums, right?

Actually - let's explore that for a moment - anyone else here running multiple cubes through Comcast that can say "yea" or "nay" to connectivity issues to Slush?

Thanks in advance;

'snail

A follow up, and perhaps some help for someone else:

Really short version: The more you can isolate these on the network the happier they'll be.

Short version: There might actually be something to that "get the Androids off the network". Running for 2 days now at above full rated speeds, just in time for the Slush pool to have a pretty good run of luck. I'm currently showing 106GH/s on the pool - my theoretical maximum for 2 at 38 and one at 30.

Longer version: I didn't think the Android issue would apply to me, as I don't use the wireless access point as my router, and the cubes and the wireless access point (and thus the Android machines) are on different network switches. I was watching my network traffic and my bandwidth utilization, both of which were quite low, and so assumed that the problem MUST be the proxy talking to the pool.
Under the heading of "can always learn something new" however, I decided to test the theory, but knew that it would be easier to cut fingers off than to get all the Android devices off my network.
So.... I took another older consumer level router that I wasn't using anymore, and connected it to my cable modem as a peer to my primary firewall (I have a pretty good internet connection that gives me some flexibility that not everyone would have). I moved a "hardware" machine and the cubes to that network, set my IP addresses, and started mining. The improvement was startling. Almost immediately into the 35 range for the two faster ones, and over the next hour, tickling 39. The slower one showed similar performance. I then put a connection from unused network ports on my virtual hosts, and started 2 virtual machines up. Set the cubes to the virtual machines for the proxy, shut down the "hardware" machine and let them run. We're coming up on 48 hours since the last time I restarted the cubes for an IP address change, and the numbers are great. I don't see them rotating between proxies, and so could probably get away with just one VM, but the 2nd one doesn't cost me anything.

Time to upgrade this poor power supply that came with the 3rd cube, and then add a 4th. Don't tell my wife.

As a side note: The "proxy in the cloud" on the Amazon EC2 actually worked pretty well once I got the cubes isolated. I'm getting a little bit better numbers with the local machines, but if I didn't have these hosts running 24/7/365 already anyway, I'd seriously consider getting the free Amazon account for a year, and letting them pay the electricity for the proxy.

Thanks for the help, and happy mining.

'snail