 Show Posts
|
|
Pages: [1]
|
|
Is there a solution hashrates to be updated only on benchmark?
The problem is, that now the hashrates are updated dynamic, not only on benchmark, also when mining after benchmark.
This causes bugs when sometimes miner is not closed, the hashrate from another algo is taken for not correct algo...
Also, when you have different GPU's and want to separate them in different miners, the hashrates become unreal... because there are different miners opened always to mine for different cards, and Nemos takes the hashrates and update them..
I found some solution, but it's not so good!
make all *hashrate files in /stats folder read only.. it's working for now, but there is red error in Nemos Miner, that it can't write to hashrate.txt files.
|
|
|
|
I also have the issue with "Very long miner warming up time" as reported in https://github.com/nemosminer/NemosMiner-v2.4.1/issues/94 . Alexis78 miner in nemosminer-23, but also polytimos and Alexis78Phi in nemosminer-241, have often this behavior on algo X17, Skein, Phi, blake2s, nist5. Only 1 or 2 miner threads/gpus are starting (out of 6) and after some long minutes (sometimes up to 10) the other gpus get full load. No errors are reported in miner log. Thats a really big performance drop. You closed the issue on github, but it seems that the problem still exist. Same problem here I lost 3 to 4 minutes sometimes when the miner switch. Only 1 or 2 GPU works, and after many minutes others comes alive This can happen when the miner "default" intensity is to high, look at the miner log for the command line arguments, open a command prompt window, cd to the bin folder where the miner is located (ie: Bin\NVIDIA-Alexis78Phi) paste the command line from the miner log and see what intensity value is used. (ie: -i 19, etc) and observe in afterburner how long it takes for all card to rev up, if takes to long, lower the intensity 1 point at time ( 19 -> 18...) until you can find the right intensity for your system. you can then edit the .ps1 miner file and add this setting. Hope this not too confusing. This start happening to me also.. i think that is some pool issue.. seems that some cards starts slower than others.. it started happening 5-6 days ago, before that i have more than 30 days uptime to my rig... and no such a problems.. i'll try with the older versions of Nemos to check.. OK, the problem is only with CCMiner Alexis78 i think.. i tried another miner for Alexis78 algos, and it's working! i'm using now CCMINER 2.2.2 for Alexis algos, and the problem is gone for now.. i'll write more when i finish the tests |
|
|
|
I also have the issue with "Very long miner warming up time" as reported in https://github.com/nemosminer/NemosMiner-v2.4.1/issues/94 . Alexis78 miner in nemosminer-23, but also polytimos and Alexis78Phi in nemosminer-241, have often this behavior on algo X17, Skein, Phi, blake2s, nist5. Only 1 or 2 miner threads/gpus are starting (out of 6) and after some long minutes (sometimes up to 10) the other gpus get full load. No errors are reported in miner log. Thats a really big performance drop. You closed the issue on github, but it seems that the problem still exist. Same problem here I lost 3 to 4 minutes sometimes when the miner switch. Only 1 or 2 GPU works, and after many minutes others comes alive This can happen when the miner "default" intensity is to high, look at the miner log for the command line arguments, open a command prompt window, cd to the bin folder where the miner is located (ie: Bin\NVIDIA-Alexis78Phi) paste the command line from the miner log and see what intensity value is used. (ie: -i 19, etc) and observe in afterburner how long it takes for all card to rev up, if takes to long, lower the intensity 1 point at time ( 19 -> 18...) until you can find the right intensity for your system. you can then edit the .ps1 miner file and add this setting. Hope this not too confusing. This start happening to me also.. i think that is some pool issue.. seems that some cards starts slower than others.. it started happening 5-6 days ago, before that i have more than 30 days uptime to my rig... and no such a problems.. i'll try with the older versions of Nemos to check.. |
|
|
|
I have a issue from today.. seems that there is some problem with the coinbase api Loading pool stats.. Error contacting pool, retrying.. Loading BTC rate from 'api.coinbase.com'.. Invoke-RestMethod : The remote name could not be resolved: 'api.coinbase.com' At C:\Users\dsa\Downloads\NemosMiner-v2.3c-beta\NemosMiner-v2.3c-beta\NemosMiner-v2.3.ps1:94 char:14 + ... $Rates = Invoke-RestMethod " https://api.coinbase.com/v2/exchange-r ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebExceptio n + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand |
|
|
|
They were running ~2500 miners about a week ago. Now 3148 so that makes sense.
Or they needed extra cash for NYE party  |
|
|
|
|
Same Here,
Balans is strage since last payment.. after the payment may be 2-3 hours there was another correction.. i don't know what they are doing.. but with this no reply on email.. i'm worried..
|
|
|
|
|
I think that is time pools to pay in Litecoin.. BTC will be dead soon with this slow and expensive transactions
|
|
|
|
Who is the pool owner? Are they on this forum? If so, can someone PM them to look at this thread?
PS: I sent an email to their support (at the bottom of their page) yesterday, but haven't received a response yet.
The big problem for me is.. not actually that the transaction is pending.. the problem is, that they do not answer their email.. i wrote them 5 days ago.. and till now nothing! It's not good, that they do not answer to their community! |
|
|
|
Mine is also stuck 18/12 - Second last payout.
I really like Ahash. Never been paid more somewhere else. Hope they will fix it somehow. Perhaps the transaction might go through in a few days.
I did get my last payment, so no problems there.
Yes, me too.. it seems that the problem is just that transaction from 6 days.. may be they had wrong counting of mining tax for it. |
|
|
|
|
I also had a pending transaction from there.. 5 days... i think that, there fee's are too small! they trying to save money!.. but they loosing miners!
|
|
|
|
This has been unconfirmed for 4 days now:
Transaction ID:
db6bb8166d355906d1b78ffa5a43a032556731439b0f2a4b67441bd74e1183e3
While I understand the network is congested, ahashpool sent a payout just 9 hours ago and it has 60 confirmations so far. So when a new payout get confirmations before an old one, combined with being 4 days now, it's easy to see why I'm concerned now.
Been patiently waiting until I saw the new payout going through but not the last one.
Here's the one that went through:
Transaction ID:
dd74b94811408bcdf4667e40020b4f92b8e715a852f3ab3985534106ddf6ad22
Yes, i have also payment in that transaction!!! and they do not answer on email!.. i think to stop mining in this pool! Every time problems there with the transactions.. small feels bla bla bla etc.! |
|
|
|
|
