|
Never seen such a behaviour, will look into it tomorrow.
|
|
|
|
|
The usual blah blah nonsense.
For memory light algos, just use the cuda cores count.
|
|
|
|
Hi all!
Mining on 2 rigs solo. Changed miner and can`t understand. 1 rig - ok, another shows:
[2017-07-13 15:25:44] [01;37maccepted: 0/1 (0.00%), 4773 kh/s[0m [01;31mNO[0m
[2017-07-13 15:25:44] [01;37maccepted: 0/2 (0.00%), 4773 kh/s[0m [01;31mNO[0m
[2017-07-13 15:25:44] [01;37maccepted: 0/3 (0.00%), 4196691 kh/s[0m [01;31mNO[0m
[2017-07-13 15:25:44] [01;37maccepted: 0/4 (0.00%), 2093266 kh/s[0m [01;31mNO[0m
....
and close itself.
PL - 100, CC, MC - 0.
Anyone knows what it can be?
Both rigs - Win10.
hashrate is not good, you must have some cuda issue. what cards? |
|
|
|
Where I can ask some questions to devs? Maybe slack or telegram? Of just ask here.
Here or on slack. |
|
|
|
|
you must ask bittfreak, I'm no windows expert.
|
|
|
|
Could you check the Connection error with djm34, please?
Go for solo mining. The coin is so old and so bad programmed in case of rpc that it's simply not working well I remember it was working perfectly well on xcn.1ghz pool (or smthng like that) when it was alive ... The trie has grown since then :-) |
|
|
|
One more question... There is another problem. Started mining on 3 rigs in 1 wallet over internet to static IP. After 6-8 hours miner shows the speed, like everything is normal, but I see that the temperature of the card dropped to idle temperature. I go to afterburner consumption of the GPU - there is a strange graph...jumps from 0 to 50-60. (in attachment file) Well, the load GPU is zero. What can it happen ? Restarting the miner doesn't help and needed to restart the wallet. Maybe someone came across ))) In image - left graph - normal mining, near the middle graph goto wrong mode... Temperature in normal mining about 60 C Temperature in wrong mode about 40 C http://prntscr.com/fv2xocRestarting the miner doesn't solve the problem: http://prntscr.com/fv37rvthat's because the wallet is busy and doesn't respond quickly enough when a new getwork call is made by the miner. one of the reasons to try higher values for "-s". |
|
|
|
hello i try to on simpleminigos. i m getting this message.
aclocal.m4: command not found
./sgminer: line 3: aclocal.m4: command not found
./sgminer: line 4: aclocal.m4: command not found
./sgminer: line 5: aclocal.m4: command not found
./sgminer: line 6: aclocal.m4: command not found
./sgminer: line 6: you: command not found
./sgminer: line 7: aclocal.m4: command not found
./sgminer: line 8: syntax error near unexpected token `('
./sgminer: line 8: ` * Software Foundation; either version 3 of the License, or (at your option)'
how can i mining cannabiscoin on simpleminingos. any body have a hot to guide step by step ?
thak you.
don't use this software, it's obsolete. look for newer sgminers. |
|
|
|
If XCN survives this time, it most definitely has more lives than a cat, maybe even more than Mario  Any news for a new pool? If ocminer refuses to help XCN survive, maybe we can track down catia, or the the old 1GH crew? Bitfreak, we know you still love your baby, please come back  Me and another couple guys have been working on the pool code together for some days, I think we are almost there. You can follow the development on the slack channel. |
|
|
|
I experienced weird errors from ccminer when using "-s 1", but only on some rigs... not sure why, I didn't investigate as they did never happen when using "-s 2".
Right, but in theory - if my miners doesn't give me any errors at all, I should (again, in theory) be able to reduce stable blocks by scanning every second instead of every two seconds, correct? Yes and no. Setting a low scantime means more requests made to the wallet, hence more load, so the end result may be difficult to predict. |
|
|
|
with the last blockchain you posted pallas i'm stuck again at 3 days behind....
how many connections? what does the debug.log say? 8, debug say orphan already exist!!! hmmm looks like your chain got corrupted. I tested the snapshot myself so I know it's ok. start fresh or with or without the snapshot. |
|
|
|
blocks rejected by the wallet (reported by the miner) are stale, i.e. the miner solved a block but the wallet received a new block meanwhile (this should be attenuated by "-s 2").
or, as it's called by sgminer, "hardware error" (nonce does not verify).
So in order to decrease stale blocks even further, I should use "-s 1" in the miners. You've previously said that the miners sometimes can get wonky (or something like that), but when I used "-s 1" everything worked just fine for all my rigs. Is there something under the hood so I won't notice if it doesn't work? I experienced weird errors from ccminer when using "-s 1", but only on some rigs... not sure why, I didn't investigate as they did never happen when using "-s 2". |
|
|
|
More questions...
I launched cryptonite-qt for win.
On local addresses everything works as it should. ( farms in local network working on this one wallet excellent)
I try to make it through the Internet, it does not connect.
Ping from mining farm to my_static_IP_adress is good=47ms.
Likely, you are pinging the router. Can you check the NAT rule in some way, using another protocol for example. |
|
|
|
Hi. My wallet under Windows synchronizes the whole day, or even more. The connections are from 1 to 14. If you look at the log file, you can see that there are errors like on the attached image. Does it all happen this way? Or this should not be? http://prntscr.com/fupfl1that's normal behavior, it's downloading recent blocks. that may be a slow process because of cpu or network connection. |
|
|
|
You are comparing your hashrate (miner side, counting orphans) to the net hashrate (which doesn't takes orphans into account).
So, you don't have 10% of the total hashrate but probably around 5%.
Alright, but then something has to be done about the orphans then. And what can we/I do? I would also like it explained why SOME blocks are added to my transactions as "generated buy not accepted" while MOST aren't? What's the dirfferynce between those rejects and other rejects that the miners report? blocks rejected by the wallet (reported by the miner) are stale, i.e. the miner solved a block but the wallet received a new block meanwhile (this should be attenuated by "-s 2"). or, as it's called by sgminer, "hardware error" (nonce does not verify). |
|
|
|
|
Additional pool not ready yet.
Ocminer won't share his code, so we are doing it from scratch.
3 people working on it.
Thing to do to make an xcn pool: import M7 hashing code, adapt custom stratum side, adapt custom getblocktemplate side.
|
|
|
|
So what's the som behind there being more orphans than there should be?
And there should be 1440 blocks found each day, that doesn't include orphans. So where does the remaining correct block go?
You are comparing your hashrate (miner side, counting orphans) to the net hashrate (which doesn't takes orphans into account). So, you don't have 10% of the total hashrate but probably around 5%. |
|
|
|
with the last blockchain you posted pallas i'm stuck again at 3 days behind....
how many connections? what does the debug.log say? |
|
|
|
I wouldn't say that things seem to work correctly if I have 10% of the net hash but get less than 5% of the blocks with 50% rejected blocks.
Right, I got the ports mixed up. I've been connecting to the RPC port all the time so nothing wrong there. I don't get any errors when connecting or mining and things are running along fine.
The problem is that 50% of my found blocks get rejected, which shouldn't be the case.
I get that orphans can happen, but 50% of my found blocks can't be orphans.
Also, some (though very few) blocks are added to the wallet as "generated but not accepted". What does that mean? They are few and far in between though, so they're not the ones that the miner reports as rejected (at least not all of them).
During the last 37 hours I've found 82 blocks. But since I have 10% of the net hash, I should have found 222. I get that luck is involved, but my miners does report about 50% rejected.
If all those would have been accepted that would've been 164 which isn't too far off 222, which I could say is the lack of luck.
orphans: there are a lot for everybody, if you followed the thread (and if you didn't, just read the last pages) you will see that's an open discussion. |
|
|
|
Hi guys,
Are you sure a single wallet (cryptonited server) works for several miners?
How could I test/check it?
is there any api i could use to query the wallet/service?
I have several miners connecting to the wallet and I see they are working, they are doing requests, connected, they do the expected hashrates... however, I don't see the expected improvements in my block discovery. I could have been unlucky but I feel that I achieve the equal hashrate to the maximum of a single rig. ie if I have a rig with 72Mhash, and two other rigs of 40Mhs I dont see a 152MHash but a 72Mhash... of course this could be just "woolly thinking"
BTW. Is accurate the whattomine expected block rewards? if not, how could I measure it?
single wallet: yes. api: the usual bitcoin rpc calls. remember there are a lot of orphans: if you followed the thread (and if you didn't, just read the last pages) you will see that's an open discussion. whattomine reports wrong profits: do your own math (it's always the best way); how to? read the last pages of the thread ;-) |
|
|
|
|
Show Posts
