Search content
Sort by
Showing 15 of 15 results by Smerks
I guess I shouldve been more specific as well Im using GUIMiner scrypt
http://i41.tinypic.com/2lxijif.jpg
http://i41.tinypic.com/2lxijif.jpg
Great guide especially for someone new to this, Im set up but getting more stales than I should while solo mining (5 or so since last night) with my hash rate just under 600khash/s. I read that it had something to do with long polling since I was seeing this "No suitable long-poll found for http://127.0.0.1:9332", so I set up a backup to my coinotron acct which I read somewhere else should solve this.
Im seeing the following and was wondering is all well with my setup?
EDIT: I have a verbose flag set to see all messages for now.
Im seeing the following and was wondering is all well with my setup?
Code:
2013-06-25 15:25:29: Listener for "SOLO": [2013-06-25 15:25:29] Stratum from pool 1 detected new block
2013-06-25 15:26:28: Listener for "SOLO": [2013-06-25 15:26:28] New block: c7abb08ed3e1fdf3... diff 50.4M
2013-06-25 15:26:28: Listener for "SOLO": [2013-06-25 15:26:28] Stratum from pool 1 detected new block
2013-06-25 15:28:01: Listener for "SOLO": [2013-06-25 15:28:00] Stratum connection to pool 1 interrupted
2013-06-25 15:28:01: Listener for "SOLO": [2013-06-25 15:28:00] Closing socket for stratum pool 1
2013-06-25 15:28:01: Listener for "SOLO": [2013-06-25 15:28:01] Stratum authorisation success for pool 1
2013-06-25 15:29:17: Listener for "SOLO": [2013-06-25 15:29:15] New block: 14aea8e625d44248... diff 50.4M
2013-06-25 15:29:17: Listener for "SOLO": [2013-06-25 15:29:15] Stratum from pool 1 detected new block
2013-06-25 15:30:48: Listener for "SOLO": [2013-06-25 15:30:47] Stratum connection to pool 1 interrupted
2013-06-25 15:30:48: Listener for "SOLO": [2013-06-25 15:30:47] Closing socket for stratum pool 1
2013-06-25 15:30:49: Listener for "SOLO": [2013-06-25 15:30:48] Stratum authorisation success for pool 1
2013-06-25 15:26:28: Listener for "SOLO": [2013-06-25 15:26:28] New block: c7abb08ed3e1fdf3... diff 50.4M
2013-06-25 15:26:28: Listener for "SOLO": [2013-06-25 15:26:28] Stratum from pool 1 detected new block
2013-06-25 15:28:01: Listener for "SOLO": [2013-06-25 15:28:00] Stratum connection to pool 1 interrupted
2013-06-25 15:28:01: Listener for "SOLO": [2013-06-25 15:28:00] Closing socket for stratum pool 1
2013-06-25 15:28:01: Listener for "SOLO": [2013-06-25 15:28:01] Stratum authorisation success for pool 1
2013-06-25 15:29:17: Listener for "SOLO": [2013-06-25 15:29:15] New block: 14aea8e625d44248... diff 50.4M
2013-06-25 15:29:17: Listener for "SOLO": [2013-06-25 15:29:15] Stratum from pool 1 detected new block
2013-06-25 15:30:48: Listener for "SOLO": [2013-06-25 15:30:47] Stratum connection to pool 1 interrupted
2013-06-25 15:30:48: Listener for "SOLO": [2013-06-25 15:30:47] Closing socket for stratum pool 1
2013-06-25 15:30:49: Listener for "SOLO": [2013-06-25 15:30:48] Stratum authorisation success for pool 1
EDIT: I have a verbose flag set to see all messages for now.
Re: [12000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
The -f 40 is for when Im using the machine to make it more responsive.
Why -f 40? isnt that knocking 20+mh/s off? also I dont believe -v does anything for 7x series cards
direct ip's are below if your resolution is bad
Name: stratum.bitcoin.cz
Addresses: 54.225.117.74
95.211.52.40
54.215.3.101
Can someone possibly explain why I can no longer mine on Slush's pool, is this error related to the DDOS? Im using GUIMiner with these flags ( -v -w 256 -f 40 ) on my HD7970. I get the below then it just hangs, I can mine my backup fine but since earlier today I cannot mine slush.
2013-06-20 00:55:23: Listener for "Smerks Slush" started
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, started OpenCL miner on platform 0, device 0 (Tahiti)
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, checking for stratum...
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, no response to getwork, using as stratum
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, No JSON object could be decoded
2013-06-20 00:55:35: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:35, Failed to subscribe
2013-06-20 00:55:37: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:37, IO errors - 1, tolerance 2
2013-06-20 00:55:23: Listener for "Smerks Slush" started
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, started OpenCL miner on platform 0, device 0 (Tahiti)
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, checking for stratum...
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, no response to getwork, using as stratum
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, No JSON object could be decoded
2013-06-20 00:55:35: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:35, Failed to subscribe
2013-06-20 00:55:37: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:37, IO errors - 1, tolerance 2
Why -f 40? isnt that knocking 20+mh/s off? also I dont believe -v does anything for 7x series cards
direct ip's are below if your resolution is bad
Name: stratum.bitcoin.cz
Addresses: 54.225.117.74
95.211.52.40
54.215.3.101
Re: [12000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
Can someone possibly explain why I can no longer mine on Slush's pool, is this error related to the DDOS? Im using GUIMiner with these flags ( -v -w 256 -f 40 ) on my HD7970. I get the below then it just hangs, I can mine my backup fine but since earlier today I cannot mine slush.
2013-06-20 00:55:23: Listener for "Smerks Slush" started
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, started OpenCL miner on platform 0, device 0 (Tahiti)
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, checking for stratum...
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, no response to getwork, using as stratum
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, No JSON object could be decoded
2013-06-20 00:55:35: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:35, Failed to subscribe
2013-06-20 00:55:37: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:37, IO errors - 1, tolerance 2
2013-06-20 00:55:23: Listener for "Smerks Slush" started
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, started OpenCL miner on platform 0, device 0 (Tahiti)
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, checking for stratum...
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, no response to getwork, using as stratum
2013-06-20 00:55:25: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:25, No JSON object could be decoded
2013-06-20 00:55:35: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:35, Failed to subscribe
2013-06-20 00:55:37: Listener for "Smerks Slush": api2.bitcoin.cz:8332 20/06/2013 00:55:37, IO errors - 1, tolerance 2
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
I am surprised you still get a chance to play games lol. When I discovered Mining my gaming days seemed to of come to an end, fuck , I bought a 7970 and have only played 1 frickin' game lol, cs:go, and that was to check that I hadn't fucked my card! haha. I needs me bitcoins!!
LOL Im glad Im not the only one who did that. The one good thing is playing WoW isnt really affected by mining much I get around 600Mhash while in WoW. Seems WoW is more dependent on processor for some odd reason, probably old code mixed with new, etc etc.
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
Weather cut the power on my machine while I'm at work. Happened yesterday aswell. Will have to wait until day's end to restart 
Might be worth getting a UPS - will keep you up for half an hour or so - maybe enough to see you through short outages...
I must have gone through a dozen of these. Different brands, different models. My conclusion: They're alwarys dead by the time you need them. Apparently we just haven't gotten that far along with battery technology to make a reliable backup unit. The only advancement they do is to make the alarm more annoying and more difficult to deactivate. Either that or the guys at the supply depot recognise my adress and they're like:
"This guys again! Hey Joe, lets go find him another reject unit."
Ive tried many and the only reliable brand for me over years and years has been APC.
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
Rate of invalid blocks is getting ridiculous,
18120 2013-05-20 15:38:18 0:04:08 Processing... 237069 25.16931001 99 confirmations left
Is not even found in blockchain.info
18120 2013-05-20 15:38:18 0:04:08 Processing... 237069 25.16931001 99 confirmations left
Is not even found in blockchain.info
Hmm, Bitminter have had 2 invalids in last 12 days - we have had 9... I think there is something wrong now...
Lucko, just because I think there may be a latency issue with bitcoind - doesn't mean I agree anything you say - and doesn't mean I still don't think you are a bit of an idiot. I'll stay mining here come what may and will not be slagging off the pool every five minutes.
But doesnt the fact that Slush hasnt even poked his head up to say hes aware make you somewhat concerned?
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
I had a payout from Slush over an hour ago and still not one confirmation on it
http://i41.tinypic.com/35krg2b.jpg
http://i41.tinypic.com/35krg2b.jpg
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
Im a bit new to all this and have one question, with all this uncertainty in the last few days with invalids and improperly calculated blocks that fix themselves in time is it normal for Slush to not respond or is this out of the ordinary?
First of all, your payout from SatoshiDice won't confirm until the original transaction does. SatoshiDice does this to prevent cheating: if the wager transaction is any way fraudulent or invalid, so is the payout, so the cheater wins nothing.
As for the original transaction not confirming, that is because the sender did not pay a transaction fee, even though a fee was required for this transaction. As a result, it (and your payout) will likely take an extremely long time to be confirmed.
What's strange is that you were actually able to send this transaction in the first place. Most clients do not allow you to spend unconfirmed funds, precisely to avoid this kind of issue. What client or wallet service were you using?
EDIT: Typo.
As for the original transaction not confirming, that is because the sender did not pay a transaction fee, even though a fee was required for this transaction. As a result, it (and your payout) will likely take an extremely long time to be confirmed.
What's strange is that you were actually able to send this transaction in the first place. Most clients do not allow you to spend unconfirmed funds, precisely to avoid this kind of issue. What client or wallet service were you using?
EDIT: Typo.
Could you be clearer on what you mean by extremely long time for confirmation, Im new to all this and was just wondering.