[∞ YH] US/EU/AU solo.ckpool.org 2% fee solo mining 313 blocks solved!

[-ck]

The new hardware is in its testing phase now and I'd appreciate it if some people could direct their hashrate to it, but make sure to have a backup pool specified in case of instability. Use the pool details of newsolo.ckpool.org:3333 . Once it's proven stable for an extended period I'll migrate the solo.ckpool.org domain to the new hardware.

[Nexus9090]

The new hardware is in its testing phase now and I'd appreciate it if some people could direct their hashrate to it, but make sure to have a backup pool specified in case of instability. Use the pool details of newsolo.ckpool.org:3333 . Once it's proven stable for an extended period I'll migrate the solo.ckpool.org domain to the new hardware.

Thanks for the updates.

OK moving my kit onto the new server, will advise if I see any issues.

Cheers

G.

-Update

All connected OK, appears to be hashing and submitting shares. Shares being accepted at the normal rates I've been seeing previously.
Will keep monitoring throughout the day.

-Update #2

All running OK, no signs of any issues at all.

Interestingly there have been zero rejected shares in the time its been running, normally I see a handful even over a short duration.

Average hash rate is marginally higher also. Of the two rigs I have attached:-
#1 averaged 470GH/s on solo and is now averaging 482GH/s on newsolo
#2 averaged 715GH/s on solo and is now averaging 722GH/s on newsolo

[blockhilltop]

The new hardware is in its testing phase now and I'd appreciate it if some people could direct their hashrate to it, but make sure to have a backup pool specified in case of instability. Use the pool details of newsolo.ckpool.org:3333 . Once it's proven stable for an extended period I'll migrate the solo.ckpool.org domain to the new hardware.

Thanks for the upgrades and updates CK! As always much appreciation and many thanks for this public service to the community.

About 2.5 hours ago I tested and moved over 1x S19 Pro 100T running in Low Power mode.

Originally it was hashing and reading (ie showing up online) at about 77-79T on the original (solo.ckpool.org) server and running relatively error free.

Now, on the new server, it's reading (ie showing up online, at newsolo.ckpool.org/user/ADDRESS) as slightly higher hashrate - about 80-81T (vs 77-79 before). And currently has submitted over 2,500 shares successfully with only 1 share rejected.

