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

Estimated reward: 0.00000001 BTC

WTF?!?  Score reset?!? Again?!?

BioMega13:
Both api addresses still point to the old IP from before the intrusion.
api.bitcoin.cz, A, 176.31.157.132
api2.bitcoin.cz, A, 176.31.157.134

I'm not sure there is an api address anymore but for mining you can use stratum.bitcoin.cz

I'm sorry to say this but Slush has lost touch completely. This forum has been flooded with problem reports and hundreds of them could have been avoided if he only posted information or at least replied that nothing can be done.

My guess is moving the servers to the amazon cloud caused a lot of unforseen problems. Synchronization between the mining nodes seems to be the most serious one, which causes reward fluctuation. This is nothing that will heal itself though.

18008    2013-05-13 05:17:33    2:14:34    18510235    none    none    235946

I received no shares or reward. I left my guiminer mining all day and most of the night without turning it off. WTF? why am i not getting anything in the last 2 hours.

2013-05-12 03:53:38: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:38, No more backup servers left. Using primary and starting over.
2013-05-12 03:53:40: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:40,  [Errno 10061] No connection could be made because the target machine actively refused it
2013-05-12 03:53:41: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:41, IO errors - 1, tolerance 2
2013-05-12 03:53:42: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:42,  [Errno 10061] No connection could be made because the target machine actively refused it
2013-05-12 03:53:43: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:43, IO errors - 2, tolerance 2
2013-05-12 03:53:44: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:44,  [Errno 10061] No connection could be made because the target machine actively refused it
2013-05-12 03:53:45: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:45, IO errors - 3, tolerance 2
2013-05-12 03:53:45: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:45, No more backup servers left. Using primary and starting over.
2013-05-12 03:53:46: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:46,  [Errno 10061] No connection could be made because the target machine actively refused it
2013-05-12 03:53:47: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:47, IO errors - 1, tolerance 2
2013-05-12 03:53:48: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:48,  [Errno 10061] No connection could be made because the target machine actively refused it
2013-05-12 03:53:49: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:53:49, IO errors - 2, tolerance 2
2013-05-12 03:54:46: Listener for "Default": api2.bitcoin.cz:8332 12/05/2013 03:54:46, Setting new difficulty: 2

this is what I am getting on my guiminer, can someone please help me understand this

I was for about a day and a half but it wasn't Slush workers at another location were fine.  Either ISP or work doing something on the line.

Just confirming that about 20% of blocks (6 of the 30 currently on the statistic page) I am only getting about 45% of what I should be as a reward.

This is a net loss of ~9% which at 950mhash isn't exactly devastating... but it's quite noticeable and has been going on for quite some time.

 I'm glad you are getting exactly what is expected from each found block. Some larger miners are stressing due to the possibility of not being fairly compensated for our shares. I hope you can appreciate an alternate perspective when there are significantly more resources than 130MH/s being brought to bear.

This is getting crazy. If you don't trust this pool's stability, go try another. Sooner or later Slush will show up and look into things. Right now all you guys are doing is feeding each other's uncertainty and discomfort. There is nothing anyone can do except Slush. If he needs input from the users, i'm sure that he'll ask us for it. Constantly posting about this server, or that server, or this calculation, or that, isn't going to accomplish anything until we here from Slush.

Yeah, we'd all like to help and figure out what is going on, but none of us can see the whole picture. We can't look behind the curtains and see what is going on.

I'm only a little miner, about 130MHs, but i've been getting exactly what i expect from each block we find.

I was using stratum.bitcoin.cz:3333 for all my workers, if that helps anyone troubleshoot things further.

guys - guiminer is flakey on any pool - try cgminer or bfg

I have more than 20 workers all connecting to the same server. Only one worker had the issue where it appeared to be working on the client side but showed zero shares on the web interface.  It just happened to be one of my faster miners. All workers are running from the same internal network so have the same external IP.

All of my workers use guiminer with the default slush setting which I believe is forwarded to stratum.bitcoin.cz:3333. 

I'm using v*****.bitcoin.cz. Seems to be okay. I don't think the issue ever was bad shares but rather the score system. Do we know how score is calculated or increased? I can tell it has something to do with the number of shares you contribute and how quickly. The tiny rewards happen when worker scores reset but the total score does not (or reaches a 12-digit+ integer).

I hear ya I'm having high discarded shares connecting via stratum to stratum.bitcoin.cz:3333

Note that I don't have a problem with rewards on this server, which other people have complained about in earlier posts. My issue is the high percentage of discarded shares.

SERVERS People!! Can't stress enough to look in on who is suposed to be recieving the shares as ( for me at least ) we got a 2 fold issue

1) Name Coin IS being processed by at least 1 stratum server ( and it's not ' official ' yet, shows on the namecoin stats page as Stratum Connections )
2) there is no indication on our end or on pages ( that at least I can find ) how many NMC Shares have been submitted.

So, both of you and future submitters, please post what stratum server seems to be the issue.

Apologies if any one is offended by this rant as I for one am waiting on either a posting here or a response in messages ( yes, i click names and send replies that I think don't belong in this thread ) from Slush.  If we post here specifics and not ' it don't work ' it's easier to get it resolved. Please and thank you.

Same, also getting IO errors in guiminer

i have a 10+ hours pending reward, why so slow to confirm...

Has anyone tried v*****.bitcoin.cz? Just wondering...

One of my bigger workers was happily submitting shares but showed zero on the stats page.  If there is nothing from Slush soon I'm going to jump ship.  This pool appears to be malfunctioning and running unmonitored.

Maybe you should use next workaround. Remove one card from a computer. Run cgminer and if it works you will get kernel for that card. If it doesn't work change SDK and run again. If hashrate is too low use diffident SDK/driver and remove .bin file from cgminer folder. When you find the best combination backup .bin file just in case. Now remove the card and put in other card. Do the same but don't delete first card .bin file only second card .bin file if you don't like hashrate. Now put both cards in and run cgminer. It might work.

And just in case. When running windows you need to plug monitor or null plug into card. Did you?

No problems here.

Pool down 4:55 PM EST or just me?