[9 TH] Bitparking Pool, DGM 0%,vardiff,stratum,Merge Mining

[kjlimo]

Thank you for your quick reply. I'm sticking with it, gonna find out how long it takes to find a block!

Last Block Found (UTC)   2013-05-29 08:26

Last 5 DGM payments   
Time (UTC)        Duration   
2013-05-29      08:26   
2013-05-29      08:18   
2013-05-29      01:13   
2013-05-28      21:50   
2013-05-28      19:07   

http://allchains.info/calc.html

using pool rate of 2 TerraHash

Chain   Time (hrs)
btc   7.2498

[Lucko]

Well we just gain 1 TH... Probably ASIC miner... Could be problem with there pool...

EDIT: No there pool just send out block so could be that they like altcoins...

EDIT2: Gain is now 1,5 TH. We are at 3,5TH. We got 1,5TH in 3 hours...

[TwinTurbo]

Im getting a crazy amount of rejects from many of my miners. Anyone else having this issue?

[LazyOtto]

I am, and have been all day, getting zero.

[Lucko]

No issues here... Do you by any chance have also LTC config and you have just switch back to BTC? I know that someone did scrypt mining on this pool some time back...

[TwinTurbo]

No issues here... Do you by any chance have also LTC config and you have just switch back to BTC? I know that someone did scrypt mining on this pool some time back...

No, nothing like that. I configure everything from a batch file. I am seeing a lot of "Stratum connection to pool 0 interrupted" errors, and then all shares are rejected after that until the pool connects again. The other thing I don't do is manually set my difficulty. I noticed others here are doing that, but is it necessary? My rigs range from about 800 MH/s to 1.8 GH/s.

[Lucko]

No issues here... Do you by any chance have also LTC config and you have just switch back to BTC? I know that someone did scrypt mining on this pool some time back...

No, nothing like that. I configure everything from a batch file. I am seeing a lot of "Stratum connection to pool 0 interrupted" errors, and then all shares are rejected after that until the pool connects again. The other thing I don't do is manually set my difficulty. I noticed others here are doing that, but is it necessary? My rigs range from about 800 MH/s to 1.8 GH/s.

What is the smallest(800)? And what is the total?

[matt4054]

The other thing I don't do is manually set my difficulty. I noticed others here are doing that, but is it necessary? My rigs range from about 800 MH/s to 1.8 GH/s.

You are the third one in a row, if you read the last 3 pages. This problem is caused by the fact that BitParking sets the default difficulty to 16, which is too high for GPU/FPGA mining. You should use "d=1" or "d=2" as your password to set the difficulty lower. This will avoid inactivity timeouts and stratum disconnections.

[TwinTurbo]

The other thing I don't do is manually set my difficulty. I noticed others here are doing that, but is it necessary? My rigs range from about 800 MH/s to 1.8 GH/s.

You are the third one in a row, if you read the last 3 pages. This problem is caused by the fact that BitParking sets the default difficulty to 16, which is too high for GPU/FPGA mining. You should use "d=1" or "d=2" as your password to set the difficulty lower. This will avoid inactivity timeouts and stratum disconnections.

Even though my rigs are 800 MH/s to 1.8 GH/s, my total farm is 23 GH/s. Is it still advised that I change them all to d=2, or does it make a difference if my entire farm is 23 GH/s?

Still seeing the problem, but haven't changed any difficulty settings yet. Also, running cgminer 3.1.1

[roy7]

Even though my rigs are 800 MH/s to 1.8 GH/s, my total farm is 23 GH/s. Is it still advised that I change them all to d=2, or does it make a difference if my entire farm is 23 GH/s?

Still seeing the problem, but haven't changed any difficulty settings yet. Also, running cgminer 3.1.1

It's the individual rigs that time out, regardless of how many total rigs you run. At 1-2 GH/s per rigs you should probably try d=2 and see how it does for you.

[doublec]

Still seeing the problem, but haven't changed any difficulty settings yet. Also, running cgminer 3.1.1

I ran a test mining at difficulty 32 with 14 Mhash and didn't see these disconnections. I am noticing that users reporting it are running cgminer 3.1.x. I'm running 2.11.x. I'll do some testing with the newer version. Perhaps there's some difference in how they're dealing with stratum.

[doublec]

Still seeing the problem, but haven't changed any difficulty settings yet. Also, running cgminer 3.1.1

I ran a test mining at difficulty 32 with 14 Mhash and didn't see these disconnections. I am noticing that users reporting it are running cgminer 3.1.x. I'm running 2.11.x. I'll do some testing with the newer version. Perhaps there's some difference in how they're dealing with stratum.