My other workers all appeared at the new address, shown in the same order as on the current live server, only they show up as essentially inactive workers (and these inactive worker's respective shares seem old/off though).

I will update this if any anomalies, errors or rejected shares, etc..

EDIT: I now see the shares for the worker I moved over are also old data, and much less than the number of shares I had accumulated on the original server. No big deal at all, and I'm assuming you're aware of this CK, just wanted to point it out just in case and for the rest of us.

Lastly, I'm assuming given we're testing it right now, in the 1 in 20+ yrs chance that my rig hits a Block at this "newsolo" server that this server is live and thus I would be rewarded the Block, correct? (to the Debbie Downers out there, I know hitting right now is a low likelihood scenario - just want to verify this new server is live on the blockchain).

Good luck everyone, let's get another Block soon! LFG!!!

[-ck]

Thanks for testing, yes the newpool is hashing live and if a block was found the reward would be distributed as normal. There'll  be a brief outage as I will be migrating the stats from the old pool across and gradually migrating miners today. If any issue occurs I will switch them back to the old hardware.

[-ck]

Thanks for testing, yes the newpool is hashing live and if a block was found the reward would be distributed as normal. There'll  be a brief outage as I will be migrating the stats from the old pool across and gradually migrating miners today. If any issue occurs I will switch them back to the old hardware.

Cancel that, the hardware is misbehaving, I will be taking it down for memory testing.

[Nexus9090]

Thanks for testing, yes the newpool is hashing live and if a block was found the reward would be distributed as normal. There'll  be a brief outage as I will be migrating the stats from the old pool across and gradually migrating miners today. If any issue occurs I will switch them back to the old hardware.

Cancel that, the hardware is misbehaving, I will be taking it down for memory testing.

OK thanks, no visible problems here.

Will roll back to using solo.ckpool.org:3333 until further notice.

Good luck fixing the HW problem.

[vincku]

I got both pool alive. I had 2 pools set: ckpool and solo ckpool.
A few minutes ago, I realised that ckpool was dead and my ant automatically had automatically switched to the solockpool.
The newsolo ckpool seems to be alive at 25.11.2024 00:06 my Ant began to mine on it. But a few minutes later, it switched back again to solo ckpool.

25.11 At 00:06
0 stratum+tcp://newsolo.ckpool.org:3333 Alive
1 stratum+tcp://solo.ckpool.org:3333 Alive

25.11 at 00:13
0 stratum+tcp://newsolo.ckpool.org:3333 Dead
1 stratum+tcp://solo.ckpool.org:3333 Alive

If it helps... 

[-ck]

I got both pool alive. I had 2 pools set: ckpool and solo ckpool.
A few minutes ago, I realised that ckpool was dead and my ant automatically had automatically switched to the solockpool.
The newsolo ckpool seems to be alive at 25.11.2024 00:06 my Ant began to mine on it. But a few minutes later, it switched back again to solo ckpool.

25.11 At 00:06
0 stratum+tcp://newsolo.ckpool.org:3333 Alive
1 stratum+tcp://solo.ckpool.org:3333 Alive

25.11 at 00:13
0 stratum+tcp://newsolo.ckpool.org:3333 Dead
1 stratum+tcp://solo.ckpool.org:3333 Alive

If it helps... 

Thanks, I'm trying to keep newsolo up as much as possible while I debug this issue, but there will be brief downtimes on it so this is not surprising.

[-ck]

The hardware passed checks and fortunately I believe I've found the issue and it's related to the toolchain in the updated operating system in the new dedicated server. I will be slowly migrating users to the new server now. If there's an issue I'll put everyone back on the old one immediately. Downtime should be negligible.

[-ck]

The hardware passed checks and fortunately I believe I've found the issue and it's related to the toolchain in the updated operating system in the new dedicated server. I will be slowly migrating users to the new server now. If there's an issue I'll put everyone back on the old one immediately. Downtime should be negligible.

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. Any lingering hashrate on the old pool can still solve a block so no hashes are being wasted.

The long story is the instability was caused by a stack overflow in the ckpool code with very long segwit addresses that never manifested on older toolchains due to the more lax amount of stack ram was being allocated. A fix has been committed to the ckpool git.

[Aleksey183-2411]

hi! should I connect the mining rentals to the newsolo.ckpool.org:3333 ? or to another one?

[-ck]

hi! should I connect the mining rentals to the newsolo.ckpool.org:3333 ? or to another one?

Same settings as always. newsolo was just a test domain. Most rentals should go to solo.ckpool.org:4334

[Nexus9090]

New pool seems to be running OK. Not seen any issues thismorning.

I did notice the disconnect for a few minutes I guess that was when things changed over.



On the topic of the stats page, is there any way to remove dormant workers from the workers list?

I had a rental a few weeks ago and it still shows up in the list even though its no longer active for nearly a month (27days).

Clicking on the worker name returns a server error page.

Code:

Application error: a server-side exception has occurred (see the server logs for more information).

Digest: 3247891116

[blockhilltop]

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!!

[-ck]

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 last 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.

Keep hashing, and onwards to our next block!

[buzzard34]

All cool, I still have people on the old pool a day and a half later - some DNS caches just last 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.

Keep hashing, and onwards to our next block!

Is it just me, or are the ping times much worse now?

I've gone from 10ms to 100ms-ish.

[-ck]

All cool, I still have people on the old pool a day and a half later - some DNS caches just last 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.

Keep hashing, and onwards to our next block!

Is it just me, or are the ping times much worse now?

I've gone from 10ms to 100ms-ish.

It's on the other side of the country as I said during the announcement.

[-ck]

The old solo pool bare metal hardware has been refashioned into the stats server solostats.ckpool.org to be better able to cope with the many users accessing it now compared to the VPS that was being used for stats. The transition should happen seamlessly without any user intervention. DNS caching may have you on the old site for a while longer but you shouldn't notice when it switches.

[-ck]

The old solo pool bare metal hardware has been refashioned into the stats server solostats.ckpool.org to be better able to cope with the many users accessing it now compared to the VPS that was being used for stats. The transition should happen seamlessly without any user intervention. DNS caching may have you on the old site for a while longer but you shouldn't notice when it switches.

Migration of https://solostats.ckpool.org is now complete. If you added your username between beginning of migration and now you may have to re-add your username for it to be picked up again, and DNS caching may have you on the old site for a while longer. Users need not do anything.

The old stats site was running prisma which appeared to be very memory intensive, and @MrV_777 has been generous enough to rewrite it using typeorm. Props for all their efforts.

You may also notice that stats are now updating one minutely instead of five. This is partly due to the lower memory usage of typeorm but also because of the significantly more resources of the server the stats have migrated to.

[willi9974]

Just a hing

On the solostat Page if you sort the worker under a address by maybe hashrate 5min, than the table is sorting by numberts yes, but not by hashrate

willi9974_3   605 GH/s   625 GH/s   612 GH/s   80.32 M   3.81 B   1 min ago
satcat21_2   604 GH/s   627 GH/s   571 GH/s   39.12 M   3.68 B   1 min ago
willi9974_4   593 GH/s   545 GH/s   522 GH/s   1.53 B   2.53 B   1 min ago
lutz_k_MRR   5,79 TH/s   5,47 TH/s   2,14 TH/s   73.77 M   3.65 T   1 min ago
ninety4_2   579 GH/s   512 GH/s   488 GH/s   18.28 M   24.20 B   1 min ago
Komakaschper_2   573 GH/s   496 GH/s   43,8 GH/s   626.97 K   21.73 B   1 min ago
yoshovon_2   551 GH/s   284 GH/s   314 GH/s   37.04 M   1.72 B   1 min ago
go-btc_m30s+_3   549 KH/s   7,13 TH/s   2,97 TH/s   958.91 M   2.50 B   1 hour 55 mins ago
yoshovon_1   538 GH/s   286 GH/s   314 GH/s   490.11 M   1.12 B   1 min ago
kekeck33_1   531 GH/s   478 GH/s   451 GH/s   82.00 M   3.30 B   1 min ago