Author

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 225. (Read 1514767 times)

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hmm that reminds me I've had this problem before. If you authed first on the DE pool you cannot auth on the main pool later on. I thought I'd fixed this bug but it seems to have returned. That would explain it. I'll look into it.
Is this related to a bug I posted about a couple weeks ago?  Well, I guess I don't know if it's a bug or a flaw in the way the miner operates, but just wondering.

The IP address of solo.ckpool.org changes after a DDoS and perhaps these devices almost never look up the IP address using a cached result for ages. In which case a restart might be required, either of cgminer or the whole device.
I have restarted the whole device 3 times (one of those was power off for 20+ minutes) and it still is in failover, I'll see if I can't flush its dns cache or something, thanks.
I had the same bug a couple of weeks back, all I had to do was change the address I was mining to.
I could not locate any sort of dns reset in the S3 interface so I tried changing addresses and the pool was ALIVE again.  I changed back to the old address thinking maybe I had cleared up the issue, but the old address reports the pool as DEAD.  A new solo address for the US node it is then!  Problem solved, thanks.
Yep, probably the same pool bug.
legendary
Activity: 1274
Merit: 1000
Hmm that reminds me I've had this problem before. If you authed first on the DE pool you cannot auth on the main pool later on. I thought I'd fixed this bug but it seems to have returned. That would explain it. I'll look into it.
Is this related to a bug I posted about a couple weeks ago?  Well, I guess I don't know if it's a bug or a flaw in the way the miner operates, but just wondering.

The IP address of solo.ckpool.org changes after a DDoS and perhaps these devices almost never look up the IP address using a cached result for ages. In which case a restart might be required, either of cgminer or the whole device.
I have restarted the whole device 3 times (one of those was power off for 20+ minutes) and it still is in failover, I'll see if I can't flush its dns cache or something, thanks.
I had the same bug a couple of weeks back, all I had to do was change the address I was mining to.
I could not locate any sort of dns reset in the S3 interface so I tried changing addresses and the pool was ALIVE again.  I changed back to the old address thinking maybe I had cleared up the issue, but the old address reports the pool as DEAD.  A new solo address for the US node it is then!  Problem solved, thanks.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
re: pool problems... it says "Failed authorization Sad" but I literally haven't changed a thing. Still [address].[worker] yes? I get same result on 3334 and 3333
Sure you haven't added a space or something in your username in your miner's config during copy/paste? Also once you fail to authorise you get throttled for attempted auths for the next 10 minutes (this has always been the case though).

yeah 100% sure all i did was turn off my miners for like a day. oh and i had them pointed to kano.is for a while as well.
That is most unusual indeed. Last time this happened to someone on this forum they restarted their machine and re-entered their credentials and everything worked after that. Perhaps in failover you never noticed it had never mined on solo and was always running on a backup?

i'll reboot tomorrow sometime. happily mining on DE server right now.

I have had same problem for a while, not being able to authenticate on the main server, but DE server is authenticating and working fine..

Have not reported it before since DE server is closer to me and did not want to bother thinking it was just me, but I can confirm I have copy pasted same address.worker name and can mine on DE but main SOLO is rejecting my authentication even if I put it as a backup..
Hmm that reminds me I've had this problem before. If you authed first on the DE pool you cannot auth on the main pool later on. I thought I'd fixed this bug but it seems to have returned. That would explain it. I'll look into it.
newbie
Activity: 41
Merit: 0
re: pool problems... it says "Failed authorization Sad" but I literally haven't changed a thing. Still [address].[worker] yes? I get same result on 3334 and 3333
Sure you haven't added a space or something in your username in your miner's config during copy/paste? Also once you fail to authorise you get throttled for attempted auths for the next 10 minutes (this has always been the case though).

yeah 100% sure all i did was turn off my miners for like a day. oh and i had them pointed to kano.is for a while as well.
That is most unusual indeed. Last time this happened to someone on this forum they restarted their machine and re-entered their credentials and everything worked after that. Perhaps in failover you never noticed it had never mined on solo and was always running on a backup?

i'll reboot tomorrow sometime. happily mining on DE server right now.

I have had same problem for a while, not being able to authenticate on the main server, but DE server is authenticating and working fine..

Have not reported it before since DE server is closer to me and did not want to bother thinking it was just me, but I can confirm I have copy pasted same address.worker name and can mine on DE but main SOLO is rejecting my authentication even if I put it as a backup..
sr. member
Activity: 419
Merit: 250
re: pool problems... it says "Failed authorization Sad" but I literally haven't changed a thing. Still [address].[worker] yes? I get same result on 3334 and 3333
Sure you haven't added a space or something in your username in your miner's config during copy/paste? Also once you fail to authorise you get throttled for attempted auths for the next 10 minutes (this has always been the case though).

