Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 157. (Read 379078 times)
May 09, 2011, 11:34:44 PM
And thanks to Sukrim for the second low priority miner tip! It failed over to deepbit PPS beautifully.
May 09, 2011, 11:31:30 PM
Last "failed to connect" was at 21:22:04 PST. Appears to be resolved.
That was the same time my miner started working again too.
May 09, 2011, 11:26:27 PM
Last "failed to connect" was at 21:22:04 PST. Appears to be resolved.
May 09, 2011, 11:26:17 PM
It seems to be working again.
And I haven't received any message so I guess it wasn't mine that caused the problem.
And I haven't received any message so I guess it wasn't mine that caused the problem.
May 09, 2011, 11:24:49 PM
Are the errors occuring RIGHT NOW (as of about the last 30 seconds)? My miners have resumed working since the block was put in place on the bad worker.
May 09, 2011, 11:23:41 PM
I'm also having issues.
alot of "failed to connect .. retrying." and rejected results.
using latest phoenix.
alot of "failed to connect .. retrying." and rejected results.
using latest phoenix.
May 09, 2011, 11:22:52 PM
I sent a message to the owner of the worker, trying to find out what miner they're using and if there's anything strange in the settings.
May 09, 2011, 11:21:27 PM
I hope it is not mine. I now get a lot of:
Code:
09/05/2011 22:19:33, long poll exception:
Traceback (most recent call last):
File "BitcoinMiner.pyo", line 259, in longPollThread
File "BitcoinMiner.pyo", line 221, in request
File "httplib.pyo", line 898, in request
File "httplib.pyo", line 935, in _send_request
File "httplib.pyo", line 892, in endheaders
File "httplib.pyo", line 764, in _send_output
File "httplib.pyo", line 723, in send
File "httplib.pyo", line 704, in connect
File "socket.pyo", line 514, in create_connection
error: [Errno 10061] No connection could be made because the target machine actively refused it
Traceback (most recent call last):
File "BitcoinMiner.pyo", line 259, in longPollThread
File "BitcoinMiner.pyo", line 221, in request
File "httplib.pyo", line 898, in request
File "httplib.pyo", line 935, in _send_request
File "httplib.pyo", line 892, in endheaders
File "httplib.pyo", line 764, in _send_output
File "httplib.pyo", line 723, in send
File "httplib.pyo", line 704, in connect
File "socket.pyo", line 514, in create_connection
error: [Errno 10061] No connection could be made because the target machine actively refused it
May 09, 2011, 11:13:58 PM
One particular worker has been causing the crashes. I've blocked them from the pool temporarily while I try to figure out what makes them so special.
May 09, 2011, 10:58:38 PM
Switching over now for a day to test out. Couldn't have happened at a better time since almost all the other major pools right now have been having some wonky issues too.
May 09, 2011, 10:46:34 PM
Thank you all for the continued support. As Sukrim stated, it is a great idea to have a second miner running low priority on another pool in case BTC Guild crashes in this early period.
May 09, 2011, 10:40:54 PM
Of course, the pool went down just minutes after I had to step away to do something else and came back just as I returned. 
But I guess that is to be expected with a new pool.
Keep up the great work!
But I guess that is to be expected with a new pool.
Keep up the great work!
May 09, 2011, 10:39:15 PM
Standing by. Of course, you feel no pressure..
Getting a huge flood right now, adding debug log printouts into the code to find out exactly where the crash is coming from. It's a memory leak issue, looks like it's related to that hashing I mentioned previously. Also checking network logs to see if this flood is legit or not (although it looks like something slush mentioned with his pool over the weekend).
UPDATE: Found out which worker is triggering the crash, now trying to figure out why.
UPDATE 2: Back up and not crashing at the moment. Gotta package some items that sold today for shipment, we'll see if it's stable or not soon. Sorry for the inconvenience, but some bugs just can't be found until you open up for the whole world to play with.
Hey eleuthria keep up the great work. I think it's going to be an awesome pool when all the bugs are worked out. I hope it wasn't one of my miners that caused the crash...
May 09, 2011, 10:34:15 PM
Of course .... it's back up now.... Oh well..
May 09, 2011, 10:32:06 PM
I'll take this opportunity to update my miners. No worries.
May 09, 2011, 10:20:17 PM
Standing by. Of course, you feel no pressure..
Getting a huge flood right now, adding debug log printouts into the code to find out exactly where the crash is coming from. It's a memory leak issue, looks like it's related to that hashing I mentioned previously. Also checking network logs to see if this flood is legit or not (although it looks like something slush mentioned with his pool over the weekend).
UPDATE: Found out which worker is triggering the crash, now trying to figure out why.
UPDATE 2: Back up and not crashing at the moment. Gotta package some items that sold today for shipment, we'll see if it's stable or not soon. Sorry for the inconvenience, but some bugs just can't be found until you open up for the whole world to play with.
May 09, 2011, 10:18:55 PM
Hehe, that's why you set up a second miner on low priority in another pool/solo! 
Thanks for the fast response(s), much appreciated!
Thanks for the fast response(s), much appreciated!
May 09, 2011, 10:12:39 PM
Standing by. Of course, you feel no pressure..
May 09, 2011, 10:08:38 PM
Jeez, right after I switched over. Guess it couldn't handle me 
May 09, 2011, 10:06:38 PM
Miners are idle. Issues?
Pool is crashing instantly upon restarting right now, trying to figure out the cause.
Jump to: