newbuntu
Member
Offline
Activity: 61
Merit: 10
|
|
October 22, 2014, 08:18:21 PM |
|
That hash is worthless it doesn't meet the target, that's an error you're seeing. A miner is submitting crap. This usually happens if they mine using a different hash algorithm, for example.
All my miners are S3 Antminers, I assume they all use the same algorithm. So this is just a one-off glitch or something? Cheers.
|
|
|
|
|
|
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
PatMan
|
|
October 22, 2014, 08:23:18 PM |
|
It shouldn't happen very often, rarely in fact. I find my S3's run best using --queue 0 in the cgminer settings, use the latest version also
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
October 22, 2014, 09:08:50 PM |
|
That hash is worthless it doesn't meet the target, that's an error you're seeing. A miner is submitting crap. This usually happens if they mine using a different hash algorithm, for example.
All my miners are S3 Antminers, I assume they all use the same algorithm. So this is just a one-off glitch or something? Cheers. What probably happened was p2pool increased the min pseudo share size and the S3 hadn't switched yet and submitted a share size smaller than was allowed. I saw this regularly when analyzing how well S2s don't perform with p2pool. It's a pseudo share, so nothing lost. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
naplam
|
|
October 22, 2014, 09:33:59 PM |
|
No, the hash in that share was completely off, no 0 bits. I'd guess it's a hardware glitch. Not much of a problem if it happens only rarely but it should never happen normally.
|
|
|
|
newbuntu
Member
Offline
Activity: 61
Merit: 10
|
|
October 22, 2014, 10:56:08 PM |
|
It shouldn't happen very often, rarely in fact. I find my S3's run best using --queue 0 in the cgminer settings, use the latest version also How do I input this --queue 0 setting into cgminer? I have ssh into one of the miner and entered vi /etc/config/cgminer there are about a dozen settings listed there all starting with the word "option" (no quotes) is this where the --queue 0 setting goes? Cheers.
|
|
|
|
PatMan
|
|
October 22, 2014, 11:20:06 PM |
|
It shouldn't happen very often, rarely in fact. I find my S3's run best using --queue 0 in the cgminer settings, use the latest version also How do I input this --queue 0 setting into cgminer? I have ssh into one of the miner and entered vi /etc/config/cgminer there are about a dozen settings listed there all starting with the word "option" (no quotes) is this where the --queue 0 setting goes? Cheers. vim /etc/init.d/cgminer Go to end of line 75 (older firmware) 70 (newer firmware) Press “i” (enter edit mode) Change the setting --queue 0 --failover-only press "esc" (exit edit mode) type ":wq" (without quotes) Press "enter" Go to web GUI, miner configuration, click "save & apply" Done To check, go to processes tab, you should see the miner settings showing the new queue value on the cgminer process.
|
|
|
|
newbuntu
Member
Offline
Activity: 61
Merit: 10
|
|
October 22, 2014, 11:48:56 PM |
|
It shouldn't happen very often, rarely in fact. I find my S3's run best using --queue 0 in the cgminer settings, use the latest version also How do I input this --queue 0 setting into cgminer? I have ssh into one of the miner and entered vi /etc/config/cgminer there are about a dozen settings listed there all starting with the word "option" (no quotes) is this where the --queue 0 setting goes? Cheers. vim /etc/init.d/cgminer Go to end of line 75 (older firmware) 70 (newer firmware) Press “i” (enter edit mode) Change the setting --queue 0 --failover-only press "esc" (exit edit mode) type ":wq" (without quotes) Press "enter" Go to web GUI, miner configuration, click "save & apply" Done To check, go to processes tab, you should see the miner settings showing the new queue value on the cgminer process. Perfect instructions. Thank you very much. Very helpful.
|
|
|
|
PatMan
|
|
October 23, 2014, 12:01:08 AM |
|
Thanks & you're welcome These settings will stay after a reboot too, so no need to keep doing it. I find I get far fewer DOA/rejects using the zero setting, but it's not a hard & fast rule, it depends on your setup/network - many use "1" as their queue setting (ck recommended setting) with good results also - it's a case of suck it & see Peace
|
|
|
|
Polyatomic
|
|
October 23, 2014, 05:02:40 AM Last edit: October 23, 2014, 07:05:28 AM by Polyatomic |
|
If you have polled upstream and the recommended value for queue is 1, why use 0.
|
|
|
|
PatMan
|
|
October 23, 2014, 09:17:59 AM |
|
Because I find I get far fewer DOA/rejects using the zero setting, but it's not a hard & fast rule.....
Use whatever works best for you
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
October 23, 2014, 09:55:57 AM |
|
If you have polled upstream and the recommended value for queue is 1, why use 0.
its a fix for a problem years ago. everyone who still uses/recommends it dosnt know anything about what hes doing
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
PatMan
|
|
October 23, 2014, 10:18:10 AM |
|
If you have polled upstream and the recommended value for queue is 1, why use 0.
its a fix for a problem years ago. everyone who still uses/recommends it dosnt know anything about what hes doing Attitude? Use whatever works best for you Be nice
|
|
|
|
IYFTech
|
|
October 23, 2014, 10:36:10 AM Last edit: October 23, 2014, 12:59:42 PM by IYFTech |
|
@ Ki773r: PatMan is correct. I done some testing of these settings some time ago & posted the results: I've ordered from batch 1, batch 4 and batch 5. Even in batch 5 the issues remain, although I did get "lucky" as one of my batch 5 units actually hashes at 504GH/s stable.
I also have one of those lucky ones at 505Gh/s from B1 - it's the most stable one out the lot!! Following up from this, I've been experimenting a little more with my settings & here's a screen of the results: (click for larger) This is 4 x S3's running at various clock speeds. Looking at the graph, I was running --queue 1 up until ~3am (yup, I'm a night time fiddler ) before changing the setting to --queue 0 & letting them run for the same amount of time. It can clearly be seen that after changing the setting to --queue 0, the DOA rate dropped & smoothed out - this was also confirmed by my nodes info page. Average hash rate was slightly higher as a result, so I'll be keeping all my S3's running with the --queue 0 setting from now on. I'm not saying that this will work for everyone, but it's definitely good for my setup & worth giving a try if you're experiencing a higher than expected DOA rate. The dip in hash rate at the end of the graph was due to a reboot after updating Xubuntu. Smoke'em if ya got'em Edit: It's also worth mentioning that my reject rate was at ~4% with --queue 1 - and ~2% with the 0 setting. This is running on a local node. You are quite knowledgeable of p2pool, but to suggest that someone "doesn't know anything about what he is doing" when they clearly do, belittles you & your "legendary" status. Seems you owe him an apology
|
|
|
|
PatMan
|
|
October 23, 2014, 10:39:09 AM |
|
I was just looking for that - I remember reading it, thanks
|
|
|
|
MissouriMiner
|
|
October 23, 2014, 09:59:15 PM |
|
A Q6700 was great in its day, but you can't go by GHz alone. That chip is now 7 years old! That's ancient in compute terms. I use this link below to judge single thread performance. Even a 1 year old i3 is twice as fast. Sorry, don't mean to rip on the Q6700. I loved that chip, in its day. https://www.cpubenchmark.net/singleThread.html
|
|
|
|
pimpstar
Newbie
Offline
Activity: 1
Merit: 0
|
|
October 24, 2014, 02:11:15 AM |
|
Hi everyone, I'm having a bit of trouble installing/setting up p2pool to mine with litecoin (will be merge mining later when i can get this done first). The issue im having is whenever i point my miner to my p2pool, it says this after New Work for Worker: "> Couldn't link returned work's job id with its handler. This should only happen if this process was recently restarted!" and it just floods with this message. Any idea on how I can fix this? Any help is greatly appreciated
|
|
|
|
newbuntu
Member
Offline
Activity: 61
Merit: 10
|
|
October 24, 2014, 04:34:58 AM |
|
Hi everyone, I'm having a bit of trouble installing/setting up p2pool to mine with litecoin (will be merge mining later when i can get this done first). The issue im having is whenever i point my miner to my p2pool, it says this after New Work for Worker: "> Couldn't link returned work's job id with its handler. This should only happen if this process was recently restarted!" and it just floods with this message. Any idea on how I can fix this? Any help is greatly appreciated I get this when I restart the bitcoin program, it all clears up and acts normally after about 2 mins - have you let it run longer than a couple of mins?
|
|
|
|
newbuntu
Member
Offline
Activity: 61
Merit: 10
|
|
October 24, 2014, 09:41:19 AM Last edit: October 24, 2014, 02:56:54 PM by newbuntu |
|
Every once in a while I see a line that says "bad peer banned ... " can someone please elaborate on what this actually is? Is this actually someone attempting something nefarious? Is this a permanent ban for this peer? Is there a ban list I can manually edit? Cheers.
EDIT: I do have firewalls enabled for each device and at each level of the network.
|
|
|
|
Prelude
Legendary
Offline
Activity: 1596
Merit: 1000
|
|
October 24, 2014, 09:51:51 PM |
|
What are ideal share difficulty and pseudo difficulty settings for an S4?
|
|
|
|
PatMan
|
|
October 25, 2014, 12:14:34 AM |
|
What are ideal share difficulty and pseudo difficulty settings for an S4?
I don't own an S4, nor am I likely to, but I would hazard a guess at the standard 2048 that they work with? Maybe someone who's running one here can chime in? Peace
|
|
|
|
|