yeah 100% sure all i did was turn off my miners for like a day. oh and i had them pointed to kano.is for a while as well.
That is most unusual indeed. Last time this happened to someone on this forum they restarted their machine and re-entered their credentials and everything worked after that. Perhaps in failover you never noticed it had never mined on solo and was always running on a backup?

i'll reboot tomorrow sometime. happily mining on DE server right now.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
re: pool problems... it says "Failed authorization Sad" but I literally haven't changed a thing. Still [address].[worker] yes? I get same result on 3334 and 3333
Sure you haven't added a space or something in your username in your miner's config during copy/paste? Also once you fail to authorise you get throttled for attempted auths for the next 10 minutes (this has always been the case though).

yeah 100% sure all i did was turn off my miners for like a day. oh and i had them pointed to kano.is for a while as well.
That is most unusual indeed. Last time this happened to someone on this forum they restarted their machine and re-entered their credentials and everything worked after that. Perhaps in failover you never noticed it had never mined on solo and was always running on a backup?
sr. member
Activity: 419
Merit: 250
re: pool problems... it says "Failed authorization Sad" but I literally haven't changed a thing. Still [address].[worker] yes? I get same result on 3334 and 3333
Sure you haven't added a space or something in your username in your miner's config during copy/paste? Also once you fail to authorise you get throttled for attempted auths for the next 10 minutes (this has always been the case though).

yeah 100% sure all i did was turn off my miners for like a day. oh and i had them pointed to kano.is for a while as well.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
re: pool problems... it says "Failed authorization Sad" but I literally haven't changed a thing. Still [address].[worker] yes? I get same result on 3334 and 3333
Sure you haven't added a space or something in your username in your miner's config during copy/paste? Also once you fail to authorise you get throttled for attempted auths for the next 10 minutes (this has always been the case though).
sr. member
Activity: 419
Merit: 250
@-ck will you ever run a solo bitcoin classic pool? maybe on a different port? just wondering...

Also, I think there are connection problems for the main pool? DE pool works fine (7:23pm EST, 2/2/2016)
Not unless classic usurps mainline.

No problems at main pool that I can see - usual problems are incomplete stratum implementations by rental services rendered non-working on the main pool due to it being behind an extra layer of DDoS protection - try port 3334 which is less protected.

good to know re: classic

re: pool problems... it says "Failed authorization Sad" but I literally haven't changed a thing. Still [address].[worker] yes? I get same result on 3334 and 3333
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
@-ck will you ever run a solo bitcoin classic pool? maybe on a different port? just wondering...

Also, I think there are connection problems for the main pool? DE pool works fine (7:23pm EST, 2/2/2016)
Not unless classic usurps mainline.

No problems at main pool that I can see - usual problems are incomplete stratum implementations by rental services rendered non-working on the main pool due to it being behind an extra layer of DDoS protection - try port 3334 which is less protected.
sr. member
Activity: 419
Merit: 250
@-ck will you ever run a solo bitcoin classic pool? maybe on a different port? just wondering...

Also, I think there are connection problems for the main pool? DE pool works fine (7:23pm EST, 2/2/2016)
legendary
Activity: 872
Merit: 1010
Coins, Games & Miners
To minimise I/O use a ckproxy -p ...

Is that "ckproxy" the same as ckpool from here?
Wrong link. That person forked a copy of it... Otherwise, yes, the thread link has been in my sig for ages.

https://bitbucket.org/ckolivas/ckpool

Talk about selective blindness.... from the noise of the signatures i was actively ignoring sigs and didn't see that info... gonna test your proxy.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
To minimise I/O use a ckproxy -p ...

Is that "ckproxy" the same as ckpool from here?
Wrong link. That person forked a copy of it... Otherwise, yes, the thread link has been in my sig for ages.

https://bitbucket.org/ckolivas/ckpool
legendary
Activity: 872
Merit: 1010
Coins, Games & Miners
To minimise I/O use a ckproxy -p ...

Is that "ckproxy" the same as ckpool from here?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
What is the best way to set up my network for best communications to -ck pool? right now i have around 20 S4's and 4 SP30's on a 24 port switch
my speed is 130Mb down and 5Mb up.  is it best to have them all going out? or setup a node?
To minimise I/O use a ckproxy -p ...
legendary
Activity: 3500
Merit: 2792
Enjoy 500% bonus + 70 FS
Thanks for the fast answer CK...
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
and a other question to the new stats.

it is possible to insert a "new line" after each worker, so it could better read...

