Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 116. (Read 289447 times)

Sucks, was mining away and suddenly couldn't connect.  Should have kept it our little secret.

Shoot, ahashpool went from avg 4000 miners to 10,674 tonight and is overloaded! 

Hi,

It seems I'm not the only one having issue connecting to zpool24h pool status.

I constantly have the message Error contacting pool, retrying..

Hopefully, if we join efforts we can get to the bottom of this...

What I found so far:

I have 2 minirigs.
When they start failing to get the pool status, it keeps trying for a long long time before receiving a response.
If I stop both and wait a few minutes and start one and wait few more minutes before starting the other, it seems that's easier to get it to work. but not good, since this is manual intervention and lots a minutes without mining.

I modified the zpool script to get more details and found that the web request succeed with http 200 status but the content is empty (no stats).

Trying to get the status manually from the browser or a port of wget have the same issue. And after a successful request with content, retrying will get an empty response again.

Trying to get the status from a different internet connection have the same issue (on my mobile phone).

trying a web proxy page, so it access the status api from a different location will have the same issue.

At this point I don't think it's a nemosminer script issue. probably some error not correctly handle on the zpool server or perhaps some API request rate limit.

As anyone have more info? Should send a post on the zpool topic but wanted to get the more info from the people having the same issue here.

You probably have guess by now, English is not my native language. Hopefully my writing is some what understandable.

Happy 2018 mining

thanls i'll do some testing and sort it out

working on Palgins HSR miner atm... any help testing would be appreciated :

https://github.com/nemosminer/NemosMiner-v2.3/archive/2.3.1+Palgin.zip
NemosMiner-v2.3.1+Palgin HSR Neoscrypt(testing)

palgins mod 1.1 i have had in nemosminer in the past there was no need for it....

i'll do some testing but im sure my current Nist5 miner is just as fast if not faster...

Regards
Nemo

https://github.com/nemosminer/NemosMiner-v2.3/commit/fe321b67f95dc7d1f2cf734cb8578c99ac733056
thanks

yes 64gb pagefile is optimal i use 120gb ssd's on all my rigs (they getting pretty cheap now days)

yikes wants a 50GB page file for 6 (8gb GPU) cards else gives out of memory errors....  Can't happen when you have 64GB SSD running the show

Yes, I can, but it only works for myself

Can't you add it yourself?

Depends on algorithm, but in general +20% compared to 1070 and a bit over 1070 Ti.

Feature request：
add ccminer palgin mod 1.1 for nist5.
add palgin's hsrminer for neosrypt.

Trying to run zpool24hr, but keep getting error contacting pool, sometimes it will connect, but most of the time the error comes up, yet regular zpool works.  Any ideas?  Thanks

Greetings, do you know why this error comes out?

C:\Users\Pc Minera Guillermo\Downloads\NemosMiner-v2.3c-beta>powershell -version 5.0 -noexit -executionpolicy bypass -windowstyle maximized -command "&.\NemosMiner-v2.3.ps1 -SelGPUDSTM '0 1' -SelGPUCC '0,1' -Currency USD -Passwordcurrency BTC -interval 120 -Username nemo -Workername miningpoolhub -Location US -PoolName miningpoolhub
 -Type nvidia -Algorithm cryptonight,keccak,lyra2z,skein,equihash,groestl,MyriadGroestl,Lyra2RE2,neoscrypt -Donate 5
INFO: Adding NemosMiner path to Windows Defender's exclusions.. (may show an error if Windows Defender is disabled)
La transcripción ha comenzado. El archivo de salida es .\Logs\2018-01-03_10-12-03.txt
Loading BTC rate from 'api.coinbase.com'..
Invoke-RestMethod : Error en el servidor remoto: (403) Prohibido.
En C:\Users\Pc Minera Guillermo\Downloads\NemosMiner-v2.3c-beta\NemosMiner-v2.3.ps1: 94 Carácter: 14
+ ...    $Rates = Invoke-RestMethod "https://api.coinbase.com/v2/exchange-r ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Loading pool stats..
Error contacting pool, retrying..

Loading BTC rate from 'api.coinbase.com'..
Invoke-RestMethod : Error en el servidor remoto: (403) Prohibido.
En C:\Users\Pc Minera Guillermo\Downloads\NemosMiner-v2.3c-beta\NemosMiner-v2.3.ps1: 94 Carácter: 14
+ ...    $Rates = Invoke-RestMethod "https://api.coinbase.com/v2/exchange-r ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Loading pool stats..
Error contacting pool, retrying..

Loading BTC rate from 'api.coinbase.com'..
Invoke-RestMethod : Error en el servidor remoto: (403) Prohibido.
En C:\Users\Pc Minera Guillermo\Downloads\NemosMiner-v2.3c-beta\NemosMiner-v2.3.ps1: 94 Carácter: 14
+ ...    $Rates = Invoke-RestMethod "https://api.coinbase.com/v2/exchange-r ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Loading pool stats..

Any one runninh 1080 Nvidia cards on Nemosminer can tel about its profitibility in comparison with 1070 Nvidia?

I read the code, change pools\nicehash.ps1 to support JP:

You can use -Location Europe in the bat file, it's case sensitive .

FYI: a pool would not cause your computer to crash or reboot.

What can be causing this are PSU or GPU overload. leave your cards gpu/mem clocks at stock settings and lower your TDP to 75% in MSI afterburner and see if the issue persist.

This also could be happening due to the different intensity settings per algo/miner. you need to find the offending algo and miner and lower the intensity. once you have finned tuned all different algos/miner intensity then you can star tweaking the gpu/mem clocks.

Is more time consuming, but it will give you the benefit of almost peak performance + uptime.

Mind sharing your script?

While this is true, my rigs freeze or reboot daily with ahashpool which cuts down on those potential profits whereas they would run endlessly in zpool. Not sure what the difference is.

According to my experience, only "us" works. Neither asia, europe or eu works and gets stuck at contacting coinbase. I am in Europe.