Quote from: schnellminer on December 30, 2013, 02:56:22 PM

Quote from: gbsray on December 14, 2013, 08:24:17 PM

Quote from: bluedragon on December 12, 2013, 04:34:05 PM

The setup that's been most stable for me is setting it to use 2 different servers. Because I want it to stay on 1 pool, I set it to use a stratum proxy for 1 of the servers, and connect directly to the getwork server on the same pool for the other server. It switches itself back and forth every so often, but doesn't stop hashing and restart.

That's the trick! Server with 2 NICs on 2 different IP's but same port. Switches between the two but dosent reset!

My blades have been rebooting every hour to the second since I got them. This suggestion is what worked for me with a few changes. Evidently the blades do not like having the same server IP address listed for primary and secondary. What I did was bind a second IP address to the same NIC on my Linux box running the stratum proxy. Changed the secondary address on the blade to the new secondary IP bound on the stratum proxy and problem gone.

Thanks to bluedragon and gbsray for pointing me in the right direction.

I changed my config back to 2 pools and it's been stable, not restarting and not switching servers hourly. I have no idea why it's staying on 1 pool now, and wasn't before. The difference in my config this time is that I started a second stratum proxy listening on a different port (same IP address) for my backup pool, instead of using 1 stratum proxy and 1 getwork server. I just don't get it.

Edit: fixed (I hope) a missing closing quote tag that was messing things up.