To put it simply, we're dealing with the usual fuckage and nothing can really connect to the pool while it's happening even though the pool is still running, and try to restart things as soon as possible to minimise the downtime. We've excluded quite a few possible causes but not found the problem yet and are still investigating and hopefully narrowing in on the true cause.
We all appreciate the effort you both put into keeping this ship afloat, I've no doubt this bug will be squashed. Wow, gotta say, totally awesome. Bitmain of course dropped the ball on this and have given up on anyone who bought their S1/S2/S3 saying they don't care. However, someone (who wants to remain anonymous) has sent me 10BTC and asked me to do the S1/S2/S3 work. Guess I'll be spending the time on this over the next 2 weeks that I was asking to do and get the S1/S2 updated and sort out some p2pool issues, and also merge a working S3 into cgminer master  (and of course dust off my old S1/S2 and get them working again) The kano.is pool problems (and a backend ckdb change I've been working on) have been taking a lot of my (and of course -ck's) time, but I think I can handle both (if I ignore everything else  ) Good news I have to agree, totally awesome! Thank you, anonymous. My S1 and S3+ thank you as well. Good luck, Kano, should be a fun project. |
|
|
|
I am now member so please update my account to member account soon !!!
You need to use the member sig. |
|
|
|
CryptoGlance uses the Difficulty Stale value. You can double check values received from the API by pressing CTRL + D in cryptoglance. This will break you to a simple debug page. Enter the miner in question and it will spit out every value returned by cgminer.
Very cool, thanks for the tip. |
|
|
|
If you delete and re-add the device it comes back showing the correct pool. Easy temp. fix for few miners (1 affected in my case).
Despite my primary pool restarting several times in the last 24h and the miner going to failover pool, the deleted/re-added (since I installed 2.1.0.4-beta) device is currently displaying the correct pool it's mining to (primary). Now, whether or not the display changed to shown the failover pool at the times I cannot say, so it's possible the pool field never changed, but I just wanted to share the observation. I have noticed one other issue: cgminer shows several stale shares being submitted, I just watched 3 as I typed this, but crytoGlance always shows 0 for stale shares. I understand CG can only show what the api gives it, so it this an api issue? |
|
|
|
Should have just shown up as a reconnect in cgminer and nothing obviously different from the miner's point of view.
Yup, just looked like any of the other recent restarts. |
|
|
|
Thanks again Phil. Your driving this bus so you do what you thinks best. Let's find a block!
There's no "us" here (as in let US find a block), this is solo mining! Phil said earlier they are splitting some hash rate. So I would assume they both put in some BTC and will split the block if they get lucky. Ahh, got it, so "us" really means "them". Darn pronouns. Good luck to us and them! |
|
|
|
Thanks again Phil. Your driving this bus so you do what you thinks best. Let's find a block!
There's no "us" here (as in let US find a block), this is solo mining! |
|
|
|
|
Don't be greedy, you're not even in the campaign for crying out loud.
|
|
|
|
|
Woo, another green block! Makes up for the big red one.
|
|
|
|
|
"bestshare": 39920950.857848018
My machines are pretty consistant at finding shares in the 107 - 108 range. I just got into mining a couple months ago, about 700gh/s, and have yet to get a share in the billions. But it's all chance, and that block busting best share could be right around the corner...
|
|
|
|
Hello, today an s3 of mine stopped working, when I turn it on the fans immediately start running at full speed, and it does not hash, blades and fan speed don't appear on the miner status tab. Does anyone know what could happen?  Thanks in advance you may have to input a dns server ip in manually. Check DNS IP use google to test 8.8.8.8 Or, likewise, input the pools by ip address and if it mines then your dns is bad. |
|
|
|
|
Right on. I tried mine at 262.5 and it freaked out, had ASICs showing ooo-o-- and hash rates were way down. I settled at 250 also, nice balance of overclocking without running the machine into the ground.
I don't know anything about queue, sorry.
|
|
|
|
|
Creeping slowly towards positive...
|
|
|
|
I like that 9.34% block after the bad one. We could use a few more of those!
It looks like my miners have been failing over to the solo pool a lot overnight, so I take it that the pool issue still hasn't been tracked down. Maybe I'll get lucky during one of the pool restarts.
Interesting, TheOneJester's little app notified me when we hit the 390% block, but I don't have a notification about the 9% block. Anyway, glad we finally knocked a couple down, let's keep those percents green! we found a block between two restarts, showing the expected result only that the short failover/failback time reduces the total hashes jsut when that ahppens, it doesn't stop the pool from finding blocks.
Good to have that confirmation despite the assurance that the pool "still works" despite the restarts. |
|
|
|
A new Nightly + Beta has been rolled out, this is specifically for bug fixes. [ v2.1.0.3-beta ]
KNOWN ISSUES
============
- Miner Failover may report incorrect active pool
If you delete and re-add the device it comes back showing the correct pool. Easy temp. fix for few miners (1 affected in my case). |
|
|
|
you need atleast full member before you can change your avatar
The post right above your is Jr. Member with an avatar. I know. Thats why i said "change". Is it clear to you now? No, how did they get an avatar in the first place? Have to change it from nothing at some point. |
|
|
|
you need atleast full member before you can change your avatar
How is the post right above you a Jr. Member with an avatar? |
|
|
|
|
I can stop at the local BevMo and have them scan it and print a dated receipt which I can show as proof the card is still good.
|
|
|
|
the newest firmware kind of sucks anyway, i use the 12/19/2014 one.
What "sucks" about it more specifically? What are the advantages to the 12/19 version? Well...I D/Led cgywin and started reading up on how to use it....sheesh! Guess I'll look for putty and see if that's any easier.
I'll track down the info I have put together, it's really very simple once you know what to do (yea, isn't everything? lol). Learning to use the vi editor is way more confusing, just wait...  Ok...sounds good. I have gotten in /w puTTy but I still get the 'Permission Denied' error. Won't let me mod. Ok, here's how I did it with Cygwin (might work wtih putty, too? I've never used putty): 1) Follow Part 1, Steps 1-3 here: http://www.wikihow.com/Use-SSH2) Login with SSH using the IP and username/password you’ve set it to use cd /usr/lib/lua/luci/model/cbi/cgminer/ 3) How to use the vi editor: http://www.cs.colostate.edu/helpdocs/vi.htmlinsert data from https://bitcointalk.org/index.php?topic=699064.msg8370071#msg8370071Save the changes, exit vi, type “reboot” (without the quotes) to restart the miner |
|
|
|
Reset or restart?
Restart miner, fixed post above. What version are you running of cgminer? It was the beta before this one, 2.1.0.1-beta? I haven't tried it with .4, I can tomorrow if it would help. |
|
|
|
|
Show Posts
