[NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 114.

Tinouti

newbie

Activity: 10

Merit: 0

Quote from: pttrade on January 03, 2018, 05:01:09 PM

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.

I'm pretty much at the same place right now.

When I'm trying to access the status from my phone, it works the first time, then return a blank page. If I switch airplane mode on and off (and thus getting a new IP), it'll work again the first time, then blank after that.

So I think that - like you assumed - zpool must have added a request limit per IP.
I don't know what the time limit is, but if we can't get the pool status, that pretty much negate the point of having a multialgo switching miner.

I guess we'll have to forget about zpool for the time being. Undecided

sundownz

hero member

Activity: 714

Merit: 512

Quote from: sundownz on January 02, 2018, 02:25:44 AM

Quote from: minerx117 on January 02, 2018, 01:17:02 AM

testing Palgins new HSR miner for neoscrypt i have it downloading and Benchmarking but running into a issue with it not closing after completing benchmarks

you can test for yourself here: https://github.com/nemosminer/NemosMiner-v2.3/issues/130

Best Regards
Nemo

Awesome.

I am testing now on my home office PC... just got back in from Mexico =)

KlaustT 8.18 --> 1.43 MH/S
Palgin 1.0.1 --> 1.75 MH/S

GTX 1080Ti with very mild OC -- (+100 core / +200 mem) in my home office PC.

Very nice!

But yes... it seems to keep on running. So far it has failed to close after several cycles.

I am not a Powershell coder... but it seems to be calling for a .txt file that doesn't exist ?

millsys

member

Activity: 112

Merit: 10

Quote from: sirbrokealot on January 05, 2018, 08:17:08 PM

Quote from: millsys on January 05, 2018, 09:49:42 AM

Quote from: sirbrokealot on January 05, 2018, 08:15:56 AM

i have a lot of downtime with x17 and intensity 19, 20, 21 currently adjusted it to 17 ( ccminerAlexis78 )

im running 2x 1070ti strix a
@ 60% power +150 Core +600 Mem

anybody knows the reason for the miner to crash or not even get started`?

while mining phi ( CcminerTpruvotcuda9 ) it wont validate on my cpu ( this might be pool related? )
this occurs after reaching the peak hashrate

The Driver Versions differ from the 0 or 1 GPU
0 runs 388.71 WHQL [r388_43-17]
1 runs 388.71 WHQL [r388_43]
Both P2 State

i hope these are not stupid questions

Try 80% power/+100 core/+500 mem

thanks, i tried 80/100/500 it got a little bit more stable! i need the 110w max so i reduced the oc overall 60/10/500

some algos will let my cards make some weird noises expecially X17
neoscrypt will close itself after couple minutes regardless of the settings..

should i try to adjust intensity settings or get the latest specific miner for the problem algos or just disable it for now ?

what would you recommend

back off intensity until you can run your cards at 120 watts

sirbrokealot

newbie

Activity: 18

Merit: 0

Quote from: millsys on January 05, 2018, 09:49:42 AM

Quote from: sirbrokealot on January 05, 2018, 08:15:56 AM

i have a lot of downtime with x17 and intensity 19, 20, 21 currently adjusted it to 17 ( ccminerAlexis78 )

im running 2x 1070ti strix a
@ 60% power +150 Core +600 Mem

anybody knows the reason for the miner to crash or not even get started`?

while mining phi ( CcminerTpruvotcuda9 ) it wont validate on my cpu ( this might be pool related? )
this occurs after reaching the peak hashrate

The Driver Versions differ from the 0 or 1 GPU
0 runs 388.71 WHQL [r388_43-17]
1 runs 388.71 WHQL [r388_43]
Both P2 State

i hope these are not stupid questions

Try 80% power/+100 core/+500 mem

thanks, i tried 80/100/500 it got a little bit more stable! i need the 110w max so i reduced the oc overall 60/10/500

some algos will let my cards make some weird noises expecially X17
neoscrypt will close itself after couple minutes regardless of the settings..

should i try to adjust intensity settings or get the latest specific miner for the problem algos or just disable it for now ?

what would you recommend

Chaob

newbie

Activity: 7

Merit: 0

Quote from: ?? on ??

I can't see the reason to remove any algos that you can run. The way that coin values and difficulties jump around you may make a few extra % on a couple of cycles out of the blue.

Between the time that you posted this and now I have run Tribus @ ahashpool on one of my machines for a cumulative hour.

Always test everything on your own rig, don't take my word for it. My own experience is that when my 8x 1080ti rig switches to it I get measly earnings post which are far, far less than other algos. I believe that the price of Tribus spikes which causes the miner to switch to it, then falls quickly so you end up mining a low payout coin for the duration of your switching time. That's what I encountered a few days ago, day by day these things change. For me it was best just to eliminate all but the coins with proven, reliable earnings.

minerx117

sr. member

Activity: 728

Merit: 256

NemosMiner-v3.8.1.3

Quote from: Bit2017User on January 05, 2018, 04:32:59 PM

Hello minerx117
Is it possible for you to add this pool https://www.unimining.net
Looks interesting and with low fees even if they are French Cheesy

Thanks

sorry no they do not support auto exchange to btc they only payout in the currency you are mining same as yiimp.eu

Bit2017User

jr. member

Activity: 76

Merit: 1

Hello minerx117
Is it possible for you to add this pool https://www.unimining.net
Looks interesting and with low fees even if they are French Cheesy

Thanks

Mike011

full member

Activity: 312

Merit: 104

Loading BTC rate from 'api.coinbase.com'..
Invoke-RestMethod : The remote server returned an error: (403) Forbidden.
At C:\Users\Master\Desktop\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], WebException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Anyone else getting this? Cant get the btc to dollar rate. Coinbase choking over Bitcoin price rising and increased traffic maybe?

millsys

member

Activity: 112

Merit: 10

Quote from: sirbrokealot on January 05, 2018, 08:15:56 AM

i have a lot of downtime with x17 and intensity 19, 20, 21 currently adjusted it to 17 ( ccminerAlexis78 )

im running 2x 1070ti strix a
@ 60% power +150 Core +600 Mem

anybody knows the reason for the miner to crash or not even get started`?

while mining phi ( CcminerTpruvotcuda9 ) it wont validate on my cpu ( this might be pool related? )
this occurs after reaching the peak hashrate

The Driver Versions differ from the 0 or 1 GPU
0 runs 388.71 WHQL [r388_43-17]
1 runs 388.71 WHQL [r388_43]
Both P2 State

i hope these are not stupid questions

Try 80% power/+100 core/+500 mem

restless

legendary

Activity: 1151

Merit: 1001

Quote from: restless on January 05, 2018, 04:33:57 AM

A friend of mine (who told me about this project) has a problem:
when running program on 8-card rigs, sometimes when mining program is to be switched , Nemo is killing the current miner - he gets "driver failed "error and then 1 of cards disappears
Any idea what might be the cause and cure?

I confirmed same fenomena - gracefully closing Alexis miner to driver crash and the card running main display disappears Sad

, need to restart
Even when making it manually with mouse

a possible workaround:

Code:

$_.Active += (Get-Date)-$_.Process.StartTime
$_.Process.CloseMainWindow() | Out-Null
Sleep 1
# if miner starts from Schedler, CloseMainWindow() is now enought, we have to force stop process by Id
Stop-Process $_.Process | Out-Null

to

Code:

$_.Active += (Get-Date)-$_.Process.StartTime
# simply "Kill with power"
Stop-Process $_.Process | Out-Null
Sleep 2

sirbrokealot

newbie

Activity: 18

Merit: 0

i have a lot of downtime with x17 and intensity 19, 20, 21 currently adjusted it to 17 ( ccminerAlexis78 )

im running 2x 1070ti strix a
@ 60% power +150 Core +600 Mem

anybody knows the reason for the miner to crash or not even get started`?

while mining phi ( CcminerTpruvotcuda9 ) it wont validate on my cpu ( this might be pool related? )
this occurs after reaching the peak hashrate

The Driver Versions differ from the 0 or 1 GPU
0 runs 388.71 WHQL [r388_43-17]
1 runs 388.71 WHQL [r388_43]
Both P2 State

i hope these are not stupid questions

ALTCOlNMlNER

newbie

Activity: 28

Merit: 0

Hey Nemo,

I registered extra to say thank you for all the hard work you do and constant developing your project! I will now donat 10 Minutes of my 6x gtx1070 rig for you.

Have a nice day!

Cheers!

restless

legendary

Activity: 1151

Merit: 1001

A friend of mine (who told me about this project) has a problem:
when running program on 8-card rigs, sometimes when mining program is to be switched , Nemo is killing the current miner - he gets "driver failed "error and then 1 of cards disappears
Any idea what might be the cause and cure?

the3dwizard

newbie

Activity: 17

Merit: 0

Quote from: skorpe on January 05, 2018, 01:47:43 AM

If I am running a rig with different Nvidia cards (multiple 1070ti, and an old 970 I have laying around), can I duplicate and rename the bat file and only direct it to the similar cards and run both simultaneously so that the benchmarks/profitability selections are independent? Is this something that people typically do or is the combined card benchmark close enough that the minor min max wouldn't be worth it.

thanks for the advice!

That is what I would do, let the cards run the algos they are best at. I am essentially doing that it is just my cards are in different rigs.

Cheers!

skorpe

newbie

Activity: 6

Merit: 0

If I am running a rig with different Nvidia cards (multiple 1070ti, and an old 970 I have laying around), can I duplicate and rename the bat file and only direct it to the similar cards and run both simultaneously so that the benchmarks/profitability selections are independent? Is this something that people typically do or is the combined card benchmark close enough that the minor min max wouldn't be worth it.

thanks for the advice!

BitBustah

hero member

Activity: 1218

Merit: 534

Quote from: Chaob on January 04, 2018, 05:50:39 PM

Tribus and Timetravel don't add up at all when my rigs switch to those and you see the petty earning amount on the website so I disabled those two on my 5 rigs. Test for yourself but pay close attention to those.

There was a time when Timetravel was the best algo. I guess you have to see whenever new coins are added to the algos..

drkCrix

newbie

Activity: 10

Merit: 0

Thanks Chaob Grin

Chaob

newbie

Activity: 7

Merit: 0

Quote from: drkCrix on January 04, 2018, 05:39:24 PM

Are you guys removing any algorithms from the batch files for ahash? Anything to steer clear from?

I have found x17, blake2s, phi, neoscrypt, xevan, skein, nist5 to give very reliable earning numbers.

Tribus and Timetravel don't add up at all when my rigs switch to those and you see the petty earning amount on the website so I disabled those two on my 5 rigs. Test for yourself but pay close attention to those.

drkCrix

newbie

Activity: 10

Merit: 0

Are you guys removing any algorithms from the batch files for ahash? Anything to steer clear from?

hogito

newbie

Activity: 31

Merit: 0

Quote from: fynxgloire on January 02, 2018, 09:35:23 AM

Quote from: jimmykl on January 02, 2018, 08:51:24 AM

Quote from: fynxgloire on January 02, 2018, 08:34:46 AM

Hi,
is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )

The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....

regards

Yes, quit Nemos, open the Stats folder and delete the relevant xxx_HashRate.txt file

e.g. to rebenchmark X17 delete the file called ccminerAlexis78_X17_HashRate.txt

Then you can extend the duration and it will only apply to the newly created benchmark

I restarted benchmarking all algorithms. When it got to the x11 benchmark and it initially showed 49 MH/s, then 30 minutes later it got up to 84.97 MH/s.
Then the benchmark ended, so I guess now I have to extend the benchmark for this algorithm to 1 hour since it never had the chance to get to the top speed.
That's kind of ridiculous.
Now Nemos miner shows the speed on top of the screen as 83.97 MH/s, but this is NOT the top speed since I am sure it would have kept going up even after 1/2 an hour.
Anyone else pay attention to this X-17 algorithm while benchmarking?

Similar but slight tangent, I added ethash to my algo list and it won't benchmark it. I cleared all benchmarks but still won't Sad

Anybody else have a similar issue?

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