I can confirm that I get this with cgminer 3.1.1 but not 2.11.0. I'm attempting to find out what it's doing differently.

[Lucko]

Still seeing the problem, but haven't changed any difficulty settings yet. Also, running cgminer 3.1.1

I ran a test mining at difficulty 32 with 14 Mhash and didn't see these disconnections. I am noticing that users reporting it are running cgminer 3.1.x. I'm running 2.11.x. I'll do some testing with the newer version. Perhaps there's some difference in how they're dealing with stratum.

I can confirm that I get this with cgminer 3.1.1 but not 2.11.0. I'm attempting to find out what it's doing differently.

I had same problem on another pool. Then I just say to my self:"Don't fix it if it is not broken and go back on 2.11.4." But never figure out what was wrong... But I'm soon getting ASIC usb keys so I will be forced to go to 3.1.1. So if you can figure it out would be great.

[doublec]

I had same problem on another pool. Then I just say to my self:"Don't fix it if it is not broken and go back on 2.11.4." But never figure out what was wrong... But I'm soon getting ASIC usb keys so I will be forced to go to 3.1.1. So if you can figure it out would be great.

I can't duplicate it locally unfortunately so there will be some restarts as I add debugging to the stratum server and tweak settings.

Edit: Logging lots of debug goodness now.

[TwinTurbo]

I switched all of my machines over to d=2, and initially as I was halfway through switching them I was still seeing rejects. At some point along the way, all started working without rejects. Not sure if it was the complete change-over, or DoubleC made some fixes but either way bitparking is working great again!

And, as always, thanks again to DoubleC for a fine pool and excellent support!

[doublec]

There were a number of server restarts over the last hour as I worked to track down the cause of the stratum disconnections every 90 seconds occurring with users of cgminer 3 and above. I finally found the issue and have installed a fix. Hopefully there will be no more restarts or disconnections related to that issue.

Unfortunately I couldn't reproduce on my test environment as it turns out the issue was due to a third party library version being different on the pool server vs on my testing machine.

Feedback on whether the number of "pool interrupted" errors have increased or decreased from here on appreciated.

[doublec]

I did notice while I was debugging a number of people connecting to the stratum port with a getwork miner. If your miner has been connecting and constantly getting errors you might want to check this.

[nottm28]

There were a number of server restarts over the last hour as I worked to track down the cause of the stratum disconnections every 90 seconds occurring with users of cgminer 3 and above. I finally found the issue and have installed a fix. Hopefully there will be no more restarts or disconnections related to that issue.

Unfortunately I couldn't reproduce on my test environment as it turns out the issue was due to a third party library version being different on the pool server vs on my testing machine.

Feedback on whether the number of "pool interrupted" errors have increased or decreased from here on appreciated.

I Haven't seen this problem at all myself with 3 separate rigs all running cgminer 3.1.1 - although I do set d=1 on all three...

[Lucko]

There were a number of server restarts over the last hour as I worked to track down the cause of the stratum disconnections every 90 seconds occurring with users of cgminer 3 and above. I finally found the issue and have installed a fix. Hopefully there will be no more restarts or disconnections related to that issue.

Unfortunately I couldn't reproduce on my test environment as it turns out the issue was due to a third party library version being different on the pool server vs on my testing machine.

Feedback on whether the number of "pool interrupted" errors have increased or decreased from here on appreciated.

I Haven't seen this problem at all myself with 3 separate rigs all running cgminer 3.1.1 - although I do set d=1 on all three...

It is hi difficulty 3.x problem... Pause between shares must be 90 second or more.... d=1 is a good workaround if you have at lest 50MH... I'm now testing on one of my miners with 3.1.1. Looks good... I will look at logs from time to time and report back if I find anything...

EDIT: Last two hours only accepted shares and stratum from pool 0 detected new block... No disconnect even with 0.09 shares/minute I was running 2.11.4 by mistake. When copying .bat file from one dir to another I run that one by mistake. Disconnections are still here. But they happen after submitting the share. If you don't find anything you don't get disconnected...

EDIT2: No last share didn't disconnect me... But I did restart cgminer to change some settings.

EDIT3: Interesting. Disconnect affected my hashrate but logs of my 2.11.4 miners doesn't show any disconnects... No idea why I lost 20% so hashrate... It looks like after restart cgminer works for some time and then you start getting disconnects. Looking for a any kind of pattern...

[nottm28]

Lucko, what do you have d= set to?