Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 596. (Read 4382755 times)

if you're using a powerfull asic you should up the difficulty, too many shares per second and just ddos the server and it may desconect you.
Not slush, amazon aws.

I had a lot of weird connection problems over the past 24 hours but my miners have been going strong for a while now, so it seems as though the issue has been fixed, at least from where I am.

I've been having trouble today too.
My internet is fine but the miner stops hashing for a few blocks then gets going again.

I am running minepeon and I even switched to a fresh sd card/install to fix it but it didn't improve.

Edit: reading backwards through the thread I understand one of the servers was having problems...so just sitting patiently I'm sure he will sort it out. In the meantime I'm up and down like a toilet seat....no biggie I'm not running a mini-rig where it might matter.
 

Try bouncing your PCs network connection and flush your DNS Cache.

Been fine all day

Anyone having trouble connecting to the pool?

Been having this problem periodically.

19220   2013-07-21  21:10:43     3:12:23    59988542    3553    0.00000001   247811  25.25581000    100 confirmations left

Hopefully it'll fix itself like most of the others have.   

you are absolutely correct. I didn't specify in my post that the IP should be just a temporary/quick fix. I didn't bother trying to flush my DNS, I will have to try that when I get home.

it took several trys before one of my miners could connect.

I aim for 85 as a top so I have a little wiggle room in case something happens to one of the case fans.  90 just makes me nervous.

Weird.  cgminer and bfgminer connects , but reaper + miningproxy does not.

I need to use differ programs for different hardware.  ATI 6000 series doesn't seem to work with anything but reaper.  7000 series seem to work with cg and BFG, and erupter works easiest with BFG.

Anything below 90C is fine for ATI chips.  95C is where I start worrying.

I don't think 80c does any harm, its voltage which damages.     

I use Guiminer with my Sapphire 7950. It has run for weeks on end with no problems or restarting but just notice that it  was not recording its work on my account page ( stopped recording sometime yesterday), so I restarted and is fine now. So it seems Something happened on the Pool yesterday that was out of the norm. I have it overclocked and I get just over 600MH/s

I also run 15 USB asic miners and use BFGminer. Once again I have run weeks without restarting with no problems. When I do start up the USB's  BFGminer turns my GPU fan up all the way which after they get started I just go into my GPU settings and turn the fan speed back down to where I want it. I run the fan on manual as to keep the temp around 72-75C if not the auto keeps it at 80C.

can't connect

I still have miners unable to connect to connect on slush, whats going on?

When I used guiminer, I found one or more gpu's needed a stop/restart about every 12 hours or they'd go off into never-never land, and a complete kill and reload of the app about every 3 days kept it from crashing.

Now I use cgminer for my gpu workers and bfgminer for my fpga/asic workers.  cgminer gives me the same start-stop control over my gpus that guiminer did, without guiminer's frequent hangs, plus other controls not directly accessible in the guiminer app like temp cutoffs per gpu and fail-overs.  Last I used guiminer, it would not support fpga/asic workers -- don't know if it does now -- so use bfgminer since it usually auto-detects fpga/asic devices, and if it doesn't, you can force it to scan any usb ports it missed.  I could use bfgminer for my gpus, too, but have been too lazy to change my cgminer .bat files to bfgminer.

See my above post regarding your second question. There was definitely something wrong with Slush's setup this morning.

Your first questions sounds like either your GPU faulted (too hot, too overclocked, hardware problem) or GUIMINER had a connection issue related to your second question.  I have personally not used BFGMiner, but I have used CGMINER and GUIMINER.  CGMINER is far superior in its informational feedback and software options (overclocking options of your GPU built into the software).  I only use GUIMiner on my windows machines that are used for other things and I can't mess around with them too much. CGminer takes more time to setup and is more finicky with OpenCL drivers.  It is much easier to setup on Ubuntu (I use 12.04 LTS on my main mining rig with 2 7870 XTs and 7 ASICMINER Block Erupters).  If you are familiar with linux or up for a challenge, I would HIGHLY suggest researching and setting up a machine running Linux and CGMiner.  The pool management options are extremely useful when mining on Slush since we occasionally (not often, but still) experience server issues.  My main rig will immediately switch to BTC GUILD in the event cgminer cannot communicate with stratum.bitcoin.cz ...  

--EDIT--
Again, just my $0.00  Again, just my $0.02

Just as a forewarning... I dont think using the direct IP is necessarily a good long term option.  From what I understand, Slush uses Amazon AWS. AWS offers load balancing, geolocating\geocaching, and failover based on availability zones.  If AWS is like the Azure platform (which I work with for my job), IP addresses are not dedicated.  When you set it up, you point your regular public DNS to your AWS FQDN and then the AWS system handles DNS\Routing from there which is what allows the above Amazon services to function with little to no setup.  By specifying a server IP address, you are circumventing this feature. This may temporarily resolve an issue such as today when a specific load balancing server is down or a specific geolocation\availability zone is malfunctioning in a way that AWS doesn't recognize the malfunction and remove the specific server from the rotation.  However, long term you don't get the benefits of those options, which would be crucial if the specific server you chose fails.  Also, without dedicated IP's, there is no guarantee that server will continue to be located there after an IP lease renewal or a server reboot. 

I could be totally wrong about this, but this is why I wont use direct IPs.  I experienced the issues earlier today and I resolved them by bouncing NIC's on all my machines to reset my connection and flush old\invalid DNS data. I also bounced the proxy software on 2 of my machines that use that.  I never stopped CGMINER or GUIMINER (on my windows machine... I know I know but CGMINER throws fits on that machine) and the network bounce took less than a minute.
Just my $0.02 

I had this same problem today. One of Slush's servers is having connection problems or something (i'm not sure) but basically whenever I connect to stratum.bitcoin.cz it fails, but someone else posted some slush IP's and the one that currently works is 54.215.3.101

so in GUIminer i set that as my host, stop and restart, and then it started accepting shares and they were being credited to my account (where as before guiminer would generate shares but i received no credit)