Reference 10:00 CST.
Poor eleuthria. In case nobody's said it lately, thanks for setting up the pool and hitfixing issues for us! I know in terms of bitcoins generated for you so far it probably hasn't been worth it so far.
Thank you! 
Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 143. (Read 379078 times)
May 21, 2011, 10:07:36 AM
Pool down again.
Reference 10:00 CST.
Poor eleuthria. In case nobody's said it lately, thanks for setting up the pool and hitfixing issues for us! I know in terms of bitcoins generated for you so far it probably hasn't been worth it so far. Thank you!
Reference 10:00 CST.
Poor eleuthria. In case nobody's said it lately, thanks for setting up the pool and hitfixing issues for us! I know in terms of bitcoins generated for you so far it probably hasn't been worth it so far.
Thank you! May 21, 2011, 09:53:12 AM
i still get stale shares a lot.
May 21, 2011, 09:43:51 AM
Pool is back up. I have an idea of what may have caused it.
I also added a watchdog monitor to the pool processes, and added the pool & bitcoind processes as startup scripts so the server should auto recover in less than 20 seconds if it does happen again.
I also added a watchdog monitor to the pool processes, and added the pool & bitcoind processes as startup scripts so the server should auto recover in less than 20 seconds if it does happen again.
Not sure about yours but my cron is set to run cron.daily at 0625. Something in the cron process freaking out the system? Was it a fresh install when you moved to the new hardware, or did you copy the current system across? Maybe looking for something that's not there anymore or moved?
May 21, 2011, 09:35:07 AM
Pool is back up. I have an idea of what may have caused it.
I also added a watchdog monitor to the pool processes, and added the pool & bitcoind processes as startup scripts so the server should auto recover in less than 20 seconds if it does happen again.
I also added a watchdog monitor to the pool processes, and added the pool & bitcoind processes as startup scripts so the server should auto recover in less than 20 seconds if it does happen again.
May 21, 2011, 08:58:22 AM
pool down again :<
[21/05/2011 06:42:52] LP: New work pushed
[21/05/2011 06:43:04] Warning: work queue empty, miner is idle
[21/05/2011 06:43:22] Disconnected from server
for tracking purposes. Time is GMT-7
It appears the pool is down for everybody... Happened about this time yesterday too.
Yeah and he didn't have time to debug it yesterday. That's why I posted the log so he would have an idea where to start looking to find out what was going on with the system at that time.
May 21, 2011, 08:54:51 AM
pool down again :<
[21/05/2011 06:42:52] LP: New work pushed
[21/05/2011 06:43:04] Warning: work queue empty, miner is idle
[21/05/2011 06:43:22] Disconnected from server
for tracking purposes. Time is GMT-7
It appears the pool is down for everybody... Happened about this time yesterday too.
May 21, 2011, 08:50:56 AM
pool down again :<
[21/05/2011 06:42:52] LP: New work pushed
[21/05/2011 06:43:04] Warning: work queue empty, miner is idle
[21/05/2011 06:43:22] Disconnected from server
for tracking purposes. Time is GMT-7
May 21, 2011, 08:49:26 AM
pool down again :<
May 21, 2011, 06:26:01 AM
I've contacted ufasoft for some assistance in getting the compatibility with his miner fixed.
In other news, we crossed 100 gH/sec a while ago, and are still seeing a steady rise. The new hardware is having no issues handling this additional load based off the reports in the IRC channel.
Many updates will be going live in the next 48 hours now that my attention is allowed to move from scaling/hardware to software updates.
In other news, we crossed 100 gH/sec a while ago, and are still seeing a steady rise. The new hardware is having no issues handling this additional load based off the reports in the IRC channel.
Many updates will be going live in the next 48 hours now that my attention is allowed to move from scaling/hardware to software updates.
Hopefully more speed will minimize the variance some and make for shorter rounds, because it's making my payments smaller even though I just increased my hashing rate.
Theoretically yes, in actuality, not all the time. Even deepbit has been getting 1 hour long sessions before getting a solve, and that's at 1 Th/s. Simple math would say that a 10 hr block @ 100 GH/s would be acceptable, when I think a lot of people would get frustrated if it went that long and some would hop over to another pool.
May 21, 2011, 05:52:12 AM
I've contacted ufasoft for some assistance in getting the compatibility with his miner fixed.
In other news, we crossed 100 gH/sec a while ago, and are still seeing a steady rise. The new hardware is having no issues handling this additional load based off the reports in the IRC channel.
Many updates will be going live in the next 48 hours now that my attention is allowed to move from scaling/hardware to software updates.
In other news, we crossed 100 gH/sec a while ago, and are still seeing a steady rise. The new hardware is having no issues handling this additional load based off the reports in the IRC channel.
Many updates will be going live in the next 48 hours now that my attention is allowed to move from scaling/hardware to software updates.
Hopefully more speed will minimize the variance some and make for shorter rounds, because it's making my payments smaller even though I just increased my hashing rate.
May 21, 2011, 03:52:41 AM
Throwing 100Mh/s your way, congrats on hitting 100 gH/sec!
May 21, 2011, 03:40:39 AM
I've contacted ufasoft for some assistance in getting the compatibility with his miner fixed.
In other news, we crossed 100 gH/sec a while ago, and are still seeing a steady rise. The new hardware is having no issues handling this additional load based off the reports in the IRC channel.
Many updates will be going live in the next 48 hours now that my attention is allowed to move from scaling/hardware to software updates.
In other news, we crossed 100 gH/sec a while ago, and are still seeing a steady rise. The new hardware is having no issues handling this additional load based off the reports in the IRC channel.
Many updates will be going live in the next 48 hours now that my attention is allowed to move from scaling/hardware to software updates.
Hopefully more speed will minimize the variance some and make for shorter rounds, because it's making my payments smaller even though I just increased my hashing rate.
May 21, 2011, 02:46:58 AM
I've contacted ufasoft for some assistance in getting the compatibility with his miner fixed.
In other news, we crossed 100 gH/sec a while ago, and are still seeing a steady rise. The new hardware is having no issues handling this additional load based off the reports in the IRC channel.
Many updates will be going live in the next 48 hours now that my attention is allowed to move from scaling/hardware to software updates.
In other news, we crossed 100 gH/sec a while ago, and are still seeing a steady rise. The new hardware is having no issues handling this additional load based off the reports in the IRC channel.
Many updates will be going live in the next 48 hours now that my attention is allowed to move from scaling/hardware to software updates.
May 21, 2011, 12:35:09 AM
Hmm, I'm having a different sort of problem, though. 
I can't connect using the Ufasoft bitcoin-miner 0.10 CPU miner, it stays at 0 MHash/sec.
These are the contents of the .bat I'm using to connect:
I can't spot any mistake, and it's pretty much the same I've been using to connect to other pools before.
EDIT: I found the possible cause of the issues:
I can't connect using the Ufasoft bitcoin-miner 0.10 CPU miner, it stays at 0 MHash/sec.These are the contents of the .bat I'm using to connect:
Code:
start /D "C:\Users\ChaosFox\Documents" bitcoin-miner.exe -o http://btcguild.com:8332 -u ChaosFox_xxxxxxxx -p xxxxxxxx
I can't spot any mistake, and it's pretty much the same I've been using to connect to other pools before.
EDIT: I found the possible cause of the issues:
After some work with luke-jr, I can now say that ufasoft now works with his pool (Eligius).
Typical command line
bitcoin-miner.exe -a 5 -o http://pool.bitcoin.dashjr.org:8337 -u -p
what i like about luke's pool is that you can use port 80 too (great for NATs) and you don't need to register on a website,
you just send the payment address in the user and you receive payments when they go above 1 BTC.
I saw there were posts here having problems with bitpenny pool too so i will write what solved the issue here (it might be the same problem there).
The problem used to be:
after running bitcoin-miner.exe, it would just get stuck on 0 MH/sec.
the problem was with the pool because it didn't obey this requirement:
"The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource."
This was fixed.
Typical command line
bitcoin-miner.exe -a 5 -o http://pool.bitcoin.dashjr.org:8337 -u
what i like about luke's pool is that you can use port 80 too (great for NATs) and you don't need to register on a website,
you just send the payment address in the user and you receive payments when they go above 1 BTC.
I saw there were posts here having problems with bitpenny pool too so i will write what solved the issue here (it might be the same problem there).
The problem used to be:
after running bitcoin-miner.exe, it would just get stuck on 0 MH/sec.
the problem was with the pool because it didn't obey this requirement:
"The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource."
This was fixed.
I just signed up for BTC Guild, and am also getting this 0 MHash/s issue with the ufasoft miner. I've had no problems using the ufasoft miner over at mining.bitcoin.cz. Is this a known issue?
May 21, 2011, 12:09:59 AM
Well, if pool is down or this is not in the first time...may be it`s time for the @https@?
Minor suggestion:
I`d like to see in stats # of current block...is it real to implement?
Minor suggestion:
I`d like to see in stats # of current block...is it real to implement?
May 20, 2011, 09:41:42 PM
Signed up and mining from now
May 20, 2011, 09:34:15 PM
The counter for m/hash on your website seems to be off a bit for my workers. worker1 on my PC is at anywhere from 520-590 m/hash, but on the site it shows that its between 200-590 m/hash, and consistently says its at 350 m/hash or below.
That's because your workers don't return work at a consistent rate. Look at the column that says Last Share. Some getworks take longer than others to process, so the math is constantly changing trying to calculate it. Once you've been running for a while your Total Worker Speed should be roughly correct and that's all that matters.
May 20, 2011, 05:49:21 PM
The counter for m/hash on your website seems to be off a bit for my workers. worker1 on my PC is at anywhere from 520-590 m/hash, but on the site it shows that its between 200-590 m/hash, and consistently says its at 350 m/hash or below.
May 20, 2011, 05:14:58 PM
Shameless bump to keep us on the front page 
May 20, 2011, 09:41:48 AM
New hardware is always awesome but almost always causes it's own problems.
So true
Jump to: