New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verthash errors when not even mining Verthash #1388
Comments
If you have MiningRigRentals activated, Verthash miner will automatically download the full 1.2GB verhash.dat in the background. Verthash is currently pretty profitable on MMR. That warning should disappear after the download has finished. Good, that you have unlimited internet. Sorry for the inconvenience. I should have integrated an extra switch. |
I'm having a somewhat similar problem. I have "EnableAutoAlgorithmAdd": "1" set and upon startup got the message about it downloading verthash.dat. However, it seems like nothing is being downloaded. The Downloads folder doesn't have anything related to verthash.dat. or verthash. The config confirms that the algo Verthash has not been added. If I manually add it, then the downloads begin. |
I'll double check - I think, I just remember, that we have an "InfoOnly" call to the miners at the beginning. That could throw that warning message, but don't start the download. |
- dont't warn of donwload, if InfoOnly call to miner (issue #1388)
@jch9678 that warning during startup is now removed. |
@paulpoco VTC (Verthash) is on Zergpool, as well. So that could have triggered the download as well. I am thinking about adding a special switch, regarding that miner, so that a download of the verthash.dat is not on the plan automatically. |
Thanks. Still having problem with Verthash not being auto added to the config file. |
Oh, I forgot to add it the Cleanup script. |
- add Autolykos2 and VertHash to add algorithms (issue #1388)
Will a benchmark fail if it the miner points to the wrong port? Verthash is failing to benchmark I think because it needs to point to 20534 and it's pointing to 17xxx port at miningpoolhub. Or should it try another pool, that might be way too cumbersome though. If the miner actually does fail but it tries every pool a coin could be mined at, that would way too much downtime. |
If possible could you please provide a hotfix ps1 I can just drop into my folder to fix miningpoolhub |
Sure, download the following zip file and extract the both ps1 files into the Pools folder: |
Thank You! |
hmmm It's still trying to use the 17032 port |
Also just testing in a standalone verthash mining folder to confirm ports, I've found another issue. When we specify --cl-devices 0,1,2,3,4,5 this miner tries to use the onboard graphics. It fails to create the buffer but in this case only 5 of 6 gpu's are activated. I have to use --cl-devices 0,1,2,3,4,5,6 in order to get all 6 cards working. But I can confirm it mines correctly at miningpoolhub with port 20534 and using --cl-devices 0,1,2,3,4,5,6 for 6 cards. |
Oh dear! This miner does have some problems. Could you please run Gputest.bat (or gputest.sh) and upload your gputestresult.txt here? |
The 17032 port is the autoexchange port, used by the MiningPoolHub module - the 20534 port is the direct mining port. If you want to use it, use the MiningPoolHubCoins module instead of the MiningPoolHub. |
- move warning message from miner module to downloader, so that you will no longer get that annoying warning message, even if you don't mine VTC (issue #1388)
I couldn't get it to work 17032. I use both modules, should I not be doing that? I think the 17xxx ports are just for algo switching, not auto exchange
|
Unfortunately I have to run now. I should be able to provide the gputest.bat in a few hours. Sorry. |
No problem. Thank you in advance! |
Yes, you should use only one. Either MiningPoolHub, which will make use of the 17xxx ports and do algo switching. Or MiningPoolHubCoins, which mines the most profitable coin, using the 20xxx ports |
- temp. disable VTC, port 17032 isn't working (issue #1388)
It is F'ing up my systems alway trying to download some 1.25GB file. Not using MRR. Not using Verthash. Not using MiningPoolHub. Will just add verthash to not use at all |
.. this is a bug - I will push a new release (almost ready). Actually, it's just a warning message - there shouldn't be a download, then. |
Only using Ethermine. |
Yes, it's a rogue warning message, only. If no pool with Verthash - then there is no download. Just ignore the warning for now. I'll have the fix ready very soon. |
- final fix to get rid of the annoying "Downloading verhash.dat" warning (issue #1388)
Ok, done. Sorry for the inconvenience! |
Could you also open http://localhost:4000/alldevices in your browser and post the resulting JSON data? Thanks a lot in advance! |
- hopefully fix AMD device selection (issue #1388)
|
4.6.8.4 almost works. 1 - it didn't seem to obey Show Miner Window 2 - my 6th card didn't activate |
addition to the above. I changed my config to exclude MiningPoolHub (use MiningPoolHubCoins instead) and RM benchmarked at zergpool. I then excluded zergpool for the below reasons, and RM acts like Verthash is not available at MiningPoolHubCoins. Do you happen to know what fee Verthash Miner uses? I used it at zergpool before it was implemented in RM and received about 1/3 less coins than calculated by minerstat. |
The miner is open source - there is no fee. I have just read through the code - I think I now know, how to address the AMD GPUs. Will push another update soon. It is intended, that the miner is not running in it's own window. It needs a wrapper due to the fact, that it hasn't an API. |
The chain's difficulty is pretty high, so it is very well possible that a pool with low hashrate fails to deliver. |
- AMD: use enumeration of devices, sorted by PCI bus id, thus including any Intel onboard (should solve issue #1388)
I am not mining verthash but I keep seeing a message downloading verthash.dat every now and then. On the Server machine window.
On one of the clients I am getting something about verthash error on the main window pointing some line of code.
Edit: I'll have to catch full error but it said line 74
Edit2: the error on the server says this verthash.dat is 1.5GB it keeps trying to download, good thing my internet is unlimited.
The text was updated successfully, but these errors were encountered: