Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 9. (Read 108468 times)
November 28, 2024, 10:18:15 AM
Does CKPool have a Discord? I spend more time there than here. Thanks!
November 28, 2024, 09:49:11 AM
Thanks to a generous donation of hardware I have now set up an EU instance of solo ckpool. This offsets the extra latency of moving the main pool to the west coast of the USA. Miners in Europe and Africa should now use eusolo.ckpool.org with stats at eusolostats.ckpool.org . Miners in The Americas and Asia-Pacific region should keep using the main pool, though miners in either region can use the sister pool as a backup if desired.
As coordination and communication of shares between the two pool instances would add unnecessary overhead, they will run as two completely separate pools, and only aid each other in propagating blocks.
As coordination and communication of shares between the two pool instances would add unnecessary overhead, they will run as two completely separate pools, and only aid each other in propagating blocks.
Thanks -CK for all the background work you're doing keeping the pools alive and improved.
Ping in the UK to eusolo.ckpool.org is quite variable at present anywhere between 20-160mS averaging out to around 28mS some pings are quite high, no obvious reason for it though.
Eg...
Code:
64 bytes from 2a01:4f8:2191:2762::2 (2a01:4f8:2191:2762::2): icmp_seq=238 ttl=54 time=28.8 ms
64 bytes from 2a01:4f8:2191:2762::2 (2a01:4f8:2191:2762::2): icmp_seq=239 ttl=54 time=153 ms
64 bytes from 2a01:4f8:2191:2762::2 (2a01:4f8:2191:2762::2): icmp_seq=240 ttl=54 time=27.5 ms
64 bytes from 2a01:4f8:2191:2762::2 (2a01:4f8:2191:2762::2): icmp_seq=241 ttl=54 time=26.8 ms
At present I can't access any of the stats pages, but I guess thats just DNS propagation being slow.
I'm going to leave my rigs on solo.ckpool.org until I get home tonight and then I'll move them over to the new local EU server.
Thanks again for the work you're doing. It must be quite an effort, I hope it all remains stable.
Cheers
G.
November 28, 2024, 08:49:13 AM
Thanks to a generous donation of hardware I have now set up an EU instance of solo ckpool. This offsets the extra latency of moving the main pool to the west coast of the USA. Miners in Europe and Africa should now use eusolo.ckpool.org with stats at eusolostats.ckpool.org . Miners in The Americas and Asia-Pacific region should keep using the main pool, though miners in either region can use the sister pool as a backup if desired.
As coordination and communication of shares between the two pool instances would add unnecessary overhead, they will run as two completely separate pools, and only aid each other in propagating blocks.
Cool, thanks for that.As coordination and communication of shares between the two pool instances would add unnecessary overhead, they will run as two completely separate pools, and only aid each other in propagating blocks.
But one question. If I have 200 Miner and 100 mine on the USA and the other 100 miner are on the EU Server. Will be the Statistik merged and see all 200 miner in one Statistik Like that https://solo.ckpool.org/users/bc1qeuupt2tgerfum8jclt8aklu9cdmzzkwml9lg7c
Best regards and happy Mining
Willi
November 28, 2024, 07:28:55 AM
hi! can I switch to eusolo? will there be no changes? Ping is great!
November 28, 2024, 06:20:07 AM
Thanks to a generous donation of hardware I have now set up an EU instance of solo ckpool. This offsets the extra latency of moving the main pool to the west coast of the USA. Miners in Europe and Africa should now use eusolo.ckpool.org with stats at eusolostats.ckpool.org . Miners in The Americas and Asia-Pacific region should keep using the main pool, though miners in either region can use the sister pool as a backup if desired.
As coordination and communication of shares between the two pool instances would add unnecessary overhead, they will run as two completely separate pools, and only aid each other in propagating blocks.
As coordination and communication of shares between the two pool instances would add unnecessary overhead, they will run as two completely separate pools, and only aid each other in propagating blocks.
November 27, 2024, 01:14:09 PM
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
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
Good catch. I'll push a fix for that. The refactor caused more changes then I expected so some of these odd small bugs popped up.
Thanks!
November 27, 2024, 12:57:48 PM
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
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
November 27, 2024, 02:38:41 AM
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.
November 26, 2024, 10:05:46 PM
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.
November 26, 2024, 05:00:16 PM
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.
November 26, 2024, 04:49:59 PM
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.
November 25, 2024, 09:57:10 PM
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]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!!
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!
November 25, 2024, 09:31:00 PM
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]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!!
November 25, 2024, 08:58:02 AM
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.
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
Digest: 3247891116
November 25, 2024, 06:57:14 AM
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 November 25, 2024, 06:49:01 AM
hi! should I connect the mining rentals to the newsolo.ckpool.org:3333 ? or to another one?
November 25, 2024, 06:06:43 AM
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.
November 25, 2024, 05:03:26 AM
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.
November 24, 2024, 06:18:34 PM
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...
November 24, 2024, 06:13:47 PM
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...
Jump to: