[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 885.

Portnoy

legendary

Activity: 2030

Merit: 1000

My money; Our Bitcoin.

Quote from: slush on September 19, 2012, 03:09:36 AM

Quote from: Portnoy on September 18, 2012, 05:27:18 PM

I live in Western Canada... is one of those better than another for my location?

I set it back to poclbm.exe [userdeatils]@api.bitcoin.cz:8332 -d0 -v -w128 -f1

The way I had it before trying Stratum, although now I am using the new version of poclbm.exe.

In new poclbm, you should see some informational message that it is switching to stratum, correct?

Yes it says something like, "diverting to stratum".

Quote

Both proxy and native support will work good, except that with native support in miner you don't need to run special software on the machine.

I see, so one doesn't need that mining_proxy.exe anymore with this new version of poclbm.

Thanks for the info.

slush

legendary

Activity: 1386

Merit: 1097

digital, please PM me with some logs if you'll see such bug again. I understand it's quite annoying, but I need some log or error message to debug&fix it.

digital

hero member

Activity: 490

Merit: 500

Quote from: slush on September 19, 2012, 03:11:16 AM

Quote from: digital on September 18, 2012, 07:29:21 PM

All of a sudden one of my workers isn't getting any shares through, the miner is working fine, but every time a share is submitted the proxy log says that it was rejected by the pool and my "worker is not authorized"

As far as I know, nothing has changed. I did just recently download the latest version of the proxy, but I'm pretty sure it had been working for several hours, and just in the last hour or so it started doing this...

Yes, this is quite interesting. I have similar bug report by another user. However I'm running latest proxy version overnight and don't see any problem. What miner are you using?

That machine was using Guiminer w/ OpenCL. Not exactly sure which version, cause I don't have the machine in front of me right now, but if I had to guess I would say it's probably the most recent version.

slush

legendary

Activity: 1386

Merit: 1097

There's some uncertainity how to connect newest poclbm to the pool using Stratum.

You don't need to change any settings in your miners, just connect them to "api.bitcoin.cz" port "8332" as usual. Pool is advertising special HTTP header which tell poclbm how to switch to Stratum automatically. You should see message about switching to Stratum in the console.

slush

legendary

Activity: 1386

Merit: 1097

Quote from: digital on September 18, 2012, 07:29:21 PM

All of a sudden one of my workers isn't getting any shares through, the miner is working fine, but every time a share is submitted the proxy log says that it was rejected by the pool and my "worker is not authorized"

As far as I know, nothing has changed. I did just recently download the latest version of the proxy, but I'm pretty sure it had been working for several hours, and just in the last hour or so it started doing this...

Yes, this is quite interesting. I have similar bug report by another user. However I'm running latest proxy version overnight and don't see any problem. What miner are you using?

slush

legendary

Activity: 1386

Merit: 1097

Quote from: Portnoy on September 18, 2012, 05:27:18 PM

I live in Western Canada... is one of those better than another for my location?

I set it back to poclbm.exe [userdeatils]@api.bitcoin.cz:8332 -d0 -v -w128 -f1

The way I had it before trying Stratum, although now I am using the new version of poclbm.exe.

In new poclbm, you should see some informational message that it is switching to stratum, correct?

Both proxy and native support will work good, except that with native support in miner you don't need to run special software on the machine.

digital

hero member

Activity: 490

Merit: 500

Well, I ended up restarting the proxy and everything is working now.

But it might be something to keep in mind because I downloaded the newest proxy around 2pm today, then everything ran great until about 7pm. Then I started getting the shares rejected with an error that said my worker was not authorized. It looked like it started with a new block.

After restarting the proxy it started working again.

I'll keep an eye on things going forward and report any other oddities...

digital

hero member

Activity: 490

Merit: 500

So...

All of a sudden one of my workers isn't getting any shares through, the miner is working fine, but every time a share is submitted the proxy log says that it was rejected by the pool and my "worker is not authorized"

As far as I know, nothing has changed. I did just recently download the latest version of the proxy, but I'm pretty sure it had been working for several hours, and just in the last hour or so it started doing this...

Any thoughts?

Portnoy

legendary

Activity: 2030

Merit: 1000

My money; Our Bitcoin.

Quote from: slush on September 18, 2012, 04:27:36 PM

Portnoy, the main reason for native support in miners is that users don't need mining proxy. So try to point latest poclbm to http://api.bitcoin.cz:8332 again, it should redirect to Stratum automatically (by following X-Stratum HTTP header in the response). Or you can put stratum://api-stratum.bitcoin.cz:3333 instead, to point miner to stratum interface directly.

I live in Western Canada... is one of those better than another for my location?

I set it back to poclbm.exe [userdeatils]@api.bitcoin.cz:8332 -d0 -v -w128 -f1

The way I had it before trying Stratum, although now I am using the new version of poclbm.exe.

slush

legendary

Activity: 1386

Merit: 1097

Portnoy, the main reason for native support in miners is that users don't need mining proxy. So try to point latest poclbm to http://api.bitcoin.cz:8332 again, it should redirect to Stratum automatically (by following X-Stratum HTTP header in the response). Or you can put stratum://api-stratum.bitcoin.cz:3333 instead, to point miner to stratum interface directly.

Portnoy

legendary

Activity: 2030

Merit: 1000

My money; Our Bitcoin.

Quote from: slush on September 18, 2012, 02:18:03 PM

Portnoy: Can you confirm that it is connecting to port 3333 instead of 8332? If so, then poclbm is mining on Stratum interface and thus giving you all benefits included in this protocol.

Sure. How do I do that?

This is what I have in my batch file:
poclbm.exe [userdetails]@localhost:8332 -d0 -v -w128 -f1

Should I change that 8332 above to 3333?

slush

legendary

Activity: 1386

Merit: 1097

Portnoy: Can you confirm that it is connecting to port 3333 instead of 8332? If so, then poclbm is mining on Stratum interface and thus giving you all benefits included in this protocol.

Portnoy

legendary

Activity: 2030

Merit: 1000

My money; Our Bitcoin.

Quote from: slush on September 18, 2012, 11:29:11 AM

m0mchil just released new version of poclbm with native support of Stratum. Can anybody check it and confirm that it works as expected? I don't have a reason to think an oposite, I just don't have GPU here around to check it myself.

Working fine for me. Although I don't see anything different. The last version worked fine for me with Stratum.

slush

legendary

Activity: 1386

Merit: 1097

m0mchil just released new version of poclbm with native support of Stratum. Can anybody check it and confirm that it works as expected? I don't have a reason to think an oposite, I just don't have GPU here around to check it myself.

pekv2

hero member

Activity: 770

Merit: 502

Quote from: slush on September 17, 2012, 01:15:18 PM

Hm, actually not. Mysql log didn't tell me anything significant, but it clearly failed during the insert to block table.

Quote from: digital on September 17, 2012, 10:31:46 AM

Quote from: slush on September 17, 2012, 10:23:57 AM

I just "fixed" the lost blocks 917,923,926 by doubling rewards for rounds #13919, #13920, #13921. I'm sorry for inconvenience.

Thanks Slush!

Just out of curiosity, did you figure out what cause the bug in the first place?

Oh nice. Can this happen more often please :p . Thanks for the double up.

slush

legendary

Activity: 1386

Merit: 1097

Hm, actually not. Mysql log didn't tell me anything significant, but it clearly failed during the insert to block table.

Quote from: digital on September 17, 2012, 10:31:46 AM

Quote from: slush on September 17, 2012, 10:23:57 AM

I just "fixed" the lost blocks 917,923,926 by doubling rewards for rounds #13919, #13920, #13921. I'm sorry for inconvenience.

Thanks Slush!

Just out of curiosity, did you figure out what cause the bug in the first place?

digital

hero member

Activity: 490

Merit: 500

Quote from: slush on September 17, 2012, 10:23:57 AM

I just "fixed" the lost blocks 917,923,926 by doubling rewards for rounds #13919, #13920, #13921. I'm sorry for inconvenience.

Thanks Slush!

Just out of curiosity, did you figure out what cause the bug in the first place?

slush

legendary

Activity: 1386

Merit: 1097

I just "fixed" the lost blocks 917,923,926 by doubling rewards for rounds #13919, #13920, #13921. I'm sorry for inconvenience.

VeeMiner

hero member

Activity: 752

Merit: 500

bitcoin hodler

Quote from: pekv2 on September 16, 2012, 09:24:22 AM

Wow, Stratum climbed from 80 or so if I recall correctly to 124.506 Ghash/s over night.

that might be because Slush presented it at the bitcoin conference in London

ilich

newbie

Activity: 59

Merit: 0

Quote from: digital on September 16, 2012, 06:33:45 PM

I got a reward on both btc, and nmc for that block. Might want to check your hardware or network connection...

Network up, hardware fine... not sure why. Will take a closer look.

edit: will wait up more. didn't notice the next block is 2 mins old. n00b moment. all good, at first it was "none", after refreshing page it's all good... yeah, n00b moment Tongue

thx for replies though.

Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 885. (Read 4382653 times)