Code:
{"hashrate1m": "1.06P", "hashrate5m": "1.06P", "hashrate1hr": "495T", "hashrate1d": "109T", "hashrate7d": "250T", "lastupdate": 1454399009, "workers": 6, "shares": 83851550250, "bestshare": 8932604530.6144924, "bestever": 334417443951, "worker": [{"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "59.3T", "hashrate7d": "109T", "lastupdate": 1454399009, "shares": 24206665784, "bestshare": 8932604530.6144924, "bestever": 24745111018, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_bitcoinlotto2"}, {"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "20.8T", "hashrate7d": "129T", "lastupdate": 1454399009, "shares": 40342440925, "bestshare": 373597880.047912, "bestever": 334417443951, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_bitcoinlotto1"}, {"hashrate1m": "1.06P", "hashrate5m": "1.06P", "hashrate1hr": "495T", "hashrate1d": "28.9T", "hashrate7d": "4.19T", "lastupdate": 1454399009, "shares": 591441012, "bestshare": 1751075839.882755, "bestever": 1751075839, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto"}]}

new line

Code:
{"hashrate1m": "1.06P", "hashrate5m": "1.06P", "hashrate1hr": "495T", "hashrate1d": "109T", "hashrate7d": "250T", "lastupdate": 1454399009, "workers": 6, "shares": 83851550250, "bestshare": 8932604530.6144924, "bestever": 334417443951, 
"worker":
{"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "59.3T", "hashrate7d": "109T", "lastupdate": 1454399009, "shares": 24206665784, "bestshare": 8932604530.6144924, "bestever": 24745111018, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_bitcoinlotto2"},
{"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "20.8T", "hashrate7d": "129T", "lastupdate": 1454399009, "shares": 40342440925, "bestshare": 373597880.047912, "bestever": 334417443951, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_bitcoinlotto1"},
{"hashrate1m": "1.06P", "hashrate5m": "1.06P", "hashrate1hr": "495T", "hashrate1d": "28.9T", "hashrate7d": "4.19T", "lastupdate": 1454399009, "shares": 591441012, "bestshare": 1751075839.882755, "bestever": 1751075839, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto"}]}
No. This site returns valid json, not fancy web stats.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hello CK,

have the USA Pool a Problem?
My fix Nicehash order with 1PHs goes always canceld, by nicehash...
I try now the german DE Pool

Greetings
Willi

Update:
The DE Pool ist stabl and the 1PHs Rental works..

{"hashrate1m": "1.12P", "hashrate5m": "950T", "hashrate1hr": "254T", "hashrate1d": "13.6T", "hashrate7d": "1.97T", "lastupdate": 1454397749, "shares": 277366380, "bestshare": 1751075839.882755, "bestever": 1751075839}
Read website. It says what for incompatible rentals to use port 3334. The main pool has an extra layer of DDoS protection.
legendary
Activity: 3500
Merit: 2792
Enjoy 500% bonus + 70 FS
and a other question to the new stats.

it is possible to insert a "new line" after each worker, so it could better read...

Code:
{"hashrate1m": "1.06P", "hashrate5m": "1.06P", "hashrate1hr": "495T", "hashrate1d": "109T", "hashrate7d": "250T", "lastupdate": 1454399009, "workers": 6, "shares": 83851550250, "bestshare": 8932604530.6144924, "bestever": 334417443951, "worker": [{"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "59.3T", "hashrate7d": "109T", "lastupdate": 1454399009, "shares": 24206665784, "bestshare": 8932604530.6144924, "bestever": 24745111018, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_bitcoinlotto2"}, {"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "20.8T", "hashrate7d": "129T", "lastupdate": 1454399009, "shares": 40342440925, "bestshare": 373597880.047912, "bestever": 334417443951, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_bitcoinlotto1"}, {"hashrate1m": "1.06P", "hashrate5m": "1.06P", "hashrate1hr": "495T", "hashrate1d": "28.9T", "hashrate7d": "4.19T", "lastupdate": 1454399009, "shares": 591441012, "bestshare": 1751075839.882755, "bestever": 1751075839, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto"}]}

new line

Code:
{"hashrate1m": "1.06P", "hashrate5m": "1.06P", "hashrate1hr": "495T", "hashrate1d": "109T", "hashrate7d": "250T", "lastupdate": 1454399009, "workers": 6, "shares": 83851550250, "bestshare": 8932604530.6144924, "bestever": 334417443951, 
"worker":
{"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "59.3T", "hashrate7d": "109T", "lastupdate": 1454399009, "shares": 24206665784, "bestshare": 8932604530.6144924, "bestever": 24745111018, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_bitcoinlotto2"},
{"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "20.8T", "hashrate7d": "129T", "lastupdate": 1454399009, "shares": 40342440925, "bestshare": 373597880.047912, "bestever": 334417443951, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_bitcoinlotto1"},
{"hashrate1m": "1.06P", "hashrate5m": "1.06P", "hashrate1hr": "495T", "hashrate1d": "28.9T", "hashrate7d": "4.19T", "lastupdate": 1454399009, "shares": 591441012, "bestshare": 1751075839.882755, "bestever": 1751075839, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto"}]}
full member
Activity: 637
Merit: 131
What is the best way to set up my network for best communications to -ck pool? right now i have around 20 S4's and 4 SP30's on a 24 port switch
my speed is 130Mb down and 5Mb up.  is it best to have them all going out? or setup a node?
Jump to: