2 hours without a hash @ 160Mhash borders on impossible.
In a pool, perhaps. But in solo mode, it will take an average of 135 days to generate a block at current difficulty.
http://www.alloscomp.com/bitcoin/old_calculator.php
hash != block
Topic: what just happened? (Read 2076 times)
In a pool, perhaps. But in solo mode, it will take an average of 135 days to generate a block at current difficulty.
http://www.alloscomp.com/bitcoin/old_calculator.php
hash != block
2 hours without a hash @ 160Mhash borders on impossible.
In a pool, perhaps. But in solo mode, it will take an average of 135 days to generate a block at current difficulty.
http://www.alloscomp.com/bitcoin/old_calculator.php
Do you mean - difficulty 1 hash ?
2 hours without a hash @ 160Mhash borders on impossible.
Well, maybe you just unlucky. Thats a lottery after all.
Do you checked how much connections your bitcoin client have ?
53 as of right now
Do you checked how much connections your bitcoin client have ?
Problem with solo mining, that 160 m\hash not anough to expect solved block in 5 hours, or even a week.
Pools let you to solve difficulty 1 hashes, that called shares and acts like indicator that you running correctly and your part in current pool work.
Pools let you to solve difficulty 1 hashes, that called shares and acts like indicator that you running correctly and your part in current pool work.
Thanks for your suggestion... actually I've solved 3 blocks in 2 1/2 months @ $8 USD it is profitable for me. at any rate, this computer is only fallback for the largest part of my network. well it was until earlier today. the other clients on my network are having the same problem.
they are all run with the -server switch and rpcuser and pass in the .conf file.
Problem with solo mining, that 160 m\hash not anough to expect solved block in 5 hours, or even a week.
Pools let you to solve difficulty 1 hashes, that called shares and acts like indicator that you running correctly and your part in current pool work.
Pools let you to solve difficulty 1 hashes, that called shares and acts like indicator that you running correctly and your part in current pool work.
I just noticed that my client was also acting up, I'm making around 160 Mhash but haven't found a hash in a couple hours. but i can connect to say btcguild and produce hashes almost instantly. switch back to solo and not find any hashes.
Just to make sure: Did you run bitcoin.exe with the -server flag?
no. i run linux.
./bitcoind
with rpcuser and rpcpassword in the ~/.bitcoin/bin/64/bitcoin.conf file.
EDIT: ...and those local Bitcoin clients are working now.
EDIT: i mean; ~/.bitcoin/bitcoin.conf
Bad connections of client discussed before, in tech section.
Fast temporary solution is on wiki
https://en.bitcoin.it/wiki/Fallback_Nodes
Fast temporary solution is on wiki
https://en.bitcoin.it/wiki/Fallback_Nodes
Just to make sure: Did you run bitcoin.exe with the -server flag?
2.) i couldn't start a local Bitcoin client on any of my miners for the period of the outtage. did anyone else have that problem?
I didn't have this problem at all. Did you have them all pointed to pools?
I'm in the middle of deciding whether or not I want to use some of my available permanent hosts for Bitcoin nodes. I was watching my recent connections.
For the two nodes that I don't pay-per bandwidth for, the connection count went from 160 and 156 to 18 and 32.....
Peer connections going from 300+ to 50 is a little weird, no?
I checked the hosts and there were no signs of repeated connects, login guessing or denial of service-looking-things, so nodes weren't affected.
As of whenever this posts goes up.. I've got about 100 connections.
I'm more interested in being a node than a miner.
no. i started local clients, figuring i'd take advantage of the outtage to do a little solo mining. just rpcuser and rpcpassword in .conf - the usual. i couldn't get a single connection out of four local clients. not one connection.
DDoS from Russia, is what the word is.
but what were they attacking? it wasn't just slush, or just deepbit.
i'd still like to know if anyone else had trouble starting their local client.
if it was an actual DDoS - from wherever - it was only a test. too short.
the pools are going to have to establish whitelists...
Only deepbit has announced it was a DDoS... I haven't heard anything from slush.
deepbit said they did "something" to resolve the DDoS issue... perhaps a router rule, or something. So, I don't think ruling it out as a DDoS because of it's length is correct. It could have very well been a DDoS... these things pop up from time to time... the pools seem to roll with the punches, and pop back online a few minutes/hours later.
DDoS from Russia, is what the word is.
but what were they attacking? it wasn't just slush, or just deepbit.
i'd still like to know if anyone else had trouble starting their local client.
if it was an actual DDoS - from wherever - it was only a test. too short.
the pools are going to have to establish whitelists...
2.) i couldn't start a local Bitcoin client on any of my miners for the period of the outtage. did anyone else have that problem?
I didn't have this problem at all. Did you have them all pointed to pools?
I'm in the middle of deciding whether or not I want to use some of my available permanent hosts for Bitcoin nodes. I was watching my recent connections.
For the two nodes that I don't pay-per bandwidth for, the connection count went from 160 and 156 to 18 and 32.....
Peer connections going from 300+ to 50 is a little weird, no?
I checked the hosts and there were no signs of repeated connects, login guessing or denial of service-looking-things, so nodes weren't affected.
As of whenever this posts goes up.. I've got about 100 connections.
I'm more interested in being a node than a miner.
DDoS from Russia, is what the word is.
need data...
1.) the two biggest pools go down.
a.) were any of the other pools affected?
2.) i couldn't start a local Bitcoin client on any of my miners for the period of the outtage. did anyone else have that problem?
has anyone noticed any communication difficulties on 8332, or 8337?
that was weird. and short. it didn't appear to be localized.
comments?
1.) the two biggest pools go down.
a.) were any of the other pools affected?
2.) i couldn't start a local Bitcoin client on any of my miners for the period of the outtage. did anyone else have that problem?
has anyone noticed any communication difficulties on 8332, or 8337?
that was weird. and short. it didn't appear to be localized.
comments?
Jump to: