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

apiontek

newbie

Activity: 19

Merit: 0

Quote from: dropky on March 27, 2018, 11:25:57 AM

Quote from: apiontek on March 27, 2018, 10:13:42 AM

I see no linux version, will there still be linux builds forthcoming?

Not that I'll be upgrading without standard stratum support (Not that Nicehash has any reason to care about that

).

But sometimes I choose to mine at Nicehash, and it'd be nice to use the latest version for that on linux.

(What would really get me to commit to Nicehash would be implementing lyra2z algorithm, but I realize that's not in the hands of excavator developers, and I've already given Nicehash Support my two cents on that.)

Yes, we'll release linux version shortly.

I'll see what I can do regarding the lyra2z.

Excellent, re: Linux versions.

For lyra2z I won't hold my breath, but it'd be sweet to be able to mine it at Nicehash. It's an excellent CPU algorithm so far, and frequently one of the highest earners at MiningPoolHub and a couple other pools, for both GPU and CPU. Better CPU earner than cryptonight, really.

dropky

jr. member

Activity: 132

Merit: 7

Quote from: apiontek on March 27, 2018, 10:13:42 AM

I see no linux version, will there still be linux builds forthcoming?

Not that I'll be upgrading without standard stratum support (Not that Nicehash has any reason to care about that

).

But sometimes I choose to mine at Nicehash, and it'd be nice to use the latest version for that on linux.

(What would really get me to commit to Nicehash would be implementing lyra2z algorithm, but I realize that's not in the hands of excavator developers, and I've already given Nicehash Support my two cents on that.)

Yes, we'll release linux version shortly.

I'll see what I can do regarding the lyra2z.

apiontek

newbie

Activity: 19

Merit: 0

I see no linux version, will there still be linux builds forthcoming?

Not that I'll be upgrading without standard stratum support (Not that Nicehash has any reason to care about that

).

But sometimes I choose to mine at Nicehash, and it'd be nice to use the latest version for that on linux.

(What would really get me to commit to Nicehash would be implementing lyra2z algorithm, but I realize that's not in the hands of excavator developers, and I've already given Nicehash Support my two cents on that.)

dropky

jr. member

Activity: 132

Merit: 7

@EvgeniyKorepov I answered you on GitHub

EvgeniyKorepov

newbie

Activity: 42

Merit: 0

Quote from: dropky on March 27, 2018, 04:53:18 AM

We released new version of excavator: https://github.com/nicehash/excavator/releases/tag/v1.5.0a

Changelog:

bug fixes & improvements
changed stratum protocol to NiceHash Miner Protocol
API version bumped to 0.1.0
added algorithm CryptoNightV7 (XMR)
speed improvements for CryptoNight
added support for Tesla P100

Additional notes:

From version 1.5.0a further excavator supports only NiceHash stratum servers. Stratum servers are available at:
nhmp.LOCATION.nicehash.com (LOCATION: eu, usa, hk, jp, in, br).
Excavator API has changed!
This version of Excavator is not compatible with NiceHash Miner (yet).

Config file example:

Code:

[
{"time":0,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.usa.nicehash.com:3200","34HKWdzLxWBduUfJE9JxaFhoXnfC6gmePG.testrig"]}
]},
{"time":2,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["equihash","0"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]

Config:
[
   {"time":1,"commands":[
      {"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","3DQ9fRMVfxHaTkxt2y8BBDnVb1eAad94NP.home"]}
   ]},
   {"time":2,"commands":[
      {"id":1,"method":"algorithm.add","params":["cryptonightV7"]}
]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["cryptonightV7","0"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"worker.print.speed","params":["0"]},
      {"id":1,"method":"algorithm.print.speeds","params":[]}
   ]}
]

Result:
[13:41:37][0x00003b58][info] Log started
[13:41:37][0x00003b58][info] core | Found CUDA device: GeForce GTX 960
[13:41:37][0x00003b58][info] api | Listening on 0.0.0.0:33333
[13:41:37][0x00003b58][info] http | Listening on 0.0.0.0:38080
[13:41:37][0x00003b58][info] core | Initialized!
[13:41:38][0x00003b58][info] Connected to nhmp.eu.nicehash.com:3200
[13:41:38][0x00000ab8][info] nhmp | Subscribed
[13:41:39][0x00003b58][info] nhmp | cryptonightV7 | add failure
[13:41:39][0x00003b58][info] nhmp | Reason: Internal server error (-1)
[13:41:40][0x00001224][info] wrkr0-0 | Algorithm: CUDA-cryptonightV7 parameters: B=14,TPB=32
[13:41:43][0x00003b58][info] nhmp | Disconnected
[13:41:43][0x00003b58][warning] nhmp | read: WebSocket connection closed normally

dropky

jr. member

Activity: 132

Merit: 7

Quote from: nitrobg on March 27, 2018, 05:03:34 AM

Quote from: dropky on March 27, 2018, 04:53:18 AM

From version 1.5.0a further excavator supports only NiceHash stratum servers.

Why?

We implemented our own stratum protocol (nhmp) to reduce the network traffic.

nitrobg

member

Activity: 413

Merit: 17

Quote from: dropky on March 27, 2018, 04:53:18 AM

From version 1.5.0a further excavator supports only NiceHash stratum servers.

Why?

dropky

jr. member

Activity: 132

Merit: 7

We released new version of excavator: https://github.com/nicehash/excavator/releases/tag/v1.5.0a

Changelog:

bug fixes & improvements
changed stratum protocol to NiceHash Miner Protocol
API version bumped to 0.1.0
added algorithm CryptoNightV7 (XMR)
speed improvements for CryptoNight
added support for Tesla P100

Additional notes:

From version 1.5.0a further excavator supports only NiceHash stratum servers. Stratum servers are available at:
nhmp.LOCATION.nicehash.com (LOCATION: eu, usa, hk, jp, in, br).
Excavator API has changed!
This version of Excavator is not compatible with NiceHash Miner (yet).

Config file example:

Code:

[
{"time":0,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.usa.nicehash.com:3200","34HKWdzLxWBduUfJE9JxaFhoXnfC6gmePG.testrig"]}
]},
{"time":2,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["equihash","0"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]

dj--alex

member

Activity: 81

Merit: 10

ok! thanks!
excavator -p 0 -c trezarcoin.json seems like works. shares present and showed in dashboard.

sOLVED!!!
TdBSh6BY2iU9uadNtDPXiXgMPMSaD4X5ac.rig1:x
waste 12 hours of mining to change it to
dj--alex.rig1:x

manual done. placed on TZC page
https://bitcointalksearch.org/topic/m.33112813

verge works.

Thanks all!

Really nice program)))

but Verge and trezarcoin is useless even on GTX 1080 .
Btg on ewbf is more effective

apiontek

newbie

Activity: 19

Merit: 0

Quote from: dj--alex on March 24, 2018, 04:11:18 AM

i fix but still error error
api | Failed to bind local port 3456 err: system:98

i run excavator from /home/username/excavator/ folder - it s empty and contain only scripts
on Linux i can run excavator from any folder.
it installed in system /opt/excavator/etc folder with right of root, normally user doen't have enough right to write conf files in /opt/
i tries today copy .json files.
it not helped. runs failed with "98"

i tries remove :x and rig1.not helped me.
{"id":1,"method":"algorithm.add","params":["lyra2rev2", "xvgmine.idcray.com:10011","D8C7HvMbxxTnZvwmzEv8jhGmWfi42woycr.rig1:x"]}
]}

i search over your link but i seek "port 3456" or "system:98"
but i found only "build_number": 3456, Sad

(((

totally unusable software ((

The error you're getting says the excavator api is unable to use port 3456 on your computer.

If you don't need to use the api, you can disable it with command line parameters as per https://github.com/nicehash/excavator#cmdline

So for example:

Code:

excavator -p 0 ...

For me it works, and I use the api in my mining scripts. Controlling excavator works differently from other mining software but it's great once you understand it.

Again, if you don't need the api and it's a roadblock for you, just disable it. If you want to use it, try setting a different port. Maybe port 3456 is already in use on your machine, or you don't have permission to use it.

dj--alex

member

Activity: 81

Merit: 10

i fix but still error error
api | Failed to bind local port 3456 err: system:98

i run excavator from /home/username/excavator/ folder - it s empty and contain only scripts
on Linux i can run excavator from any folder.
it installed in system /opt/excavator/etc folder with right of root, normally user doen't have enough right to write conf files in /opt/
i tries today copy .json files.
it not helped. runs failed with "98"

i tries remove :x and rig1.not helped me.
{"id":1,"method":"algorithm.add","params":["lyra2rev2", "xvgmine.idcray.com:10011","D8C7HvMbxxTnZvwmzEv8jhGmWfi42woycr.rig1:x"]}
]}

i search over your link but i seek "port 3456" or "system:98"
but i found only "build_number": 3456, Sad

(((

totally unusable software ((

dropky

jr. member

Activity: 132

Merit: 7

Quote from: dj--alex on March 23, 2018, 04:29:44 AM

I use excavator -c verge.json
I thinking do something wrong.

i thinking this is no password, most pools use password "x"
I got error
api | Failed to bind local port 3456 err: system:98

verge.json
[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["Lyra2rev2", "stratum+tcp://xvg-mine.idcray.com:10011","D8C7HvMbxxTnZvwmzEv8jhGmWfi42woycr.rig1:x","c=XVG d=20000"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"algorithm.print.speeds","params":[]}
   ]}
]

There are multiple mistakes in your algorithm.add method:
- change Lyra2rev2 to lyra2rev2, you have to use lower case
- stratum URL has to be without stratum+tcp:// prefix
- remove the fourth ("c=XVG d=20000") parameter, the method expects only 3 parameters (5 in case of dual mining)

Algorithm.add should be like this:

Code:

{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["lyra2rev2", "xvgmine.idcray.com:10011","D8C7HvMbxxTnZvwmzEv8jhGmWfi42woycr.rig1:x"]}
]}

Here is the documentation for the method - https://github.com/nicehash/excavator/tree/master/api#-algorithmadd.

dj--alex

member

Activity: 81

Merit: 10

I use excavator -c verge.json
I thinking do something wrong.

i thinking this is no password, most pools use password "x"
I got error
api | Failed to bind local port 3456 err: system:98

verge.json
[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["Lyra2rev2", "stratum+tcp://xvg-mine.idcray.com:10011","D8C7HvMbxxTnZvwmzEv8jhGmWfi42woycr.rig1:x","c=XVG d=20000"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"algorithm.print.speeds","params":[]}
   ]}
]

trezarcoin.json
[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["neoscrypt","stratum+tcp://pool.trezarcoin.com:6666","TdBSh6BY2iU9uadNtDPXiXgMPMSaD4X5ac.rig1","c=TZC d=20000"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"algorithm.print.speeds","params":[]}
   ]}
]

dropky

jr. member

Activity: 132

Merit: 7

Quote from: dj--alex on March 15, 2018, 01:30:32 PM

I read fifty times instructios.

Please help write .SH file for Linux to run excavator
(examples of .bat files )
I can run ewbf or claymore but i dont understand how to run Excavator.
i just tries write in console excavator and .... what keys and parameters i must write?

please give me a sample anybody
any sample/

I tries use random help from internet pages for cc miner, i not change keys.
if i change it - it will works, or i MUST use JSON?
excavator -a blake2s -o stratum+tcp://pool.unimining.net:5766 -u D8Z2APfnC68K461amMR6v4faaiCxWiY1rE -p c=XVG --cpu-priority=3

You can run excavator either using a start-up JSON file or HTTP API. Here is an example of the json file (to run blake2s on GPU-0):

Code:

[
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["blake2s", "pool.unimining.net:5766","username.workerName:password"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]

Save it to blake2s.json file and start excavator with the next command:
excavator -c blake2s.json

If you want to run excavator on more cards, you have to add more worker.add methods. For example, to run it on 4 GPUs you'll have to add 3 more workers, like this:

Code:

{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]},
   {"id":1,"method":"worker.add","params":["0","1"]},
   {"id":1,"method":"worker.add","params":["0","2"]},
   {"id":1,"method":"worker.add","params":["0","3"]}
]},

Please take another look at our GitHub repository - https://github.com/nicehash/excavator/#how-to-use-excavator
Here is another example of the config file: https://github.com/nicehash/excavator/blob/master/default_command_file.json
You should check the API docs as well - https://github.com/nicehash/excavator/tree/master/api#methods

dj--alex

member

Activity: 81

Merit: 10

I read fifty times instructios.

Please help write .SH file for Linux to run excavator
(examples of .bat files )
I can run ewbf or claymore but i dont understand how to run Excavator.
i just tries write in console excavator and .... what keys and parameters i must write?

please give me a sample anybody
any sample/

I tries use random help from internet pages for cc miner, i not change keys.
if i change it - it will works, or i MUST use JSON?
excavator -a blake2s -o stratum+tcp://pool.unimining.net:5766 -u D8Z2APfnC68K461amMR6v4faaiCxWiY1rE -p c=XVG --cpu-priority=3

dropky

jr. member

Activity: 132

Merit: 7

Quote from: uncarvedblockhead on March 13, 2018, 01:52:19 AM

@dropky - would appreciate any progress update you can share on upcoming equihash improvements? Thanks very much

We're working on it.. Hopefully there will be a new release with improved equihash shortly.

uncarvedblockhead

newbie

Activity: 2

Merit: 0

@dropky - would appreciate any progress update you can share on upcoming equihash improvements? Thanks very much

dropky

jr. member

Activity: 132

Merit: 7

Quote from: Khazouk on March 07, 2018, 08:27:23 AM

Thanks. Do you know why the profitability is low right now? Out of all algos, the best benchmark is showing up as DaggerPascal, yet it keeps dropping everyday. I'm at as low as 4.50 now a day lol

High difficulty & market crash.

dropky

jr. member

Activity: 132

Merit: 7

Quote from: proteus7 on March 06, 2018, 11:16:19 AM

Running it through awesome miner. There doesn’t seem to be any documentation on how the config file works, seems very confusing. I was just looking for a cli option like ccminer, claymore, etc all have to run on specific GPUs.

Quote from: dropky on March 06, 2018, 03:27:49 AM

Quote from: proteus7 on March 06, 2018, 02:18:02 AM

If I have a mixed rig with 6 similar cards (1080ti) and 1 different card (Tesla), how can I get Excavator to disable it, so that it can be used elsewhere? Trying to disable card 0 specifically.
There doesn't seem to be a command line option for this...

How are you running excavator? If you're using config file, just don't assign any workers for the specific card.

Check the comment above - https://bitcointalksearch.org/topic/m.31712321.

It's quite simple actually, you have to run excavator with -c config_file_name.json parameter.

Here is an example of the config file:

Code:

[
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash","equihash.usa.nicehash.com:3357","btc_addr"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","1"]},
{"id":1,"method":"worker.add","params":["0","2"]},
{"id":1,"method":"worker.add","params":["0","3"]},
{"id":1,"method":"worker.add","params":["0","4"]},
{"id":1,"method":"worker.add","params":["0","5"]},
{"id":1,"method":"worker.add","params":["0","6"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]

You have to add worker for each GPU (in your case - running on 6 gpus, excluding the gpu 0).

Khazouk

newbie

Activity: 3

Merit: 0

Quote from: dropky on March 07, 2018, 01:13:50 AM

Quote from: Khazouk on March 06, 2018, 10:33:24 AM

Thank you Dropky!
I have Zotac 2 1070 and 1 1060. I did overclock the cards and getting only 5.75 usd on them/day
Is there something I am missing here?

Here are the links of the pictures to my card :

https://ibb.co/nCw9q7 1060 Zotac 6GB
https://ibb.co/eAvr3S 1070 Zotac 8GB

Actually, I think your profit is as good as it currently can get, the profitability is quite low right now. Depends on what your mining most of the time, if it's daggerhashimoto you could increase the memory clock on your 1060 for a bit (be careful with increasing overclocking though, make sure that everything is still stable, if not just revert the settings).

Thanks. Do you know why the profitability is low right now? Out of all algos, the best benchmark is showing up as DaggerPascal, yet it keeps dropping everyday. I'm at as low as 4.50 now a day lol

Topic: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a] - page 4. (Read 179296 times)