 Show Posts
|
|
Pages: [1]
|
|
Happy to get my rigs back on Zerg!
Seems a lot of miners are coming back pretty quick too!
|
|
|
|
Well according to my .log, it's occurring between the Comparing miners and pools.. and Launching Prerun: stage during a cycle. Since those status strings show up in Core.ps1, maybe the problem lies within there? Starting Cycle
Loading BTC rate from 'api.coinbase.com'..
Loading pool stats..
Computing pool stats..
Loading miners..
Comparing miners and pools..
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
closing current miner and switching
Launching Prerun: .\Prerun\default.bat
Starting miner I also noticed this error occuring in the CoreCycle.log: This error repeats quite a few times in the log. + CategoryInfo : NotSpecified: (:) [], SetValueInvocationException
+ FullyQualifiedErrorId : ScriptSetValueRuntimeException
Exception setting "StatusText": "The 'Add-Member' command was found in the module 'Microsoft.PowerShell.Utility', but
the module could not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.Utility'."
At D:\Mining\NemosMiner-v3.5.1\Core.ps1:171 char:4
+ $Variables.StatusText = "! Error contacting pool retrying ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], SetValueInvocationException
+ FullyQualifiedErrorId : ScriptSetValueRuntimeException Since you think it may be pool-based, maybe it errors out when the pool cant be reached for a moment? I'm using standard zpool. Nemo says he uses Nicehash and Zpool24hr: https://bitcointalk.org/index.php?topic=1777336.msg47377248#msg47377248Just throwing out some information to hopefully help you or whoever solve the issues! |
|
|
|
Looks like release 3.5.5 broke it for me. I just got a crash but in another place and a different error (not the one I patched). This time it's a "You cannot call a method on a null-valued expression".
I'll dig into it.
I had that one a while back: https://bitcointalk.org/index.php?topic=1777336.msg46856313#msg46856313Increasing the interval (mines at 900 / 15 mins) pretty much stopped that crash for me, but it the error still exists. I don't understand code well enough to solve this one myself, but if you check the Logs\miner.log you can see repeated PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression." errors on every cycle. And in terms of updating, I've been running Nemo's for over a year now. Version 3.0 was the most stable release for me so I used it until it became too outdated to keep updated when the GUI changed. The way I do it now, since Nemo's is a pretty modular package, is I update selective parts from github that I feel are necessary or are significant improvements instead of moving to a fresh release every time. This has let me keep my rigs up longer and troubleshoot much less!  Edit: And look what I just got... https://i.imgur.com/FuVfRWU.jpg |
|
|
|
Don't forget to close down and restart the miner!
Of course! Had everything closed while I made the edit. It has ran all day without a hitch since. Still too soon to called it fixed as I've had many days without crashes before making the edit, but it looks promising so far. Thanks again!  |
|
|
|
^ @InfiniteImp Thanks for sharing! I'm giving it a test on one of my rigs right now. Let's hope it does the trick! |
|
|
|
^ Happens on all 3 of my machines at random times. Can't figure out what causes it. Seems to occur during a "cycle" so I increased the interval which helped decrease the amount of times it errors. Luckily it continues to mine at least, but it won't profit switch when the error happens. I just monitor my machines a few times a day and restart nemos when I see the error.  |
|
|
|
|
Will there be a CUDA 9.1 version of CryptoDredge v0.10.0?
Past couple of release have not had CUDA 9.1 now.
|
|
|
|
|
cs@blazepool,
I want to try your pool but I am a small miner and your pool has one of the higher payout thresholds. It would be more inviting for people wanting to try your pool if the threshold could be reduced a little. Most pools have a 0.0025 BTC minimum and some an even smaller a weekly payout, which is great for a small miner.
|
|
|
|
Blaze + Zpool. Std option. ActiveMinerGain% set to 10 percent, 900 second interval.
I'll have to give that a try. Thanks for the info. |
|
|
|
Simple fix. 1) dont use the magic and fairy farts 'plus' options 2) dont use ahashpool. Plus option is based on faulty logic... that past performance is indicative of future gains. UNLESS you have a mining farm if you go against the pool's flow you will loose (ie your hashing power on XYZ will not overcome everyone else on a dif alog. this happens all the time on plus option. everyone else moves to a dif alog and you are almost solely mining for awhile)... and Ahashpool... well... it blows. Too small a pool with too few coins.
What pool are you running now that Zerg is gone? Since you don’t like the Plus option, do you use standard pool or 24hr? |
|
|
|
i don't know i don't get that error.. all my rigs are running v3.5 release they auto restart every 24hours i get no errors at all... i have multiple rigs ranging from 1060's to 2080's.
cant help you sorry..
no spam please
Seems the issue is related to bminer.ps1. It was giving a lot of errors in CoreCycle.log. Got the updated one from the latest master and the errors stopped. Been running for 20 hours now and haven’t had any script errors since. I usually ran blaze with zerg as a backup (usually w/ a .90 in poolconfig json file). With zerg MIA the question becomes: blaze vs nlpool vs blockmasters? Which would you use for your rigs? Dont like zpool. Nothing against them persay... just their stats are always WAY off what they claim them to be. Last time I tried zpool had to set .83 to get remotely close to realistic stats.
I’m currently giving Blockmasters a try. Seems like a promising pool. Haven’t been using them long enough to give any sort of review though. |
|
|
|
|
minerx117,
I'm am running the new NemosMiner-v3.5 release and after a random amount of time the script will give me a debug error "You cannot call a method on a null-valued expression" and a huge excepUI.txt file is created in the logs folder. This seems to happen when a cycle is started and doesn't complete or something.
I was able to run for 10 hours before it happened. Another time it happened in only 1 hour.
Running Win10. How can I fix this?
|
|
|
|
Hello,
With zergpool stopping their pool, you have an opportunity to attract a lot of miner if you set up some algos like equihash variation (92,144,192), bcd, sonoa... Those algos were very profitable for a lot of people...
I'll second this. BlockMasters has a very nice opportunity here. I'm a Zergpool refugee and I'm looking for a new pool. Basically the only real alternative right now is Zpool, with BlockMasters as a close second imo. Zpool offers more with higher fees and BlockMasters offers less with lower fees. If BlockMasters can offer more algos while maintaining the lower fees, you could have a very competitive pool bringing in a lot of miners. I'd like to see a smaller pool like BM succeed and be competitive against the big pools like Zpool. |
|
|
|
yes we could do that, i personally only use 1 pool it was zergpool.. now im back on zpool.. (a backup pool is a good idea thankyou)
Regards
Nemo
Zerg was my main pool too. Not sure where to go now. I’m thinking BlockMasters or Zpool. Even though they offer less algos and coins, Nemos is showing better profit estimates on BlockMasters so far. |
|
|
|
Very sad to see the pool shutting down. I just wanted to say thank you to Pinpins and everyone else involved for the hard work and dedication you’ve put into this project. I’ve been using the pool almost since inception and I never experienced any major issues or felt cheated out of any earnings. It’s been a good run. Good luck in your future endeavors. |
|
|
|
First test :
I got the same error too Also got the same error while benchmarking on a fresh install of 3.3. Returning to previous version of Nemos for now. |
|
|
|
I have to add that the GPU monitor stops running after several hours, it just closes without apparent reason.
This happens to me too. I tried to make the .bat restart itself if the monitor closes with Windows Task Scheduler, but I can't seem to make it work properly. |
|
|
|
Version 3.0 of Nemo's is working great for me and my rigs. However I was wondering if it was possible to change the payment threshold and earnings currency. I am using Zergpool's LTC payout method, but NemosMiner shows the standard BTC payout threshold and BTC/D. I would like to set the payout threshold to Zergpool's LTC threshold (0.25 LTC and 0.05 LTC on Sunday) and see my earnings reported in LTC/D instead. I tried to change the numbers in poolapiref.json, but it seems like the file is rewritten automatically. If this is a lot of work, maybe it could be considered a feature request for a future update. Thank you minerx117 and MrPlus for your awesome work on this project. |
|
|
|
|
