Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 1009. (Read 4382653 times)
June 15, 2011, 01:28:04 AM
Something just popped in my mind and I have to ask. Ppl with the recent backend problems wouldn't be in california would you guys?
June 15, 2011, 01:13:16 AM
miner stopped connecting a few minutes ago. IP address is whitelisted.
connection refused/backend is not connected.
connection refused/backend is not connected.
June 15, 2011, 01:11:31 AM
Can we get wallet lock option when you have the time? I think many miners would want to see this.
Yes, actually I started to code it today, but then spent some time on that server configuration.
so glad to hear that
June 15, 2011, 01:09:40 AM
Is the pool down? I just a "backend is not connected" error message with a "call to bitcoind failed ... connection refused" My gf also mines here and she says her's is fine, so I pointed my miners at BTCGuild and I don't get any errors. It's just slush's pool for me.
June 15, 2011, 01:08:28 AM
Hi Slush,
I am connecting from two different locations. While one is fine, I can't connect from the other - it says MSG: backend is not connected
I am connecting from two different locations. While one is fine, I can't connect from the other - it says MSG: backend is not connected
June 14, 2011, 11:39:08 PM
I'd say it's a problem with his phase coil inducers. Rerouting power through his secondary transmogrifier manifold should do the trick. Worked last time it happened to me, at least.
Jiggle the handle. Works every time.
June 14, 2011, 10:13:35 PM
How do I fix this?
Looks like hardware error. But correct me if I'm wrong...
June 14, 2011, 07:52:28 PM
Can we get wallet lock option when you have the time? I think many miners would want to see this.
Yes, actually I started to code it today, but then spent some time on that server configuration.
June 14, 2011, 07:39:20 PM
Can we get wallet lock option when you have the time? I think many miners would want to see this.
June 14, 2011, 07:25:58 PM
Still happening. Are you still under attack?
Yes, but it has minimal impact to the pool, I see 2000 requests/second, which is expected. Also all my miners are working well.
Real problem is only higher packetloss (actually 14%), so miner can freeze for a moment while waiting for response from lost packet. But it depends on miner implementation, for example phoenix (which I'm using) is robust in this situation.
I'm actually configuring new beast machine which will act as pool firewall. It will be ready tomorrow, so people connecting to api.bitcoin.cz should be safe then.
June 14, 2011, 07:04:03 PM
Hey Slush,
After you got everything back to normal yesterday, all my miners were working perfectly. Things continued to work fine up to the 1.0Thash/s point. Once the load went over that I started getting the following console messages again (and lots of them).
warning: job finished miner is idle
Problems communicating with bitcoin RPC
After you got everything back to normal yesterday, all my miners were working perfectly. Things continued to work fine up to the 1.0Thash/s point. Once the load went over that I started getting the following console messages again (and lots of them).
warning: job finished miner is idle
Problems communicating with bitcoin RPC
We're under another attack right now, which is creating some packet loss. Actually it isn't ddos, network flood is coming from infiumhost.com. I'm already in touch with those guys.
Still happening. Are you still under attack?
June 14, 2011, 06:42:34 PM
How do I fix this?
Looks like hardware error. But correct me if I'm wrong...
June 14, 2011, 05:32:35 PM
How do I fix this?
What is "this Verification failed, check hardware" ?
Quote
2011-06-14 02:53:35: Listener for "Slush Sec": 14/06/2011 02:53:35, Problems communicating with bitcoin RPC
2011-06-14 02:53:41: Listener for "Slush 2 sec": 14/06/2011 02:53:41, Problems communicating with bitcoin RPC
2011-06-14 04:05:44: Listener for "Slush Prim": 14/06/2011 04:05:44, Problems communicating with bitcoin RPC
2011-06-14 08:03:52: Listener for "Slush Prim": Verification failed, check hardware!
2011-06-14 09:32:00: Listener for "Slush2 Prim": Verification failed, check hardware!
2011-06-14 02:53:41: Listener for "Slush 2 sec": 14/06/2011 02:53:41, Problems communicating with bitcoin RPC
2011-06-14 04:05:44: Listener for "Slush Prim": 14/06/2011 04:05:44, Problems communicating with bitcoin RPC
2011-06-14 08:03:52: Listener for "Slush Prim": Verification failed, check hardware!
2011-06-14 09:32:00: Listener for "Slush2 Prim": Verification failed, check hardware!
What is "this Verification failed, check hardware" ?
Please guys, can someone tell me how I can fix this?
June 14, 2011, 02:39:24 PM
Hey Slush,
After you got everything back to normal yesterday, all my miners were working perfectly. Things continued to work fine up to the 1.0Thash/s point. Once the load went over that I started getting the following console messages again (and lots of them).
warning: job finished miner is idle
Problems communicating with bitcoin RPC
After you got everything back to normal yesterday, all my miners were working perfectly. Things continued to work fine up to the 1.0Thash/s point. Once the load went over that I started getting the following console messages again (and lots of them).
warning: job finished miner is idle
Problems communicating with bitcoin RPC
We're under another attack right now, which is creating some packet loss. Actually it isn't ddos, network flood is coming from infiumhost.com. I'm already in touch with those guys.
June 14, 2011, 02:11:25 PM
Hey Slush,
After you got everything back to normal yesterday, all my miners were working perfectly. Things continued to work fine up to the 1.0Thash/s point. Once the load went over that I started getting the following console messages again (and lots of them).
warning: job finished miner is idle
Problems communicating with bitcoin RPC
Nothing has changed on my end. And yes I am using the new server address in my client.
Can you please look into this?
Thanks.
After you got everything back to normal yesterday, all my miners were working perfectly. Things continued to work fine up to the 1.0Thash/s point. Once the load went over that I started getting the following console messages again (and lots of them).
warning: job finished miner is idle
Problems communicating with bitcoin RPC
Nothing has changed on my end. And yes I am using the new server address in my client.
Can you please look into this?
Thanks.
Same here.
June 14, 2011, 01:36:02 PM
Hey Slush,
After you got everything back to normal yesterday, all my miners were working perfectly. Things continued to work fine up to the 1.0Thash/s point. Once the load went over that I started getting the following console messages again (and lots of them).
warning: job finished miner is idle
Problems communicating with bitcoin RPC
Nothing has changed on my end. And yes I am using the new server address in my client.
Can you please look into this?
Thanks.
After you got everything back to normal yesterday, all my miners were working perfectly. Things continued to work fine up to the 1.0Thash/s point. Once the load went over that I started getting the following console messages again (and lots of them).
warning: job finished miner is idle
Problems communicating with bitcoin RPC
Nothing has changed on my end. And yes I am using the new server address in my client.
Can you please look into this?
Thanks.
June 14, 2011, 11:44:14 AM
I'm having lot of fun with another attack, but looks like IP whitelist really works. There is significant packet loss, but mining is still up. Without whitelist it would be already down completely, like earlier today. There is important ongoing change in pool architecture, so:
Please point your miners against api.bitcoin.cz
If you already changed miners to mining2.bitcoin.cz, you don't need change anything. I'll need to split website and mining backend to separate machines, so mining cannot use same IP as website anymore. Website will be still on mining.bitcoin.cz, miners on api.bitcoin.cz .
I'll send email to all registered users with all necessary changes with all that summary about IP whitelisting and necessary changes in miner configuration. I believe that this changes and updates will make pool more robust in future attacks.
Please point your miners against api.bitcoin.cz
If you already changed miners to mining2.bitcoin.cz, you don't need change anything. I'll need to split website and mining backend to separate machines, so mining cannot use same IP as website anymore. Website will be still on mining.bitcoin.cz, miners on api.bitcoin.cz .
I'll send email to all registered users with all necessary changes with all that summary about IP whitelisting and necessary changes in miner configuration. I believe that this changes and updates will make pool more robust in future attacks.
Hey slush, how long do I have to change my miners over to api.bitcoin.cz before mining.bitcoin.cz stops accepting work?
June 14, 2011, 07:46:23 AM
I already asked Kiv to modify this in GUI miner and announce 'bugfix' release. Hope it will be available soon, I understand that modifying ini files isn't what common user of GUI miner want...
June 14, 2011, 07:30:19 AM
Quote
If necessary could you explain in detail please what steps are necessary when using GUIMiner. Do we have to change the content of the 'servers.ini' file in the guiminer folder? and what changes are advisable?
Thanks
Thanks
On the same profile you have open for slush in guiminer now:
1. Chose "other" from the server dropdown box instead of slush's pool.
2. Under "Host:" put "api.bitcoin.cz".
3. Make sure Port is 8332
4. Username and password should have been kept from the old profile. If not, just put them in as normal for slush's pool. Same for the flags.
5. That's it.
What you describe is definitely the solution for the moment I used in one of my machines already and File/save settings will make it stay after a reboot of that system.
But coming back after some weeks to other machines it would be better you could use your GUIMine by intuition what means select 'Slush' and not 'Other' when you want 'Slush'.
To get 'Slush' working with 'api.bitcoin.cz' I guess you have to change the server.ini file in the guiminer folder.
The server.ini file has got server sections, the first one being:
Code:
"name": "slush's pool",
"host": "mining.bitcoin.cz",
"url": "http://mining.bitcoin.cz",
"port": 8332,
"balance_token_url": "http://mining.bitcoin.cz/accounts/token-manage/",
"balance_host": "mining.bitcoin.cz",
"balance_url": "/accounts/profile/json/%s"
Quote
Unfortunately it is necessary because I need to split site/mining traffic to improve firewall rules.
So I'll teach my machines to visit "api.bitcoin.cz" instead of "mining.bitcoin.cz" - Thanks Slush
June 14, 2011, 07:07:58 AM
Everything seems working again (without changing anything on my mining machines).
Do you think it's really necessary to switch to a new adress like api.bitcoin.cz. I would prefer not to, as you never should change a running system.
Do you think it's really necessary to switch to a new adress like api.bitcoin.cz. I would prefer not to, as you never should change a running system.
Unfortunately it is necessary because I need to split site/mining traffic to improve firewall rules. As is mentioned above, it is possible to configure guiminer with new address pretty easily, but I'll ask Kiv to change pool's url for next guiminer release...
Jump to: