excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a]

[lexkanev]

EXCAVATOR BENCHMARKS--

After installing Excavator on my Linux rig (instructions at the GitHub site), I ran the bencmark script.  Here are the results:

Excavator Version: v1.3.8a_nvidia                                                                                                                                                                                                                  
OS: Ubuntu 14.04.5 LTS                                                                                                                                                                                                                              
NVIDIA Driver Version: 384.90                                                                                                                                                                                                                      
Found 3 device(s):                                                                                                                                                                                                                                  
GeForce GTX 1070 Ti                                                                                                                                                                                                                                
GeForce GTX 980 Ti                                                                                                                                                                                                                                  
GeForce GTX 980 Ti                                                                                                                                                                                                                                  
Benchmarking with 3 device(s) for 300 seconds for each algorithm...                                                                                                                                                                                
Benchmarking without network connection first...                                                                                                                                                                                                    
equihash: 1.412996 kH/s
pascal: 3.140780 GH/s                                                                                                                                                                                                                              
decred: 8.864810 GH/s                                                                                                                                                                                                                              
sia: 5.674955 GH/s                                                                                                                                                                                                                                  
lbry: 837.269673 MH/s                                                                                                                                                                                                                              
blake2s: 12.842469 GH/s
lyra2rev2: 119.783266 MH/s                                                                                                                                                                                                                          
cryptonight: 1.569471 kH/s                                                                                                                                                                                                                          
daggerhashimoto: 70.255890 MH/s
daggerhashimoto_pascal: 52.603532 MH/s & 2.006996 GH/s                                                                                                                                                                                              
daggerhashimoto_decred: 67.375154 MH/s & 2.927411 GH/s
daggerhashimoto_sia: 68.533263 MH/s & 1.346579 GH/s                                                                                                                                                                                                
Benchmarking with 3 device(s) for 300 seconds for each algorithm...                                                                                                                                                                                
Connectng to usa.nicehash.com...                                                                                                                                                                                                                    
equihash: 1.408922 kH/s (50 acceped, 0 rejected)                                                                                                                                                                                                    
pascal: 2.084523 GH/s (38 acceped, 0 rejected)                                                                                                                                                                                                      
decred: 8.870751 GH/s (124 acceped, 0 rejected)                                                                                                                                                                                                    
sia: 5.676765 GH/s (102 acceped, 0 rejected)                                                                                                                                                                                                        
lbry: 837.882124 MH/s (97 acceped, 0 rejected)                                                                                                                                                                                                      
blake2s: 12.825668 GH/s (194 acceped, 0 rejected)                                                                                                                                                                                                  
lyra2rev2: 119.710346 MH/s (66 acceped, 0 rejected)                                                                                                                                                                                                
cryptonight: 1.536833 kH/s (2 acceped, 1 rejected)                                                                                                                                                                                                  
daggerhashimoto: 52.099698 MH/s (12 acceped, 0 rejected)                                                                                                                                                                                            
daggerhashimoto_pascal: 49.025702 MH/s & 1.836451 GH/s (82 acceped, 1 rejected)                                                                                                                                                                    
daggerhashimoto_decred: 47.552451 MH/s & 2.268395 GH/s (42 acceped, 0 rejected)                                                                                                                                                                    
daggerhashimoto_sia: 50.623493 MH/s & 1.102006 GH/s (32 acceped, 0 rejected)

Things to note!  I had difficulty breaking out of the benchmark process with "control-c" and had to reboot to stop the process.  The word "accepted" is spelled wrong.  The process took more than 2 hours, 22 benchmarks at 300 seconds each.  Neoscrypt is not included in the benchmarks.  My 1070ti is slightly faster than my 980ti cards, at about 1/2 the wattage.     --scryptr

Hi!

I tested of lyra2rev2 algo with 1.3.4a, 1.3.7a and 1.3.8a on Ubuntu 16.04 and had this results: 26-27 MH/s, 22-23 MH/s, 22-23 MH/s.
I think it is not normal. GPU - P106-100 (Palit GTX 1060 6Gb).
Monero has a worse result too on new versions.

[JNXD]

So i just got this miner for myself, so pretty noob still with it. I have 2 GPU's and i would want to mine with only my secondary one from time to time, how do i do it?

[SUB750T]

Hi All,

How do I make excavator work with p2pool, or what I need to change in the pool to make excavator to work> CC Miner works fine  but has slightly lower hash rate.

I'm getting  "error" not expected type: Array

[23:20:00][0x00004010][info] Log started
[23:20:00][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Initialized!
[23:20:02][0x00003948][info] net | Connecting to 127.0.0.1:9171 (127.0.0.1)
[23:20:02][0x00002078][info] net | Connected!
[23:20:02][0x00003948][warning] net | Net error: JSON member "error" not expected type: Array
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"

Thanks!

[lexkanev]

Hi!

Now in 1.3.8a version on Ubuntu 16.04 I get an error about 1-2 days after start mining and Excavator stops working:

rig03 kernel: [77113.327260] show_signal_msg: 18 callbacks suppressed
rig03 kernel: [77113.327270] excavator[32683]: segfault at 0 ip 00007fa7c52e2c29 sp 00007fa7c20d1b98 er$
rig03 start.sh[32653]: Segmentation fault (core dumped)
rig03 systemd[1]: exc.service: Main process exited, code=exited, status=139/n/a
rig03 systemd[1]: exc.service: Unit entered failed state.
rig03 systemd[1]: exc.service: Failed with result 'exit-code'.

I'll try 1.3.7a and I'll write results late.

[Kayfolom]

Hi All,

How do I make excavator work with p2pool, or what I need to change in the pool to make excavator to work> CC Miner works fine  but has slightly lower hash rate.

I'm getting  "error" not expected type: Array

[23:20:00][0x00004010][info] Log started
[23:20:00][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Initialized!
[23:20:02][0x00003948][info] net | Connecting to 127.0.0.1:9171 (127.0.0.1)
[23:20:02][0x00002078][info] net | Connected!
[23:20:02][0x00003948][warning] net | Net error: JSON member "error" not expected type: Array
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"

Thanks!

Here are the specifications of the protocol stratum, the pool should support them https://github.com/nicehash/Specifications

[Kayfolom]

ExcavatorMonitor

Windows
https://github.com/Kayfolom/ExcavatorMonitor/releases/tag/1.0.9.0

Android
https://play.google.com/store/apps/details?id=ru.flintnet.ExcavatorMonitor

[black91]

Hi All,

How do I make excavator work with p2pool, or what I need to change in the pool to make excavator to work> CC Miner works fine  but has slightly lower hash rate.

I'm getting  "error" not expected type: Array

[23:20:00][0x00004010][info] Log started
[23:20:00][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Initialized!
[23:20:02][0x00003948][info] net | Connecting to 127.0.0.1:9171 (127.0.0.1)
[23:20:02][0x00002078][info] net | Connected!
[23:20:02][0x00003948][warning] net | Net error: JSON member "error" not expected type: Array
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"

Thanks!

Here are the specifications of the protocol stratum, the pool should support them https://github.com/nicehash/Specifications

is there any single page where I can learn to create a mining pool? Recently tried and couldn't find a one-stop solution?

[Trimegistus]

is there any single page where I can learn to create a mining pool? Recently tried and couldn't find a one-stop solution?

There are many guides online, including YouTube. This is not the proper thread for that kind of request.

[SUB750T]

Hi All,

How do I make excavator work with p2pool, or what I need to change in the pool to make excavator to work> CC Miner works fine  but has slightly lower hash rate.

I'm getting  "error" not expected type: Array

[23:20:00][0x00004010][info] Log started
[23:20:00][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Initialized!
[23:20:02][0x00003948][info] net | Connecting to 127.0.0.1:9171 (127.0.0.1)
[23:20:02][0x00002078][info] net | Connected!
[23:20:02][0x00003948][warning] net | Net error: JSON member "error" not expected type: Array
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"

Thanks!

Here are the specifications of the protocol stratum, the pool should support them https://github.com/nicehash/Specifications

So I installed the pool and I can mine using one click miner or cc miner. Where should I look and what to change to have excavator working with it? Is there a pool configuration ( and where) that needs to be tweeked?

[lexkanev]

Hi!

Now in 1.3.8a version on Ubuntu 16.04 I get an error about 1-2 days after start mining and Excavator stops working:

rig03 kernel: [77113.327260] show_signal_msg: 18 callbacks suppressed
rig03 kernel: [77113.327270] excavator[32683]: segfault at 0 ip 00007fa7c52e2c29 sp 00007fa7c20d1b98 er$
rig03 start.sh[32653]: Segmentation fault (core dumped)
rig03 systemd[1]: exc.service: Main process exited, code=exited, status=139/n/a
rig03 systemd[1]: exc.service: Unit entered failed state.
rig03 systemd[1]: exc.service: Failed with result 'exit-code'.

I'll try 1.3.7a and I'll write results late.

I had test 1.3.7a and after some time got an error in syslog and stoping mining:

rig04 start.sh[1183]: #033[0m#033[40m[15:32:49][0x00007f064a4fd700][info] #033[38;5;87mcore | Algorithm 'equihash' total speed: 3.525743 kH/s
rig04 kernel: [313941.139024] show_signal_msg: 21 callbacks suppressed
rig04 kernel: [313941.139028] excavator[1709]: segfault at 0 ip 00007f064d70dbe9 sp 00007f064a4fcb98 error 4 in libstdc++.so.6.0.21[7f064d669000+172000]
rig04 systemd[1]: Stopping NVIDIA Persistence Daemon...
rig04 nvidia-persistenced: Received signal 15
rig04 nvidia-persistenced: Socket closed.
rig04 nvidia-persistenced: PID file unlocked.
rig04 nvidia-persistenced: PID file closed.
rig04 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced
rig04 nvidia-persistenced: Shutdown (1312)
rig04 systemd[1]: Stopped NVIDIA Persistence Daemon.
rig04 start.sh[1183]: Segmentation fault (core dumped)
rig04 systemd[1]: exc.service: Main process exited, code=exited, status=139/n/a
rig04 systemd[1]: exc.service: Unit entered failed state.
rig04 systemd[1]: exc.service: Failed with result 'exit-code'.

Now I'll try upgrade system to the last and I'll test again with 1.3.7a.

[MarkAz]

First off, good job on Excavator, I really find it super easy to use - both on Windows and Linux.

One note on your linux distribution, it doesn't include the /web/index file that you do with the Windows, but if you put it in the same directory as where you run excavator from, it works fine.  It took me a couple of attempts to figure out where it wanted the web folder, I wish that when you cranked up the messages with -d 0 that it would give full paths on failures so you could see where it was looking.

My main question is this - I've used it with a couple pools, such as Nicehash and ZPool without issue, but when I try to use it with MiningPoolHub, it doesn't ever seem to connect - and at the same time it doesn't seem to have any additional error messages for me to figure out what isn't correct (even with -d 0).  Any insight on this, an example of using this pool, or steps to try to debug what's going on?

Thanks again!

[Florin Andrei]

I'm having trouble using Excavator to mine Pascal Coin on Nanopool. The miner launches, detects the card, but doesn't seem to do anything.

Code:

$ excavator -a pascal -s pasc-us-west1.nanopool.org:15555 -u ${addr}.0.${worker}/${mail} -d 0 -ca

=========================== www.nicehash.com =========================
                Excavator v1.3.1a_nvidia GPU Miner for NiceHash.
           Copyright (C) 2017 NiceHash. All rights reserved.
    Developed by djeZo, zawawa, dropky and voidstar with help and
   contributions from pallas, Vorksholk, bitbandi, ocminer, Genoil.
=========================== www.nicehash.com =========================

Build time: N/A
Build number: 0
[17:49:43][0x00007f78c50a2740][info] Log started
[17:49:44][0x00007f78c50a2740][debug] nvidia | Failed connecting to X server
[17:49:44][0x00007f78c50a2740][info] core | Found CUDA device: GeForce GTX 1060 6GB
[17:49:44][0x00007f78c50a2740][info] api | Listening on 127.0.0.1:3456
[17:49:44][0x00007f78c50a2740][info] core | Initialized!

I get the exact same behavior on Windows 10 and Linux (Ubuntu 16.04). What am I doing wrong?

[sir_blacks]

I'm having trouble using Excavator to mine Pascal Coin on Nanopool. The miner launches, detects the card, but doesn't seem to do anything.

Code:

$ excavator -a pascal -s pasc-us-west1.nanopool.org:15555 -u ${addr}.0.${worker}/${mail} -d 0 -ca

I get the exact same behavior on Windows 10 and Linux (Ubuntu 16.04). What am I doing wrong?

1. you need to edit / create a new json file for each algo what you want to use for be organize
start editing default_command_file.json & rename it for algo like pasc.nanopool.json

2. after create your json edit excavator+web+restart_script.bat file & 3'rd line it suppose to look like this:
SET COMMAND_FILE=pasc.nanopool.json then you are ready to mine

3. corect is wallet(user).worker:pass or wallet.worker:email not wallet.worker/email

cheers

[sir_blacks]

First off, good job on Excavator, I really find it super easy to use - both on Windows and Linux.

One note on your linux distribution, it doesn't include the /web/index file that you do with the Windows, but if you put it in the same directory as where you run excavator from, it works fine.  It took me a couple of attempts to figure out where it wanted the web folder, I wish that when you cranked up the messages with -d 0 that it would give full paths on failures so you could see where it was looking.

My main question is this - I've used it with a couple pools, such as Nicehash and ZPool without issue, but when I try to use it with MiningPoolHub, it doesn't ever seem to connect - and at the same time it doesn't seem to have any additional error messages for me to figure out what isn't correct (even with -d 0).  Any insight on this, an example of using this pool, or steps to try to debug what's going on?

Thanks again!

about MiningPoolHub from what i undestend from treath pool page Excavator it have block that pool by dev look on last page

as far as i knw excavator you are using was develop by nicehash. As they developed it they will lock it up only to be used for their pool. Greedy nicehash is to blame. It is best that we as miners exercise due diligence.

yes excavator was & it is dev by ppls what was & work for nicehash, but that not means is working only on they'r pool if you was read what i was write is working perfectly on Nano, Supernova, zpool or on any other ... only on here is not but if admin of pool decide to ban a miner apps is his decision

NiceHash blocked MiningPoolHub on Excavator.

aaronsace  sorry from first your affirmation i was undestend other way aka excavator is block by pool ... now you say dev from excavator was block this pool ? errr never mind i get headhake    i will move on > that is not working here < fine fine i will keep simple

way or if is true i not know ze point is Excavator it not mine on that pool

[MarkAz]

about MiningPoolHub from what i undestend from treath pool page Excavator it have block that pool by dev look on last page

way or if is true i not know ze point is Excavator it not mine on that pool

Wow, very interesting - I roamed around a bit in the executable, and sure enough it mentioned "miningpoolhub" explicitly, but no other pools, so that would lend some credence to that.  I wouldn't be surprised if they really don't care if it connects to other POOLS, but they do care about it connecting to multi-pools with auto BTC conversion - since that's exactly what Nicehash does.  I certainly wouldn't have an issue with that, but it would be nice if it was spelled out in the docs so I didn't waste time trying to get it working.

Thanks for the heads up!

[Kayfolom]

For miningpoolhub pools - resolve domain name to IP, and insert to Excavator json config - Profit!

[MarkAz]

For miningpoolhub pools - resolve domain name to IP, and insert to Excavator json config - Profit!

I suspect it's more than that - as that would be a pretty trivial bypass.  I wouldn't be surprised of some part of the Stratum protocol probably includes some host field and that's what it's working off of.

[Kayfolom]

For miningpoolhub pools - resolve domain name to IP, and insert to Excavator json config - Profit!

I suspect it's more than that - as that would be a pretty trivial bypass.  I wouldn't be surprised of some part of the Stratum protocol probably includes some host field and that's what it's working off of.

Excavator (3 rigs) works on the pool https://monacoin.miningpoolhub.com for a week without problems.
instead
{"id":1,"method":"algorithm.add","params":["lyra2rev2","hub.miningpoolhub.com:20593","***********"]}
use
{"id":1,"method":"algorithm.add","params":["lyra2rev2","52.6.227.167:20593","***********"]}

[malthrax]

For miningpoolhub pools - resolve domain name to IP, and insert to Excavator json config - Profit!

I suspect it's more than that - as that would be a pretty trivial bypass.  I wouldn't be surprised of some part of the Stratum protocol probably includes some host field and that's what it's working off of.

You may suspect that, but did you try it?  You might be surprised.

[sir_blacks]

For miningpoolhub pools - resolve domain name to IP, and insert to Excavator json config - Profit!

I suspect it's more than that - as that would be a pretty trivial bypass.  I wouldn't be surprised of some part of the Stratum protocol probably includes some host field and that's what it's working off of.

You may suspect that, but did you try it?  You might be surprised.

yes i was try replace named adress with IP & yes it wroking BUT is more about trivial bypass, coz invalid share it will be many aka let give you a expample > Your Invalid: 676.0354 (26.58%) for equihash algo on one rownd, it was not a problem if was 1-2% but 25% to much. I any other pool invalid share are 0 or max 1% soo my conclusion is yes is more that trivial bypass special if i run other miner like dstm 0% bad share or EWBF

anyway for me is clear excavator & miningpoolhub not work togheter = https://github.com/nicehash/excavator/issues/51