|
Flashman
|
 |
December 26, 2013, 01:31:41 AM
Last edit: December 26, 2013, 03:12:05 AM by Flashman |
|
Aaaargh, my ISP had decided to leave me offline for an hour or so, and I thought my mining host reconnected back fine, but apparently not, it's been bouncing off mint.bitminter.com:3333 so I tried 5050 same thing... I am wondering if it's me, or whether my IP change with the downtime put me in some blocked range. I'm on a 198.13.xx.xx one right now.
Edit: not just BFGminer, the java client appears not to connect either (and it's only finding one ASIC...)
Edit2: hashing on multipool just fine... still won't connect to bitminter.
|
TL;DR See Spot run. Run Spot run. .... .... Freelance interweb comedian, for teh lulz >>> 1MqAAR4XkJWfDt367hVTv5SstPZ54Fwse6
Bitcoin Custodian: Keeping BTC away from weak heads since Feb '13, adopter of homeless bitcoins. |
|
|
DrHaribo (OP)
Legendary
 Offline
Activity: 2730
Merit: 1034
Needs more jiggawatts
|
|
December 26, 2013, 03:27:36 AM |
|
Mining service restart... will only take a second or two.
|
|
|
|
|
brioche
|
|
December 26, 2013, 03:50:41 AM |
|
Mining service restart... will only take a second or two.
haven't been able to connect for 4-5 hours, keeps saying remote connection denied? |
＼ ＼ ＼ ＼＼＼＼＼＼＼＼＼＼＼＼＼＼＼＼◥◣◢◤／／／／／／／／／／／／／／／／ ／ ／ ／
❖ North Carolina ❖ First in Flight ❖ ／ ／ ／ ／／／／／／／／／／／／／／／／◢◤◥◣＼＼＼＼＼＼＼＼＼＼＼＼＼＼＼＼ ＼ ＼ ＼ |
|
|
|
Flashman
|
|
December 26, 2013, 04:07:46 AM |
|
w00t, back on.
edit: very briefly and bounced off again...
Though bfg showing a network failure that bounced it to next failover pool so might not have been bitminter... but I'm fed up of messing with it now, it can go back to bitminter if it feels like it later.
|
TL;DR See Spot run. Run Spot run. .... .... Freelance interweb comedian, for teh lulz >>> 1MqAAR4XkJWfDt367hVTv5SstPZ54Fwse6
Bitcoin Custodian: Keeping BTC away from weak heads since Feb '13, adopter of homeless bitcoins. |
|
|
MoreBloodWine
Legendary
Offline
Activity: 1064
Merit: 1001
|
|
December 27, 2013, 04:54:47 AM |
|
For those of you "as of this reply" that mine with with anywhere from 550 to 650 Gh/s in BitMinter of course heh. What do you seem to be averaging per day since the last diff increase and how did it compare to what you were averaging before the increase ?
|
To be decided...
|
|
|
|
Flashman
|
|
December 27, 2013, 01:40:04 PM |
|
We haven't really had many "average" days lately, we were super lucky on the 23rd, but have been unlucky since... I THINK we're doing about 8 blocks a day average, and at a little under 200Gh I'm getting about 0.01 a block, so 600 should be getting a little over 0.03ish and about a quarter coin a day on average.
|
TL;DR See Spot run. Run Spot run. .... .... Freelance interweb comedian, for teh lulz >>> 1MqAAR4XkJWfDt367hVTv5SstPZ54Fwse6
Bitcoin Custodian: Keeping BTC away from weak heads since Feb '13, adopter of homeless bitcoins. |
|
|
|
Cascaders28
|
|
December 27, 2013, 01:46:07 PM |
|
**SNIP** In other news, do the Chili Miners work with the BitMinter client?
In the latest version of Bitminter client I made a fix for the Chili firmware BFL-incompatibility, but I couldn't get anyone to test whether it works. Worth a try.  Awesome! I've got a pair of them coming to me so I'll let you know how things look probably next week. Well this didn't work out as planned so I'm still hunting for some Chilis...perhaps I can try it out in early 2014  |
|
|
|
|
|
|
DrHaribo (OP)
Legendary
Offline
Activity: 2730
Merit: 1034
Needs more jiggawatts
|
|
December 27, 2013, 06:55:46 PM |
|
Banning botnets and fending off their attacks. Bit of a bumpy ride at the moment. But looking better already.
To botnet herders: connecting thousands of cpuminer instances using getwork from 1 IP is no better than from thousands of IPs. It still causes a lot of load for almost no effect, and you will still get banned. Also, advice on illegal botnet activity: earning 0.01 BTC per year is not worth going to jail.
|
|
|
|
|
Flashman
|
|
December 27, 2013, 07:51:20 PM |
|
|
TL;DR See Spot run. Run Spot run. .... .... Freelance interweb comedian, for teh lulz >>> 1MqAAR4XkJWfDt367hVTv5SstPZ54Fwse6
Bitcoin Custodian: Keeping BTC away from weak heads since Feb '13, adopter of homeless bitcoins. |
|
|
|
SgtMoth
|
|
December 27, 2013, 09:00:26 PM |
|
This bullshit keeps knocking my machines down.
|
|
|
|
|
|
hayseed
|
|
December 28, 2013, 04:43:44 AM |
|
Are there still issues? I am trying to connect a stratum pool. It will work for about 10 mins then workers shows 0 and full size stats shows a missing box even though the mining_proxy.py shows activity. Later on it might start working again then it repeats with zero activity.
|
|
|
|
|
|
cenicsoft
|
|
December 28, 2013, 04:52:40 AM |
|
To botnet herders: connecting thousands of cpuminer instances using getwork from 1 IP is no better than from thousands of IPs.
May be time to drop getwork support... |
|
|
|
|
smoothrunnings
|
|
December 28, 2013, 05:55:27 AM |
|
Banning botnets and fending off their attacks. Bit of a bumpy ride at the moment. But looking better already.
To botnet herders: connecting thousands of cpuminer instances using getwork from 1 IP is no better than from thousands of IPs. It still causes a lot of load for almost no effect, and you will still get banned. Also, advice on illegal botnet activity: earning 0.01 BTC per year is not worth going to jail.
Is there something wrong with the pool, my Avalon's aren't hashing from your pool, they are set to hash from you first and failover in the event your pools stop working? |
|
|
|
|
|
ct1aic
|
|
December 28, 2013, 09:30:35 AM |
|
Are there still issues? I am trying to connect a stratum pool. It will work for about 10 mins then workers shows 0 and full size stats shows a missing box even though the mining_proxy.py shows activity. Later on it might start working again then it repeats with zero activity.
I had same problem... 3 of my RPI's with bfgminer 3.9.0 went to the second pool, for more than 1 hour. For them, the BitMinter pool was down, but I still had 2 other mining to same pool. Very strange indeed. |
Rui Costa, Portugal - BTC : 1ct1aicGoUVpZeovsw3cCcPJZJHV5JXtW
|
|
|
DrHaribo (OP)
Legendary
Offline
Activity: 2730
Merit: 1034
Needs more jiggawatts
|
|
December 28, 2013, 12:38:07 PM |
|
Wow, 4 blocks in a row on the blockchain today. Everything should be running smoothly now. If you have issues there are two types of IP based filtering in use. There's a botnet ban list where IPs sit for some time. And then there is the anti ddos which may accidentally filter you along with attackers during an attack. We're working to improve on this. This should only last a few minutes before you can mine again though. If you are unable to mine for hours then you could be on the botnet ban list, or it could be a different issue entirely. In that case use the contact form ("contact" menu) on the website and I'll see if I can figure out what the problem is. Hehe, this gave me a good laugh. That's exactly what it's like. |
|
|
|
Asinine
Member
Offline
Activity: 62
Merit: 10
|
|
December 28, 2013, 04:47:34 PM |
|
Wow, we get an amazing spree of good luck and my shift work is in the toilet due to a DDoS, which leaves me wondering if that is a coincidence or not.
|
|
|
|
|
|
Zoella
|
|
December 28, 2013, 05:24:14 PM |
|
Stats seem odd as well. New to the pool, but it usually seems to average ~450T and ~1200 workers. Right now we are at ~340T and ~7800 workers.
|
|
|
|
|
DrHaribo (OP)
Legendary
Offline
Activity: 2730
Merit: 1034
Needs more jiggawatts
|
|
December 28, 2013, 05:37:04 PM |
|
Looks like about 200-300 users are blocked by the anti ddos currently. If you are one of them, you should be able to connect again within a minute or two. Apologies for the inconvenience.
|
|
|
|
Asinine
Member
Offline
Activity: 62
Merit: 10
|
|
December 28, 2013, 06:19:37 PM |
|
Chainminer-Bitfury-DDoS note:
You may have to manually generate and modify a best.cnf in order to turn off auto-tuning for your chips. Normally, you would want this on. But, when the pool gets nailed, Chainminer seems to want to down-clock entire banks of chips. And, they may not return to normal after the DDoS subsides.
Chips will start off hashing very slowly until they warm up if the clock rate is manually set too high.
I originally posted this in the miner thread, but then realized that thread was specific to the Bitminter Java client. That post has been deleted.
|
|
|
|
|
|
