Can you guys told all ports which are used currently for testing? What's the port for Stratum, var diff or GBT?
Stratum is on 3333 and 5050, GBT is on 8332 (I think). Both of them are out of testing and have variable difficulty enabled. 
Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 261. (Read 837101 times)
December 09, 2012, 02:52:57 PM
December 09, 2012, 02:50:46 PM
Can you guys told all ports which are used currently for testing? What's the port for Stratum, var diff or GBT?
December 09, 2012, 02:44:59 PM
I see in the website logs some communication errors with both Yahoo and Google spread out over a period of 1 hour. The last error was about 40 minutes ago, and both Yahoo and Google logins appear to be working now. Not sure what caused that - can't remember seeing any problems with Google or Yahoo before.
About the Stratum errors, is that something that happens rarely? Every once in a while I see errors in the log about garbled data being submitted. Is there a more detailed error message? Are you saying the miner actually crashes when this happens and you have to restart it?
About the Stratum errors, is that something that happens rarely? Every once in a while I see errors in the log about garbled data being submitted. Is there a more detailed error message? Are you saying the miner actually crashes when this happens and you have to restart it?
No details when it happens. One machine (3 gpus) cgminer crashes. Another (3 gpus) it hangs. The third (1 gpu) it recovers w/o a problem. I've never figured out why or what the differences are among the machines, aside from the obvious GPU count. It might be a driver thing, but playing with drivers is a pain and time consuming process, so I leave well enough alone.
M
December 09, 2012, 02:09:07 PM
I am sitting here in NJ USA I have the same flu! Get well!
Thanks, you get well too. It's an annoying one.
Anyone else having comm problems? Two of my miners keep crashing "pool 0 stratum submission failure".
M
M
I have been unable to log in. get transport error. when I use my open id. Since I use multiple pcs to run my video cards I happen to be logged into the site one 1 of the 9 pcs I have. all other pcs and a mac that is not a worker can't log in. It is fine for me in one sense since I can check my workers on the on pc. All 9 are running but if a work crashes I won't be able to sign it back in.
I see in the website logs some communication errors with both Yahoo and Google spread out over a period of 1 hour. The last error was about 40 minutes ago, and both Yahoo and Google logins appear to be working now. Not sure what caused that - can't remember seeing any problems with Google or Yahoo before.
About the Stratum errors, is that something that happens rarely? Every once in a while I see errors in the log about garbled data being submitted. Is there a more detailed error message? Are you saying the miner actually crashes when this happens and you have to restart it?
December 09, 2012, 12:51:30 PM
Anyone else having comm problems? Two of my miners keep crashing "pool 0 stratum submission failure".
M
M
December 08, 2012, 08:38:39 PM
Is there a way to force cgminer not to use var diff?
I prefer to mine at diff 1 as long as it possible....
I prefer to mine at diff 1 as long as it possible....
You can use the --fix-protocol option to force getwork. It may be some more days before I turn on var diff for getwork. But in general, the diff is set by the server and the miner can't override it.
I have found that during the recent pool outages that cgminer is not switching to backup pools. Bitminter is marked dead, then alive, but no work issued.
Any ideas before I raise this in the cgminer thread?
Any ideas before I raise this in the cgminer thread?
I guess this is because the pool wasn't down but horribly slow. Too slow should probably be considered down, for some definition of "too slow."
I bet that will be a lot easier to fix after about another week passes. After all the 50 BTC per block rewards have scrolled off.
Then just set it to 25 BTC.
A lot of hassle not worth the effort, IMO, to have it deal with the 'switchover' event mid graph.
Then just set it to 25 BTC.
A lot of hassle not worth the effort, IMO, to have it deal with the 'switchover' event mid graph.
For the reward graph, I would like to add some buttons in the future to move forward and back in time, though. So I would like to have the 25/50 BTC change work in the graph. I tried to fix it but it's not quite working. A bit out of it with the flu at the moment, so not at regular programming speed.
Nice, being able to alter time dimension would be useful
December 08, 2012, 04:32:48 PM
Is there a way to force cgminer not to use var diff?
I prefer to mine at diff 1 as long as it possible....
I prefer to mine at diff 1 as long as it possible....
You can use the --fix-protocol option to force getwork. It may be some more days before I turn on var diff for getwork. But in general, the diff is set by the server and the miner can't override it.
I have found that during the recent pool outages that cgminer is not switching to backup pools. Bitminter is marked dead, then alive, but no work issued.
Any ideas before I raise this in the cgminer thread?
Any ideas before I raise this in the cgminer thread?
I guess this is because the pool wasn't down but horribly slow. Too slow should probably be considered down, for some definition of "too slow."
I bet that will be a lot easier to fix after about another week passes. After all the 50 BTC per block rewards have scrolled off.
Then just set it to 25 BTC.
A lot of hassle not worth the effort, IMO, to have it deal with the 'switchover' event mid graph.
Then just set it to 25 BTC.
A lot of hassle not worth the effort, IMO, to have it deal with the 'switchover' event mid graph.
For the reward graph, I would like to add some buttons in the future to move forward and back in time, though. So I would like to have the 25/50 BTC change work in the graph. I tried to fix it but it's not quite working. A bit out of it with the flu at the moment, so not at regular programming speed.
December 08, 2012, 02:34:28 PM
I have found that during the recent pool outages that cgminer is not switching to backup pools. Bitminter is marked dead, then alive, but no work issued.
Any ideas before I raise this in the cgminer thread?
It's always been like that with cgminer and Stratum. Dunno if it's being worked on or not. Any ideas before I raise this in the cgminer thread?
December 08, 2012, 02:25:28 PM
I have found that during the recent pool outages that cgminer is not switching to backup pools. Bitminter is marked dead, then alive, but no work issued.
Any ideas before I raise this in the cgminer thread?
December 08, 2012, 08:16:58 AM
Doc,
Is there a way to force cgminer not to use var diff?
I prefer to mine at diff 1 as long as it possible....
10X
Is there a way to force cgminer not to use var diff?
I prefer to mine at diff 1 as long as it possible....
10X
December 07, 2012, 01:22:27 PM
Hey Doc, does the rewards graph need to be updated?
http://bitminter.com/stats/rewards
The one the bottom looks a little off.....
http://bitminter.com/stats/rewards
The one the bottom looks a little off.....
Yeah, that one needs fixing. It's still using 50 BTC as expected income per block.
Then just set it to 25 BTC.
A lot of hassle not worth the effort, IMO, to have it deal with the 'switchover' event mid graph.
December 07, 2012, 12:50:10 PM
Hey Doc, does the rewards graph need to be updated?
http://bitminter.com/stats/rewards
The one the bottom looks a little off.....
http://bitminter.com/stats/rewards
The one the bottom looks a little off.....
Yeah, that one needs fixing. It's still using 50 BTC as expected income per block.
December 07, 2012, 08:25:04 AM
Hey Doc, does the rewards graph need to be updated?
http://bitminter.com/stats/rewards
The one the bottom looks a little off.....
http://bitminter.com/stats/rewards
The one the bottom looks a little off.....
December 07, 2012, 04:34:22 AM
Thanks Doc,
Later....Too much pressure in the office right now
...I will see some debug info to send if available
PS: 10X DOC I was in a hurry to add backup pool in the morning so user/pass was messed out all is good now!
Later....Too much pressure in the office right now
...I will see some debug info to send if availablePS: 10X DOC I was in a hurry to add backup pool in the morning so user/pass was messed out all is good now!
December 07, 2012, 04:25:59 AM
Did you change the config? Wrong name/password maybe?
Could you give it another try then? Mining is working.
I just noticed someone is sending wrong credentials 10 times per second (standard with DiabloMiner). Remember after the user name to include an underscore and a worker name.
December 07, 2012, 04:11:18 AM
Did you change the config? Wrong name/password maybe?
December 07, 2012, 03:55:40 AM
Short question: is var diff enabled on default port, for GetWork miners?
Not yet. I'm waiting a bit with this so hashpower.com can get var diff support. We have a bunch of miners using their services and going var diff on getwork would break things as of now.
Even though cgminer 2.9.7 indeed has very minimal rejects on BitMinter, should the vardiff code still be adjusted to avoid constantly changing difficulty? Have slightly different threshold levels for increasing/decreasing the difficulty, or use a longer time period for averaging shares per minute. I'm not sure if I correctly understood the information on cgminer's thread, but it seemed to indicate that changing difficulty has the potential for some lost work because of latency.
This was an issue with the way Stratum used to work. But changes were made and adjusting difficulty is no longer a problem.
I see that my hashrate estimate has a lot more swings when mining on stratum. With higher difficulty shares, the averaging period should obviously be longer to get a meaningful estimate.
Yes, the higher difficulty makes the hashrate estimates less accurate. I'll have to look into that. Maybe a longer averaging period the higher your hashrate is.
December 07, 2012, 03:47:14 AM
Did you change the config? Wrong name/password maybe?
December 07, 2012, 03:38:58 AM
December 07, 2012, 03:28:40 AM
Pool having some issues. Working on it.
Everything up and running again. Sorry for the downtime.
namecoind crashed as usual, but something more went wrong causing very high cpu usage. I'm looking into it (logs, heap dump) to make sure it won't happen again. The high cpu usage was also the reason that the website was unstable.
Happy the pool is back up, I rather mine at Bitminter than the PPS back-up pool
Greetz
Jump to: