Quote from: blockhilltop on Today at 02:31:00 AM

Quote from: -ck on November 25, 2024, 11:06:43 AM

Quote from: -ck on November 25, 2024, 10:03:26 AM

The hardware passed checks and fortunately I believe I've found the issue and it's related to the toolchain [snip]

Most users should have migrated by now. Some with persistent DNS caches that ignore the short time to live setting of solo.ckpool.org may take a while to switch over. [snip]

Thanks again for the update and communications CK.

FYI my software is showing a 10 to 12% increase in total number of shares accepted hourly since 11AM EST (when you posted your notice regarding successful upgrade/migration). And has been doing so consistently for 10+ hours since, no rejected shares or errors. I'm certainly happy to see the bump in total shares, but not sure if it's real or some reporting error (looking at my Foreman software's hourly history).

Noticed the homepage has been updated too, it looks better and is easier on my eyes. Also noticed the two alt subdomains, but when I try and ping solo6 I get an error stating not known, assuming that's a DNS caching issue and will try again tomorrow, the solo4 subdomain does work however (meaning can be accessed via ping).

Lastly on the homepage the link on the bottom doesn't take you to this sub-forum (sub-group?) directly, rather it links to the bitcointalk.org homepage - not sure if this is on accident which is why I mention it.

Good luck ladies and gentlemen! Let's get another Block soon!!

All cool, I still have people on the old pool a day and a half later - some DNS caches just forever, even though the time to live is set to 5 minutes so maybe that's what you're experiencing with solo6. The other addresses were always available, they've just been pointed to the new pool, but perhaps they were hard to read on the old page. Higher hashrate is almost certainly just an unusually lucky streak as there's no valid reason the pool would give a higher hashrate, though lasting 10 hours is odd. The link I"ll update.

Anyone still on the old pool address - either because of DNS caching or because they're mining directly to the IP instead - their shares are being forwarded to the new pool.

Hash and onwards to our next block!