[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[mylesrom]

I switched to de pool and it will run, but the regular pool is dead for me.

[1715080011]

1715080011

[1715080011]

1715080011

[1715080011]

1715080011

[1715080011]

1715080011

[1715080011]

1715080011

[zOU]

I switched to de pool and it will run, but the regular pool is dead for me.

i switched to DE pool too

[-ck]

Looks like a problem with the redirector. Anyone that was mining would not have been kicked off but anyone establishing a new connection would have been unable to connect. You should be able to connect now with the redirector temporarily bypassed via DNS until I get it working again. There are still some minor lingering issues with the upgrade too so I may need to restart them all again later today. Apologies for any inconvenience.

Found and fixed the redirector problem and have updated the pools yet again. Thanks for your patience. Block on.

[-ck]

Dear users "cobramining", "whirledps1" and "koh0907", you cannot use a regular username on this pool; you must use a valid bitcoin address as your username. Additionally user trying to log in with 1EF7qiyc5Beog1x1sZKitiYKhp31zKYq8w your bitcoin address is invalid.

[Rabinovitch]

Why does my user's statistics differ from my worker's statistics?

I'm mining as 1EMjekyXEjJuFCHuiq3Sku6KZpDNS4AEXd.X6 for several days already, so I thought that both stats should be the same.

[-ck]

Why does my user's statistics differ from my worker's statistics?

I'm mining as 1EMjekyXEjJuFCHuiq3Sku6KZpDNS4AEXd.X6 for several days already, so I thought that both stats should be the same.

After a restart any workers or users that have not been mining since the restart won't have any updates on their stats; the lastupdate field is there to help people notice that. Alternatively if you're mining on the de pool there is a possibility that stats are not being propagated properly to the main pool since that was massively modified in the software update. What exactly is wrong?

[Rabinovitch]

I just would like to know if everything is OK. It's OK if everything is OK. 

[-ck]

I just would like to know if everything is OK. It's OK if everything is OK. 

Everything's hunky dory.

[powrslave]

getting Stratum connection to pool 0 interrupted still

[-ck]

getting Stratum connection to pool 0 interrupted still

Then you have some kind of network problem. The pool is working perfectly fine for 2.8PH of miners at the moment. Only thing I can see is people trying to connect repeatedly with invalid usernames which is a user problem.

[powrslave]

Strange.
I cannot connect to de either. Also changed port from 3334 to 3333.
This started today.

When I connect to antpool everything is working.

[-ck]

Strange.
I cannot connect to de either. Also changed port from 3334 to 3333.
This started today.

When I connect to antpool everything is working.

Check your username is a valid bitcoin address and doesn't contain a space or something, or try another address.

[DanielRo]

Why does my user's statistics differ from my worker's statistics?

I'm mining as 1EMjekyXEjJuFCHuiq3Sku6KZpDNS4AEXd.X6 for several days already, so I thought that both stats should be the same.

After a restart any workers or users that have not been mining since the restart won't have any updates on their stats; the lastupdate field is there to help people notice that. Alternatively if you're mining on the de pool there is a possibility that stats are not being propagated properly to the main pool since that was massively modified in the software update. What exactly is wrong?

{"hashrate1m": "1.18T", "hashrate5m": "1.09T", "hashrate1hr": "354G", "hashrate1d": "17.7G", "hashrate7d": "2.55G", "lastupdate": 1483517948, "workers": 1, "shares": 359650, "bestshare": 94424.865578987708, "bestever": 94424, "worker": [{"hashrate1m": "1.18T", "hashrate5m": "1.1T", "hashrate1hr": "1.12T", "hashrate1d": "1.16T", "hashrate7d": "1.08T", "lastupdate": 1483517948, "shares": 456909001, "bestshare": 1828075158.9156022, "bestever": 1828075158, "workername": "1DXz8U4jggxD5c8xCBP3i5wm12AHHkqxTa"}]}

The worker stats are right. The main stats are not. It shows "hashrate1hr": "354G" on the main stats and "hashrate1hr": "1.12T" on the worker stats.
This are my stats. I'm using the DE pool.

[-ck]

{"hashrate1m": "1.18T", "hashrate5m": "1.09T", "hashrate1hr": "354G", "hashrate1d": "17.7G", "hashrate7d": "2.55G", "lastupdate": 1483517948, "workers": 1, "shares": 359650, "bestshare": 94424.865578987708, "bestever": 94424, "worker": [{"hashrate1m": "1.18T", "hashrate5m": "1.1T", "hashrate1hr": "1.12T", "hashrate1d": "1.16T", "hashrate7d": "1.08T", "lastupdate": 1483517948, "shares": 456909001, "bestshare": 1828075158.9156022, "bestever": 1828075158, "workername": "1DXz8U4jggxD5c8xCBP3i5wm12AHHkqxTa"}]}

The worker stats are right. The main stats are not. It shows "hashrate1hr": "354G" on the main stats and "hashrate1hr": "1.12T" on the worker stats.
This are my stats. I'm using the DE pool.

Thanks. Will investigate when time permits. There were huge updates pending first (check the ckpool git to see all the changes); unfortunately those changes seem to have affected these stats. No mining is lost though, the stats are probably not being propagated fully to the main pool.

[-ck]

And now for something completely different, I'll be bouncing the pools yet again for more improvements. Sorry about any inconvenience.

All complete, everyone seems to have reconnected without a hitch and more!

One more minor adjustment and bounce, sorry folks.

EDIT: Done. The restarts at least have been virtually seamless today.

[tubexc]

 How to see solo ck pool current hashrate ?

[ComputerGenie]

How to see solo ck pool current hashrate ?

http://solo.ckpool.org/pool/

[-ck]

Updating both bitcoinds to 0.13.2 based versions shortly.

Completed.

Note that there are still 4 users who have been trying to log in repeatedly with invalid usernames. I have since blocked your IP addresses so if you cannot connect at all you may be one of them.
For those with low hashrate hardware that are having trouble staying on the pool now, it is probably related to the increase in starting diff to 4000, so you can work around this by adding --suggest-diff and a suitable diff to your mining device. Note that there is hardly any reason to use suggest diff otherwise on this pool.

[tubexc]

 How to see when it was the last pool block ?

[-ck]

How to see when it was the last pool block ?

https://www.blocktrail.com/BTC/pool/solockpool