Yeah, obviously I'm totally cool with getting something that I value very highly for free, but that's way different than denigrating the company that currently offers the best deal to me. Glad you understand.
I have no problems with rooms charging rake either. They've got to pay the bills somehow. World Sports Exchange had a rake free room but it failed. Any thoughts on how you expect to fund things? |
|
|
|
|
Unfortunately running the pooled server is proving too taxing for my VPS host. They keep killing the server due to using too much CPU. sjaak on IRC has offered to host a server on 91.121.29.91 that runs full time on a dedicated machine (rather than a VPS). If sjaak posts here to confirm the offer I plan to turn my server off when it generates the next block (so all the existing contributers haven't wasted their time since the last block). sjaak's new server is currently running if you want to start using it now.
|
|
|
|
Where was the trouble when you attached the debugger? I tried to duplicate this here, but I don't have enough hash rate locally to overload the server. It sounds like a network issue to me, but it's possible it could be something else. Are you sure you have enough upload bandwidth to the server? Is your host throttling it?
I saw nothing obvious in the debugger. It still seemed to be stepping through the clients ok. Is it possible for a slow or malicious client to cause the server to block or slow down? I should have enough bandwidth. I have a similar server that serves a lot more traffic than this one running the pooled miner. That said my host has been killing the server for excessive CPU usage recently so anything is possible. Is anyone else willing to run/take over running the pool that might have a more reliable server or connection? |
|
|
|
I think we should definitely add a warning not to use MyBitcoin addresses until the problem has been found.
I added a warning to the pool page. |
|
|
|
Pls. correct me, doublec, if this isn't so.
It isn't so. They are definitely 'generated'. If you look at the block you'll see the one generation block is split amongst all the addresses: http://blockexplorer.com/b/97017. Each of those addresses will have a 'Generated' transaction. |
|
|
|
The MyBitcoin address is 1B8Dgkq4UtwVofQHN9TCay5ENfEz3k7Kbt.
And this address is shown in the block explorer.
MyBitcoin should forward the bitcoins to my client.
So it was a MyBitcoin address? I wonder if anyone else used a MyBitcoin address and if they got their coins too? The generated transactions appear differently in clients. They show as 'Generated' and don't become usable for 120 blocks. Non-gui clients can't even see them or access them in any way using bitcoind until that 120 block period has passed. Possibly something in the way MyBitcoin is setup stopped them from picking up that you got coins? Have you tried contacting them? |
|
|
|
not that I'm missing my bitcents, but the pool-mined block 97017 is now (97333) 316 blocks away.
And yet I didn't receive any bitcents...
Neither on MyBitcoin, nor on my Bitcoin client.
What went wrong? My fault? The servers fault?
Anyone else has this problem?
When did you contribute? Did you stop at any time? For the first few days the server was running the connected method, not contributed due to bugs in the later as described here: http://pastecoin.com/download.php?file=70Is the address you listed appearing in the block as shown in block explorer? |
|
|
|
|
The server got stuck idling and producing zero hashes again. I've temporarily fallen back to the previous server, version 1.2.1, until the problem is resolved. Note that 1.2.1 is averaging about 60% the CPU usage of 1.2.2.
|
|
|
|
puddinpop, some timestats.txt for the last few hours: section count time
BitcoinMinerRemote Handling Messages 3538540 6125980632
BitcoinMinerRemoteServer::AddDistributionFromContributed 7444 12161303
BitcoinMinerRemoteServer::BlockToJson 7444 37761410
BitcoinMinerRemoteServer::DecodeBase64 1137964 7965160
BitcoinMinerRemoteServer::EncodeBase64 14888 110513
BitcoinMinerRemoteServer::GetAllClientsCalculatedKHashFromBest 990 12888072
BitcoinMinerRemoteServer::GetAllClientsCalculatedKHashFromMeta 990 5102865
BitcoinMinerRemoteServer::GetOldestNonVerifiedMetaHashClient 1684875 13319578
BitcoinMinerRemoteServer::SendWork 7444 218351595
BitcoinMinerRemoteServer::Step 3538541 1986327641
MetaHashVerifier::Start 398 112139
MetaHashVerifier::Step 78488 1280946445
RemoteClientConnection::GetCalculatedKHashRateFromBestHash 104395 12802790
RemoteClientConnection::GetCalculatedKHashRateFromMetaHash 104395 5005396
RemoteClientConnection::GetNewestSentWorkWithMetaHash 1606785 8341113
RemoteClientConnection::GetSentWorkByID 1137964 3100622
RemoteClientConnection::MessageReady 327210958 585449940
RemoteClientConnection::ProtocolError 327210958 575656559
RemoteClientConnection::ReceiveMessage 1140525 300611249
RemoteClientConnection::SendMessage 20680 17677026
RemoteClientConnection::SetWorkVerified 384 1151
RemoteClientConnection::SocketReceive 753356 11741667
RemoteClientConnection::SocketSend 19110 1143503950
VerifyBestHash 1001002 6195863
|
|
|
|
|
The server got stuck in an idle state again. It was using 0% CPU and not processing requests. I'm building in debug mode now and I'll attach with a debugger if it happens again.
|
|
|
|
Something odd happened with the server. I noticed it was using 0 CPU as if no clients were connected. I connected a miner and I just got this repeated: Requesting a new block 1292156535151
Requesting a new block 1292156540258
Requesting a new block 1292156545364 So it was constantly 'requesting a new block'. Any thoughts on what might cause this? I restarted the server and the miner connected and worked fine. |
|
|
|
|
Is it possible that the new server code uses more CPU? Prior to the update I was averaging 60%, now it's 95%. It's hard to tell if it's because of more clients suddenly joining or the update (about 10 new clients joined). Maybe they're OpenCL clients and the server is just busier. It'd be great if the server could have stats about number of OpenCL, Cuda and CPU clients are connected.
|
|
|
|
I've updated to puddinpop's latest server code. There is also a new client. The new client displays the distribution method the server is using, can use multiple threads (no more needing to run multiple instances of the miner), and no longer dumps the 'best hash rate' to the console. There is also a new OpenCL remote miner: http://www.bluishcoder.co.nz/bitcoin-pool |
|
|
|
In the debug.log I get lines like this a lot (tens of thousands of lines) from some IP addresses: Client x.x.x.x sent metahash for block we don't know about! What causes this? Note that this is with the 20101206 release. |
|
|
|
The first post has been updated with a new release.
cmake-bitcoinr/CMakeLists.txt seems to be missing a line for remoteminerthreadcpu.cpp. There's a link error unless I add this. |
|
|
|
Hmm, mine currently says "Generated (0.60 matures in 27 more blocks)" but then says 0.00 under the Credit column, I assume this is just because the amount isn't added to the balance yet. Is this what is happening for you too maybe? Or maybe it is the rounding thing.
It's because the block hasn't matured yet. It should display the amount after that. |
|
|
|
The server will now send the contribution type to the clients, and the clients will display it upon connecting to the server. The server will also save timing stats to a text file periodically so that we can narrow down what the bottlenecks are. If you are running a server, please post your timing stats after the server has been up for a while.
I'll update the server I run today and post some stats when it's been running for a while. |
|
|
|
And besides, I wouldn't expect the pool mining service to cause any "Generated" message in anyone's client. Wouldn't it just come in as a regular payment?
As Theymos said, it definitely does show up as generated on all clients that participated. Do any of the address with amounts less than 0.01 in this block look familiar? http://blockexplorer.com/b/97017 |
|
|
|
|
Did you use the pool mining service at all? If so your share of contributions may be less than 0.01 and the bitcoin client is displaying it as 0.00 due to rounding.
|
|
|
|
The amount of bitcoin's being reported since the update from about a week or so ago seems to be cut in half. This was brought up before and it was quickly disregarded. So now I'm asking the other people that are running clients that are contributing to the pool to look at their numbers and see if it's off for you too.
A new block was generated by the pool today. The total amounts distributed in the recently generated block can be seen here: http://blockexplorer.com/b/97017 |
|
|
|
|
Show Posts
