Code Monkey home page Code Monkey logo

meta-miner's Introduction

meta-miner

Meta Miner: allows to add algo switching support to any stratum miner.

Does not add any extra mining fees.

Check mm.js builtin help

Usage: mm.js [<config_file.json>] [options]
Adding algo switching support to *any* stratum miner
<config_file.json> is file name of config file to load before parsing options (mm.json by default)
Config file and options should define at least one pool and miner:
Options:
        --pool=<pool> (-p):             <pool> is in pool_address:pool_port format, where pool_port can be <port_number> or ssl<port_number>
        --host=<hostname>:              defines host that will be used for miner connections (localhost 127.0.0.1 by default)
        --port=<number>:                defines port that will be used for miner connections (3333 by default)
        --user=<wallet> (-u):           <wallet> to use as pool user login (will be taken from the first miner otherwise)
        --pass=<miner_id>:              <miner_id> to use as pool pass login (will be taken from the first miner otherwise)
        --perf_<algo>=<hashrate>        Sets hashrate for algo that is: rx/0, rx/wow, cn/r, cn-pico/trtl, cn-heavy/xhv, cn/gpu, argon2/chukwa, k12, c29s, c29v, c29b, kawpow, ethash, autolykos2, panthera, ghostrider
        --algo_min_time=<seconds>       Sets <seconds> minimum time pool should keep our miner on one algo (0 default, set higher for starting miners)
        --miner=<command_line> (-m):    <command_line> to start smart miner that can report algo itself
        --<algo>=<command_line>:        <command_line> to start miner for <algo> that can not report it itself
        --watchdog=<seconds> (-w):      restart miner if is does not submit work for <seconds> (600 by default, 0 to disable)
        --hashrate_watchdog=<percent>:  restart miner if is hashrate dropped below <percent> value of of its expected hashrate (0 by default to disable)
        --miner_stdin:                  enables stdin (input) in miner
        --quiet (-q):                   do not show miner output during configuration and also less messages
        --verbose (-v):                 show more messages
        --debug:                        show pool and miner messages
        --log=<file_name>:              <file_name> of output log
        --no-config-save:               Do not save config file
        --help (-help,-h,-?):           Prints this help text

Check https://github.com/xmrig/xmrig-proxy/blob/master/doc/STRATUM_EXT.md#14-algorithm-names-and-variants for list of possible algo names.

Sample mm.json (to use with xmrig v2.99.0+ located in the same directory)

{
 "miner_host": "127.0.0.1",
 "miner_port": 3333,
 "pools": [
  "gulf.moneroocean.stream:10001"
 ],
 "algos": {
  "cn/1": "./xmrig --config=config.json",
  "cn/2": "./xmrig --config=config.json",
  "cn/r": "./xmrig --config=config.json",
  "cn/fast": "./xmrig --config=config.json",
  "cn/half": "./xmrig --config=config.json",
  "cn/xao": "./xmrig --config=config.json",
  "cn/rto": "./xmrig --config=config.json",
  "cn/rwz": "./xmrig --config=config.json",
  "cn/zls": "./xmrig --config=config.json",
  "cn/double": "./xmrig --config=config.json",
  "cn/gpu": "./xmrig --config=config.json",
  "cn-heavy/0": "./xmrig --config=config.json",
  "cn-heavy/tube": "./xmrig --config=config.json",
  "cn-heavy/xhv": "./xmrig --config=config.json",
  "cn-pico": "./xmrig --config=config.json",
  "rx/0": "./xmrig --config=config.json",
  "rx/wow": "./xmrig --config=config.json",
  "rx/loki": "./xmrig --config=config.json",
  "rx/arq": "./xmrig --config=config.json",
  "rx/sfx": "./xmrig --config=config.json",
  "argon2/chukwa": "./xmrig --config=config.json",
  "argon2/wrkz": "./xmrig --config=config.json",
  "ghostrider": "./xmrig --config=config.json",
  "ethash": "./gminer/miner --server localhost:3333 --user 87MKQonkAUsQ9MNGKB3L51PE884cTeJbgcu6zWZPZt13b632huSGu9xPZwQALhLnAadEurYA8npRPZTJUWed95ZAT17brdt --pass gpu_miner --algo ethash --proto stratum",
  "kawpow": "./gminer/miner --server localhost:3333 --user 87MKQonkAUsQ9MNGKB3L51PE884cTeJbgcu6zWZPZt13b632huSGu9xPZwQALhLnAadEurYA8npRPZTJUWed95ZAT17brdt --pass gpu_miner --algo kawpow",
  "c29s": "./gminer/miner --server localhost:3333 --user 87MKQonkAUsQ9MNGKB3L51PE884cTeJbgcu6zWZPZt13b632huSGu9xPZwQALhLnAadEurYA8npRPZTJUWed95ZAT17brdt --pass gpu_miner --algo cuckaroo29s",
  "c29b": "./gminer/miner --server localhost:3333 --user 87MKQonkAUsQ9MNGKB3L51PE884cTeJbgcu6zWZPZt13b632huSGu9xPZwQALhLnAadEurYA8npRPZTJUWed95ZAT17brdt --pass gpu_miner --algo cuckaroo29b",
  "c29v": "./gminer39/miner --server localhost:3333 --user 87MKQonkAUsQ9MNGKB3L51PE884cTeJbgcu6zWZPZt13b632huSGu9xPZwQALhLnAadEurYA8npRPZTJUWed95ZAT17brdt --pass gpu_miner --algo cuckarood29",
  "autolykos2": "./trex/t-rex -a autolykos2 -o stratum+tcp://localhost:3333 -u 87MKQonkAUsQ9MNGKB3L51PE884cTeJbgcu6zWZPZt13b632huSGu9xPZwQALhLnAadEurYA8npRPZTJUWed95ZAT17brdt -p gpu_miner"
 },
 "algo_perf": {
  "rx/0": 243.6,
  "cn/r": 49.8,
  "cn/gpu": 12.9,
  "cn-heavy/xhv": 30.5,
  "cn-pico/trtl": 0,
  "rx/wow": 282.2,
  "defyx": 0,
  "argon2/chukwa": 4725.4,
  "k12": 0,
  "c29s": 0,
  "c29v": 0,
  "rx/loki": 243.6,
  "cn/0": 49.8,
  "cn/1": 49.8,
  "cn/2": 49.8,
  "cn/wow": 49.8,
  "cn/fast": 99.6,
  "cn/half": 99.6,
  "cn/xao": 49.8,
  "cn/rto": 49.8,
  "cn/rwz": 66.39999999999999,
  "cn/zls": 66.39999999999999,
  "cn/double": 24.9,
  "cn-heavy/0": 30.5,
  "cn-heavy/tube": 30.5,
  "c29b": 0.1865,
  "c29s": 0.23375,
  "c29v": 0.4875,
  "kawpow": 0.003953464329242706,
  "ethash": 49860000,
  "autolykos2": 144120000,
  "ghostrider": 1000
 },
 "algo_min_time": 0,
 "user": "89TxfrUmqJJcb1V124WsUzA78Xa3UYHt7Bg8RGMhXVeZYPN8cE5CZEk58Y1m23ZMLHN7wYeJ9da5n5MXharEjrm41hSnWHL",
 "pass": "x",
 "log_file": null,
 "watchdog": 600,
 "hashrate_watchdog": 0
}

General configuration guidelines

  • Configure your miners to connect to the single localhost:3333 (non SSL/TLS) pool.

  • For best results separate xmr-stak/xmrig CPU and GPU miners (by using --noCPU, --noAMD, --noNVIDIA options for xmr-stak).

  • Prepare your miner config files that give the best performance for your hardware on cryptonight, cryptonight-heavy, cryptonight-pico, randomx, randomx/wow, randomx/arq algorithm classes (not needed for xmrig v2.99+).

  • If you have several miners on one host use mm.js --port option to assign them to different ports.

  • Additional mm.js pools will be used as backup pools.

  • To rerun benchmark for specific algorithm class use --perf_algo=0 option.

The configuration guide below is for stock xmrig. For xmr-stak/rx check configuration guide for xmr-stak page. For GPU mining setup using gminer algo check configuration guide for gminer page. For c29 algo reference miner setup check configuration guide for cuckaroo29 page.

Usage examples on Windows

Place mm.exe or mm.js (with nodejs installed) into unpacked miner directory either by:

Usage example with xmrig on Windows

  • Download and unpack the lastest xmrig-amd (https://github.com/xmrig/xmrig/releases/download/v5.4.0/xmrig-5.4.0-msvc-win64.zip).

  • Modify config.json file in xmrig directory this way and adjust it for the best threads performance (out of scope of this guide):

    • Set "url" to "localhost:3333"
    • Set "user" to "89TxfrUmqJJcb1V124WsUzA78Xa3UYHt7Bg8RGMhXVeZYPN8cE5CZEk58Y1m23ZMLHN7wYeJ9da5n5MXharEjrm41hSnWHL" (put your Monero wallet address)
  • Run Meta Miner (or use "node mm.js" instead of mm.exe):

mm.exe -p=gulf.moneroocean.stream:10001 -m="xmrig-amd.exe --config=config.json"

Usage examples on Linux (Ubuntu 18.04)

Get node and Meta Miner (mm.js) in the miner directory:

sudo apt-get update
sudo apt-get install -y nodejs
wget https://raw.githubusercontent.com/MoneroOcean/meta-miner/master/mm.js
chmod +x mm.js

Usage example with xmrig on Linux

  • Get xmrig:
wget https://github.com/xmrig/xmrig/releases/download/v5.4.0/xmrig-5.4.0-xenial-x64.tar.gz
tar xf xmrig-5.4.0-xenial-x64.tar.gz
cd xmrig-5.4.0
  • Prepare configs for different algorithms (put your Monero wallet address):
sed -i 's/"url": *"[^"]*",/"url": "localhost:3333",/' config.json
sed -i 's/"user": *"[^"]*",/"user": "89TxfrUmqJJcb1V124WsUzA78Xa3UYHt7Bg8RGMhXVeZYPN8cE5CZEk58Y1m23ZMLHN7wYeJ9da5n5MXharEjrm41hSnWHL",/' config.json
  • Run Meta Miner:
./mm.js -p=gulf.moneroocean.stream:10001 -m="./xmrig --config=config.json"

Developer Donations

If you'd like to make an one time donation, the addresses are as follows:

  • XMR - 89TxfrUmqJJcb1V124WsUzA78Xa3UYHt7Bg8RGMhXVeZYPN8cE5CZEk58Y1m23ZMLHN7wYeJ9da5n5MXharEjrm41hSnWHL
  • AEON - WmsEg3RuUKCcEvFBtXcqRnGYfiqGJLP1FGBYiNMgrcdUjZ8iMcUn2tdcz59T89inWr9Vae4APBNf7Bg2DReFP5jr23SQqaDMT
  • ETN - etnkQMp3Hmsay2p7uxokuHRKANrMDNASwQjDUgFb5L2sDM3jqUkYQPKBkooQFHVWBzEaZVzfzrXoETX6RbMEvg4R4csxfRHLo1
  • SUMO - Sumoo1DGS7c9LEKZNipsiDEqRzaUB3ws7YHfUiiZpx9SQDhdYGEEbZjRET26ewuYEWAZ8uKrz6vpUZkEVY7mDCZyGnQhkLpxKmy
  • GRFT - GACadqdXj5eNLnyNxvQ56wcmsmVCFLkHQKgtaQXNEE5zjMDJkWcMVju2aYtxbTnZgBboWYmHovuiH1Ahm4g2N5a7LuMQrpT
  • MSR - 5hnMXUKArLDRue5tWsNpbmGLsLQibt23MEsV3VGwY6MGStYwfTqHkff4BgvziprTitbcDYYpFXw2rEgXeipsABTtEmcmnCK
  • LTHN - iz53aMEaKJ25zB8xku3FQK5VVvmu2v6DENnbGHRmn659jfrGWBH1beqAzEVYaKhTyMZcxLJAdaCW3Kof1DwTiTbp1DSqLae3e
  • WOW - Wo3yjV8UkwvbJDCB1Jy7vvXv3aaQu3K8YMG6tbY3Jo2KApfyf5RByZiBXy95bzmoR3AvPgNq6rHzm98LoHTkzjiA2dY7sqQMJ
  • XMV - XvyVfpAYp3zSuvdtoHgnDzMUf7GAeiumeUgVC7RTq6SfgtzGEzy4dUgfEEfD5adk1kN4dfVZdT3zZdgSD2xmVBs627Vwt2C3Ey
  • RYO - RYoLsi22qnoKYhnv1DwHBXcGe9QK6P9zmekwQnHdUAak7adFBK4i32wFTszivQ9wEPeugbXr2UD7tMd6ogf1dbHh76G5UszE7k1
  • XLA - SvkpUizij25ZGRHGb1c8ZTAHp3VyNFU3NQuQR1PtMyCqdpoZpaYAGMfG99z5guuoktY13nrhEerqYNKXvoxD7cUM1xA6Z5rRY
  • XHV - hvxyEmtbqs5TEk9U2tCxyfGx2dyGD1g8EBspdr3GivhPchkvnMHtpCR2fGLc5oEY42UGHVBMBANPge5QJ7BDXSMu1Ga2KFspQR
  • TUBE - TubedBNkgkTbd2CBmLQSwW58baJNghD9xdmctiRXjrW3dE8xpUcoXimY4J5UMrnUBrUDmfQrbxRYRX9s5tQe7pWYNF2QiAdH1Fh
  • LOKI - L6XqN6JDedz5Ub8KxpMYRCUoQCuyEA8EegEmeQsdP5FCNuXJavcrxPvLhpqY6emphGTYVrmAUVECsE9drafvY2hXUTJz6rW
  • TRTL - TRTLv2x2bac17cngo1r2wt3CaxN8ckoWHe2TX7dc8zW8Fc9dpmxAvhVX4u4zPjpv9WeALm2koBLF36REVvsLmeufZZ1Yx6uWkYG
  • XTNC - XtazhSxz1bbJLpT2JuiD2UWFUJYSFty5SVWuF6sy2w9v8pn69smkUxkTVCQc8NKCd6CBMNDGzgdPRYBKaHdbgZ5SNptVH1yPCTQ
  • IRD - ir3DHyB8Ub1aAHEewMeUxQ7b7tQdWa7VL8M5oXDPohS3Me4nhwvALXM4mym2kWg9VsceT75dm6XWiWF1K4zu8RVQ1HJD8Z3R9
  • ARQ - ar4Ha6ZQCkKRhkKQLfexv7VZQM2MhUmMmU9hmzswCPK4T3o2rbPKZM1GxEoYg4AFQsh57PsEets7sbpU958FAvxo2RkkTQ1gE
  • XWP - fh4MCJrakhWGoS6Meqp6UxGE1GNfAjKaRdPjW36rTffDiqvEq2HWEKZhrbYRw7XJb3CXxkjL3tcYGTT39m5qgjvk1ap4bVu1R
  • XEQ - Tvzp9tTmdGP9X8hCEw1Qzn18divQajJYTjR5HuUzHPKyLK5fzRt2X73FKBDzcnHMDJKdgsPhUDVrKHVcDJQVmLBg33NbkdjQb
  • XTA - ipN5cNhm7RXAGACP4ZXki4afT3iJ1A6Ka5U4cswE6fBPDcv8JpivurBj3vu1bXwPyb8KZEGsFUYMmToFG4N9V9G72X4WpAQ8L
  • DERO - dero1qygrgnz9gea2rqgwhdtpfpa3mvagt5uyq0g92nurwrpk6wnn7hdnzqgudsv6t
  • CCX - ccx7dmnBBoRPuVcpKJSAVZKdSDo9rc7HVijFbhG34jsXL3qiqfRwu7A5ecem44s2rngDd8y8N4QnYK6WR3mXAcAZ5iXun9BQBx
  • BLOC - abLoc5iUG4a6oAb2dqygxkS5M2uHWx16zHb9fUWMzpSEDwm6T7PSq2MLdHonWZ16CGfnJKRomq75aZyviTo6ZjHeYQMzNAEkjMg
  • RVN - RLVJv9rQNHzXS3Zn4JH8hfAHmm1LfECMxy
  • RTM - RUCyaEZxQu3Eure73XPQ57si813RYAMQKC
  • ERG - 9fe533kUzAE57YfPP6o3nzsYMKN2W2uCxvg8KG8Vn5DDeJGetRw
  • BTC - 3HRbMgcvbqHVW7P34MNGvF2Gh3DE26iHdw
  • BCH - 18sKoDSjLCFW9kZrXuza1qzEERnKi7bx8S
  • ETH - 0xfE23a61548FCCE159a541FAe9e16cEB92Da650ed
  • ETC - 0x4480Ad73a113BEFf05B2079E38D90c9757Ecb063
  • LTC - MGj8PU1PpTNDDqRHmuEqfDpH3gxp6cJrUU

meta-miner's People

Contributors

bathmat avatar marosmacko avatar moneroocean avatar spudz76 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

meta-miner's Issues

MM 1.2 restart errors

MM v1.2 with stock xmrig 2.8.1 log file attached. I am experiencing restart errors similar to the attached on my rig. 3 different instances running (local host 3334,5, and 6) to separate different cards. Trying stock xmrig 2.8.3 has no change. Errors consistently reference the miner port being in use by another instance.
mm.log
mm config.json as follows
{
"miner_host": "127.0.0.1",
"miner_port": 3335,
"pools": [
"us.moneroocean.stream:10032"
],
"algos": {
"cn/1": "xmrig-amd.exe --config=config.json",
"cn/2": "xmrig-amd.exe --config=config.json",
"cn/xtl": "xmrig-amd.exe --config=config.json",
"cn/msr": "xmrig-amd.exe --config=config.json",
"cn/xao": "xmrig-amd.exe --config=config.json",
"cn/rto": "xmrig-amd.exe --config=config.json",
"cn-heavy/0": "xmrig-amd.exe --config=config-heavy.json",
"cn-heavy/tube": "xmrig-amd.exe --config=config-heavy.json",
"cn-heavy/xhv": "xmrig-amd.exe --config=config-heavy.json",
"cn-lite/1": "xmrig-amd.exe --config=config-lite.json"
},
"algo_perf": {
"cn": 1807,
"cn/2": 1902,
"cn/msr": 3512.2,
"cn-lite": 3674,
"cn-heavy": 1354
},
"algo_min_time": 400,
"user": "removed",
"pass": "RX480",
"log_file": "mm.log",
"watchdog": 250,
"hashrate_watchdog": 80
}

mm.js not work with cryptodredge

hello.i want to user cryptodredge miner to do with mm.js,but after i set it up.there is no accepted result show and no hashrate show.anyone get any success on it?
[01:51:22] INFO - GPU4 Intensity set to 6
[01:51:22] INFO - GPU5 Intensity set to 6
[01:51:22] INFO - GPU6 Intensity set to 6
[01:51:22] INFO - GPU7 Intensity set to 6
[01:51:22] INFO - CCminer TCP API: server started on 0.0.0.0:16000

Miner message: {"id":2,"method":"login","params":{"agent":"CryptoDredge/0.9.3","login":"4AkLFtaEdz3T1bDn6pJdGSUH29TCZFTytgRgtCcXMPvVEhATAPyTLHPEB4E7Ayx4egXctWVLgWBUKjkzZTf4x4fiL6vWGtu","pass":"test"}}
Pool (us.moneroocean.stream:10001) <-> miner link was established due to new miner connection
[01:51:22] INFO - 1/0 Accepted : diff=0 : 0.00H/s
[01:51:22] INFO - Start user session
[01:52:22] INFO - GPU0 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=38C Fan=65%
[01:52:22] INFO - GPU1 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=39C Fan=65%
[01:52:22] INFO - GPU2 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=40C Fan=65%
[01:52:22] INFO - GPU3 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=39C Fan=65%
[01:52:22] INFO - GPU4 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=44C Fan=65%
[01:52:22] INFO - GPU5 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=43C Fan=65%
[01:52:22] INFO - GPU6 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=42C Fan=65%
[01:52:22] INFO - GPU7 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=43C Fan=65%
[01:52:22] INFO - GPU5 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=43C Fan=65%
[01:52:22] INFO - GPU6 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=42C Fan=65%
[01:52:22] INFO - GPU7 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=43C Fan=65%
[01:53:22] INFO - GPU0 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=39C Fan=65%
[01:53:22] INFO - GPU1 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=40C Fan=65%
[01:53:22] INFO - GPU2 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=42C Fan=65%
[01:53:22] INFO - GPU3 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=41C Fan=65%
[01:53:22] INFO - GPU4 GTX 750 : 0.00H/s (Avr 0.00H/s) : 0.00H/W : T=44C Fan=65%

Pool (gulf.moneroocean.stream:10218) socket error

>>> Meta Miner v4.4
>>> POOL USER: '<wallet address hidden>', PASS: 'x'
!!! Pool (gulf.moneroocean.stream:10218) socket error

Meta-miner doesn't start, gets stuck on this error.

It was able to benchmark the algorithms though, but after that and for the following runs, it freezes on the above error.

Error thrown when passing config_file.json as command line parameter

`root@Ubuntu1804MATEbeta:/home/xmr# ./mm.js mm3333.json

Meta Miner v0.5
module.js:549
throw err;
^

Error: Cannot find module 'mm3333.json'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at load_config_file (/home/xmr/meta-miner/mm.js:586:16)
at /home/xmr/meta-miner/mm.js:517:9
at Array.forEach ()
at parse_argv (/home/xmr/meta-miner/mm.js:512:25)
at Object. (/home/xmr/meta-miner/mm.js:643:1)
at Module._compile (module.js:652:30)
root@Ubuntu1804MATEbeta:/home/xmr# ./mm.js mm.json

Meta Miner v0.5
module.js:549
throw err;
^

Error: Cannot find module 'mm.json'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at load_config_file (/home/xmr/meta-miner/mm.js:586:16)
at /home/xmr/meta-miner/mm.js:517:9
at Array.forEach ()
at parse_argv (/home/xmr/meta-miner/mm.js:512:25)
at Object. (/home/xmr/meta-miner/mm.js:643:1)
at Module._compile (module.js:652:30)
root@Ubuntu1804MATEbeta:/home/xmr# ls -hl mm*
-rw-r--r-- 1 root root 1.6K Aug 13 09:45 mm3333.json
lrwxrwxrwx 1 root root 16 Aug 13 09:31 mm.js -> meta-miner/mm.js
-rw-r--r-- 1 root root 1.6K Aug 13 09:41 mm.json`

Watchdog causes repeated miner restarts

Windows compile of mm 1.5. Metaminer is getting into a loop restarting the miner when no results are being returned.

  1. The watchdog is set at 600s (ten minutes).
  2. If there are no results accepted by the pool in ten minutes, mm restarts the miner.
  3. After the initial restart, mm lets the miner run for about a minute and, then, restarts it again due to no results for the last 600 seconds. After another minute, it starts again.
  4. The miner restarts repeat until the miner manages to return a result during its short run time, or mm is manually restarted.

Need some set up help please

I am completely new to MO and meta-miner. i have the new stak installed and running good. i am running vega 64's with a windows system and amd ver 22.19.659.0 drivers. now i am unsure of the mm.js config. i will post what i have below, but do i have all the alt coins for MO? does this look like all i need to get started???

{
"miner_host": "127.0.0.1",
"miner_port": "3333",
"pools": [
"gulf.moneroocean.stream:10128",

],
"algos": {
--cn/1="xmr-stak.exe --noCPU
--currency cryptonight_v7 --amd amd.txt"
--cn/msr="xmr-stak.exe --noCPU
--currency cryptonight_masari --amd amd.txt"
--cn-lite/1="xmr-stak.exe --noCPU
--currency cryptonight_lite_v7 --amd amd-lite.txt"
--cn-heavy/0="xmr-stak.exe --noCPU
--currency cryptonight_heavy --amd amd-heavy.txt"
--cn-heavy/xhv="xmr-stak.exe --noCPU
--currency cryptonight_haven --amd amd-heavy.txt"
--cn-heavy/tube="xmr-stak.exe --noCPU
--currency cryptonight_bittube2 --amd amd-heavy.txt"

"user": "wallet",
"pass": "x",
"log_file": null,
"watchdog": 600,
"hashrate_watchdog": 0
}

Support for TLS?

Can the software communicate with moneroocean pool via TLS? The example configuration on README.md currently shows a non-tls pool port. What configs must one change to enable TLS?

xmrig CUDA usage

Hello, i am trying to xmrig with the cuda library i compiled and xmrig cant seem to find it in the folder.
Is there somewhere i need to add the library in xmrigs config?

Duplicate shares when switching from c29b to ethash

This issue was monitored since a few days. When switching from cuckaroo29b to ethash mining all shares are rejected as duplicates. Then of course IP is banned.
I think I didn't noticed it before because this switching is quite rare but this might be a new issue, dunno. All other monitored switching pairs work fine from weeks.
The result is the same with GMiner or T-rex with ethash: duplicate shares

+----------------------------------------------------------------+
| GMiner v2.58 |
+----------------------------------------------------------------+
Algorithm: Cuckaroo29b
DevFee: 4%
Stratum server:
host: 127.0.0.1:3333
user: WALLET
password: GPU~c29b
Power calculator: off
Color output: on
Watchdog: on
API: off
Log to file: off
Selected devices: GPU0
Intensity: 100
Temperature limits: 90/120
02:13:12 P2 State Disabled
02:13:13 Nvidia Driver: 471.68
02:13:14 GPU0 NVIDIA GeForce RTX 2060 6GB: Selected 5GB Solver
Pool (gulf.moneroocean.stream:10256) <-> miner link was established due to new miner connection
02:13:14 Connected to 127.0.0.1:3333 [127.0.0.1]
02:13:14 Authorized on Stratum Server
02:13:14 New Job: 17170242 Diff: 6
02:13:14 Started Mining on GPU0: NVIDIA GeForce RTX 2060 6GB [0000:26:00.0]
02:13:24 New Job: 17170664 Diff: 6
02:13:30 GPU0: Share #1 accepted 58 ms

...

03:06:44 Pool: 127.0.0.1:3333 Shares/Minute: 1.83
03:06:44 Uptime: 0d 00:53:30
03:06:49 GPU0: Share #99 accepted 62 ms
03:06:58 New Job: 17309372 Diff: 5
03:07:12 New Job: 17310168 Diff: 5
+---+-----+----+-----+---------+--------+------+----+------+
| ID GPU Temp Fan Speed Fidelity Shares Core Mem |
+---+-----+----+-----+---------+--------+------+----+------+
| 0 2060 62 66 % 6.64 G/s 1.03 99/0 1695 8000 |
+---+-----+----+-----+---------+--------+------+----+------+
03:07:14 Pool: 127.0.0.1:3333 Shares/Minute: 1.83
03:07:14 Uptime: 0d 00:54:00
03:07:26 New Job: 17310718 Diff: 5
03:07:42 New Job: 17310961 Diff: 5
+---+-----+----+-----+---------+--------+------+----+------+
| ID GPU Temp Fan Speed Fidelity Shares Core Mem |
+---+-----+----+-----+---------+--------+------+----+------+
| 0 2060 62 66 % 6.64 G/s 1.03 99/0 1695 8000 |
+---+-----+----+-----+---------+--------+------+----+------+
03:07:44 Pool: 127.0.0.1:3333 Shares/Minute: 1.82
03:07:44 Uptime: 0d 00:54:30
03:08:01 New Job: 17311633 Diff: 5
03:08:01 GPU0: Share #100 accepted 173 ms
03:08:02 New Job: 17311645 Diff: 5
03:08:03 New Job: 17311660 Diff: 5
Starting miner './nsfminer.exe -P stratum2+tcp://WALLET:[email protected]:3333 --report-hashrate --HWMON 2' to process new ethash algo
!!! Miner socket error
03:08:10 miner nsfminer 1.3.14 (No stinkin' fees edition)
03:08:10 miner Copyright 2021 Jean M. Cyr, Licensed under the terms
03:08:10 miner of the GNU General Public License Version 3
03:08:10 miner https://github.com/no-fee-ethereum-mining/nsfminer
03:08:10 miner Build: windows/release/msvc
03:08:10 miner 3rd Party: MSVC 19.16.27045.0, CUDA 11.3, Boost 1.76.0
03:08:10 miner 3rd Party: OpenSSL 1.1.1j 16 Feb 2021
03:08:10 miner Running as user:
03:08:10 miner Configured pool 127.0.0.1:3333
03:08:10 miner Selected pool 127.0.0.1:3333
03:08:10 miner Stratum mode : EthereumStratum/1.0.0 (NiceHash)
03:08:10 miner Established connection to 127.0.0.1:3333
03:08:10 miner Spinning up miners...
03:08:10 cu-0 Using Pci 0000:26:00.0: NVIDIA GeForce RTX 2060 (Compute 7.5) Memory : 6.00 GB
03:08:10 miner Extranonce set to fb9d
03:08:10 miner Authorized worker WALLET
03:08:10 miner Epoch : 438 Difficulty : 986.69 Mh
03:08:10 miner Job: 4965d91a 127.0.0.1:3333
03:08:13 cu-0 Required GPU mem: Total 4.49 GB, Cache 70.75 MB, DAG 4.42 GB, Miscellaneous 56.00 B
03:08:15 miner 0:00 A0 0.00 h - cu0 0.00 59C 0% 90.96W
03:08:19 miner Job: 9238e98b 127.0.0.1:3333
03:08:20 miner 0:00 A0 0.00 h - cu0 0.00 59C 0% 90.68W
03:08:25 miner 0:00 A0 0.00 h - cu0 0.00 59C 0% 91.24W
03:08:29 miner Job: 4ea9b4e2 127.0.0.1:3333
03:08:30 cu-0 4.42 GB of DAG data generated in 16.4 seconds
03:08:30 miner 0:00 A0 12.96 Kh - cu0 12.96 58C 0% 87.80W
03:08:35 miner 0:00 A0 33.04 Mh - cu0 33.04 58C 0% 88.19W
03:08:36 miner Job: cb901958 127.0.0.1:3333
03:08:38 miner Job: d91a0e49 127.0.0.1:3333
03:08:40 miner 0:00 A0 33.09 Mh - cu0 33.09 58C 0% 87.84W
03:08:45 miner 0:00 A0 33.08 Mh - cu0 33.08 58C 0% 87.86W
03:08:50 miner 0:00 A0 33.09 Mh - cu0 33.09 57C 0% 87.61W
03:08:52 miner Epoch : 438 Difficulty : 982.55 Mh
03:08:52 miner Job: f255ed59 127.0.0.1:3333
03:08:54 miner Job: 5ed9157e 127.0.0.1:3333
03:08:55 miner 0:00 A0 33.09 Mh - cu0 33.09 57C 0% 87.70W
03:09:00 miner 0:00 A0 33.08 Mh - cu0 33.08 57C 0% 87.56W
03:09:00 miner Job: 5d6f16e1 127.0.0.1:3333
03:09:02 miner Job: 557ea9b4 127.0.0.1:3333
03:09:05 miner 0:00 A0 33.09 Mh - cu0 33.09 57C 0% 87.71W
03:09:07 miner Job: f17a913e 127.0.0.1:3333
03:09:07 miner Job: 9227221c 127.0.0.1:3333
03:09:10 miner 0:01 A0 33.07 Mh - cu0 33.07 57C 0% 87.36W
03:09:10 miner Job: 8dfa8591 127.0.0.1:3333
03:09:15 miner 0:01 A0 33.08 Mh - cu0 33.08 57C 0% 87.41W
03:09:18 cu-0 Job: 8dfa8591 Solution: 0xfb9d00000f6e683d
03:09:18 miner Solution difficulty: 2.55 Gh
03:09:18 miner Reject reason : code:-1 message:Duplicate share
03:09:18 miner **Rejected 50 ms. 127.0.0.1:3333
03:09:20 miner 0:01 A0:R1 33.08 Mh - cu0 33.08 57C 0% 87.73W
03:09:21 miner Job: c165b851 127.0.0.1:3333
03:09:23 miner Job: 942871d6 127.0.0.1:3333
03:09:25 miner 0:01 A0:R1 33.08 Mh - cu0 33.08 56C 0% 87.51W
03:09:30 miner 0:01 A0:R1 33.08 Mh - cu0 33.08 56C 0% 87.64W
03:09:35 miner 0:01 A0:R1 33.09 Mh - cu0 33.09 56C 0% 87.42W
03:09:40 miner 0:01 A0:R1 33.09 Mh - cu0 33.09 56C 0% 87.41W
03:09:45 miner 0:01 A0:R1 33.09 Mh - cu0 33.09 56C 0% 87.07W
03:09:45 miner Job: 30aa6edb 127.0.0.1:3333
03:09:50 miner 0:01 A0:R1 33.09 Mh - cu0 33.09 56C 0% 87.36W
03:09:55 miner 0:01 A0:R1 33.08 Mh - cu0 33.08 56C 0% 87.13W
03:09:59 miner Epoch : 438 Difficulty : 974.29 Mh
03:09:59 miner Job: 951b9aef 127.0.0.1:3333
03:10:00 miner 0:01 A0:R1 33.09 Mh - cu0 33.09 56C 0% 87.37W
03:10:05 miner 0:01 A0:R1 33.08 Mh - cu0 33.08 56C 0% 86.99W
03:10:10 miner 0:02 A0:R1 33.09 Mh - cu0 33.09 56C 0% 87.03W
03:10:15 miner Job: a6cae94c 127.0.0.1:3333
03:10:15 miner 0:02 A0:R1 33.09 Mh - cu0 33.09 56C 0% 87.15W
03:10:20 miner 0:02 A0:R1 33.08 Mh - cu0 33.08 56C 0% 86.91W
03:10:21 cu-0 Job: a6cae94c Solution: 0xfb9d00000cc5f31b
03:10:21 miner Solution difficulty: 1.40 Gh
03:10:21 miner Reject reason : code:-1 message:Duplicate share
03:10:21 miner **Rejected 51 ms. 127.0.0.1:3333
03:10:25 miner 0:02 A0:R2 33.09 Mh - cu0 33.09 56C 0% 87.24W
03:10:30 miner 0:02 A0:R2 33.08 Mh - cu0 33.08 56C 0% 87.14W

Two instances needed for CPU+GPU usage?

Say one has a mining rig with a performant CPU and GPUs. With the example mm.json on README.md, the computer would only use either the CPU or the GPUs at a given time, correct?

Would a good solution to that be: having two mm.js instances (with different ports), one for CPU miners, one for GPU miners?
Is this needed / recommended?

Thanks

mm.js spawning multiple child mining threads

It appears that mm.js is not cleanly killing the current mining thread before spawning a new thread when changing crypto alogorithms. Seen on all mm.js versions since just before the cn/2 fork.

When running mm.js, after a random amount of time (hours to days) it will eventually start to complain about 'connection already in use' and fail to submit any hashes. Looking at the pidtree of the 'node mm.js' process you can see two child processes of xmrig running. Killing mm.js and restarting it will allow it to continue working again.

I have seen this happen on both my Windows and Linux rigs, and spawning either xmrig or xmrig-nvidia.

I have begun testing with older commits of mm.js (0.8,0.9,1.1 and 1.2) on various machines to try and track down which commit this issue started with. I know the older version from late Aug (0.8?) did not show this. I will update this ticket if I can determine which commit needs closer inspection.

Support for ETC/etchash

Since moneroocean pool now supports ETC, can the meta-miner support it too? I'm available to help as a volunteer.

Problem switching to cn-lite

mm.exe v1.3
When auto-switching to cn-lite sometimes this continuously happens..

[2018-10-26 12:31:22] accepted (5/0) diff 60000 (25 ms)
Starting miner 'xmrig-amd.exe --config=config-lite.json' to process new cn-lite/1 algo
Miner socket error
 * ABOUT        XMRig-AMD/2.8.4 MSVC/2017
 * LIBS         libuv/1.23.0 OpenCL/2.0 OpenSSL/1.1.1 microhttpd/0.9.59 
 * CPU          AMD Ryzen 7 2700 Eight-Core Processor           x64 AES
 * ALGO         cryptonight-lite/1, donate=0%
 * POOL #1      localhost:3333 variant=1, TLS=0
 * API BIND     0.0.0.0:420
 * COMMANDS     'h' hashrate, 'p' pause, 'r' resume
[2018-10-26 12:31:24] compiling code and initializing GPUs. This will take a while...
Starting miner 'xmrig-amd.exe --config=config-cn1.json' to process new cn/xtl algo
 * ABOUT        XMRig-AMD/2.8.4 MSVC/2017
 * LIBS         libuv/1.23.0 OpenCL/2.0 OpenSSL/1.1.1 microhttpd/0.9.59 
 * CPU          AMD Ryzen 7 2700 Eight-Core Processor           x64 AES
 * ALGO         cryptonight, donate=0%
 * POOL #1      localhost:3333 variant=1, TLS=0
 * API BIND     0.0.0.0:420
 * COMMANDS     'h' hashrate, 'p' pause, 'r' resume
[2018-10-26 12:31:24] compiling code and initializing GPUs. This will take a while...
[2018-10-26 12:31:25] found AMD platform index: 0, name: Advanced Micro Devices, Inc.
[2018-10-26 12:31:25] #0, GPU #1 (Radeon RX Vega), intensity: 1920 (8/256), unroll: 4, cu: 56
[2018-10-26 12:31:25] #1, GPU #1 (Radeon RX Vega), intensity: 1920 (8/256), unroll: 4, cu: 56
[2018-10-26 12:31:25] #2, GPU #0 (Radeon RX Vega), intensity: 1920 (8/256), unroll: 8, cu: 64
[2018-10-26 12:31:26] #3, GPU #0 (Radeon RX Vega), intensity: 1920 (8/256), unroll: 8, cu: 64
[2018-10-26 12:31:26] #4, GPU #2 (Radeon RX Vega), intensity: 1920 (8/256), unroll: 8, cu: 64
[2018-10-26 12:31:26] #5, GPU #2 (Radeon RX Vega), intensity: 1920 (8/256), unroll: 8, cu: 64
Pool (gulf.moneroocean.stream:10064) <-> miner link was established due to new miner connection
[2018-10-26 12:31:26] use pool localhost:3333  127.0.0.1
[2018-10-26 12:31:26] new job from localhost:3333 diff 60000 algo cn/xtl

------and sometimes this...------

[2018-10-26 13:01:05] new job from localhost:3333 diff 60000 algo cn/2
Starting miner 'xmrig-amd.exe --config=config-lite.json' to process new cn-lite/1 algo
Starting miner 'xmrig-amd.exe --config=config-cn2.json' to process new cn/2 algo
Miner socket error
 * ABOUT        XMRig-AMD/2.8.4 MSVC/2017
 * LIBS         libuv/1.23.0 OpenCL/2.0 OpenSSL/1.1.1 microhttpd/0.9.59
 * CPU          AMD Ryzen 7 2700 Eight-Core Processor           x64 AES
 * ALGO         cryptonight, donate=0%
 * POOL #1      localhost:3333 variant=1, TLS=0
 * API BIND     0.0.0.0:420
 * COMMANDS     'h' hashrate, 'p' pause, 'r' resume
[2018-10-26 13:01:09] compiling code and initializing GPUs. This will take a while...
[2018-10-26 13:01:10] found AMD platform index: 0, name: Advanced Micro Devices, Inc.
[2018-10-26 13:01:10] #0, GPU #1 (Radeon RX Vega), intensity: 1920 (16/256), unroll: 4, cu: 56
[2018-10-26 13:01:10] #1, GPU #1 (Radeon RX Vega), intensity: 1920 (16/256), unroll: 4, cu: 56
[2018-10-26 13:01:10] #2, GPU #0 (Radeon RX Vega), intensity: 1920 (16/256), unroll: 8, cu: 64
[2018-10-26 13:01:11] #3, GPU #0 (Radeon RX Vega), intensity: 1920 (16/256), unroll: 8, cu: 64
[2018-10-26 13:01:11] #4, GPU #2 (Radeon RX Vega), intensity: 1920 (16/256), unroll: 8, cu: 64
[2018-10-26 13:01:11] #5, GPU #2 (Radeon RX Vega), intensity: 1920 (16/256), unroll: 8, cu: 64
Pool (gulf.moneroocean.stream:10064) <-> miner link was established due to new miner connection
[2018-10-26 13:01:11] use pool localhost:3333  127.0.0.1
[2018-10-26 13:01:11] new job from localhost:3333 diff 60000 algo cn/2

meta-miner error while switching

I have 3 cpu miners encounter this after a few hours of mining:

!!! Ignoring job with new algo cn/1 from the pool (10.77.77.120:1111) since we still waiting for new miner to start
[2018-08-20 15:12:09] : Fast-connecting to localhost:3333 pool ...
[2018-08-20 15:12:09] : Pool localhost:3333 connected. Logging in...
>>> Pool (10.77.77.120:1111) <-> miner link was established due to new miner connection
!!! No pool (10.77.77.120:1111) job to send to the miner!
!!! Pool (10.77.77.120:1111) <-> miner link was broken due to closed miner socket
[2018-08-20 15:12:19] : SOCKET ERROR - [localhost:3333] CALL error: Timeout while waiting for a reply
[2018-08-20 15:12:49] : Fast-connecting to localhost:3333 pool ...
[2018-08-20 15:12:49] : Pool localhost:3333 connected. Logging in...
>>> Pool (10.77.77.120:1111) <-> miner link was established due to new miner connection
!!! No pool (10.77.77.120:1111) job to send to the miner!
/home/xmr/mm.js:361
        err("[INTERNAL ERROR] Can not update pool (" + c.pools[pool_num] + ") job since its first job is missing");
                                                               ^

ReferenceError: pool_num is not defined
    at pool_new_msg (/home/xmr/mm.js:361:64)
    at Socket.<anonymous> (/home/xmr/mm.js:273:23)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:146:16)
    at Socket.Readable.push (_stream_readable.js:110:10)
    at TCP.onread (net.js:523:20)

All miners where using self-compiled xmr-stak (for zero dev fee). They were all mining cn-lite and this error happened when they tried to switch to cn/1

separating cn/xtl from cn/1 in algo_perf

Hi!

Since claymore do not support cn/1 variants (and no or buggy support from xmr-stak, as well), I'm looking for a way to detach cn/xtl (and xao and rto) from cn/1's algo_perf value so that I can point it to xmrig instead. So I added the following in mm.js:

const algo_perf_algo = {
  "cn":       "cn/1",
  "cn-xtl":   "cn/xtl",          // <== Added this here...
  "cn-fast":  "cn/msr",
  "cn-lite":  "cn-lite/1",
  "cn-heavy": "cn-heavy/0",
};

function algo_perf_class(algo) { // converts algo to algo class
   if (algo.indexOf("heavy") > -1) return "cn-heavy";
   if (algo.indexOf("lite")  > -1) return "cn-lite";
   if (algo.indexOf("msr")   > -1) return "cn-fast";
   if (algo.indexOf("rto")   > -1) return "cn-xtl";       // <== and this,
   if (algo.indexOf("xao")   > -1) return "cn-xtl";       // <== and this,
   if (algo.indexOf("xtl")   > -1) return "cn-xtl";       // <== and this here.
   return "cn";

Then I manually added an algo_perf entry in mm.json for cn/xtl

Is that enough?

GMiner v2.39 socket drops

Just a heads up that as of yesterday GMiner v2.39 on cuckarood29v as shown in the example gist consistently drops the socket after submitting a share. I singled this out as the issue by removing it from my mm.json so that it used a more recent version of GMiner on cuckarood29s. My xmrig worked consistently on the same machine, while GMiner v2.39 dropped sockets for ~20 hours, so I am confident that this was not a network issue.

Please note that this is not a complaint, just a friendly heads up. I'm going to find another cuckarood29v miner tomorrow. Please keep up the great work.

Ethash : "failed to ethproxy-subscribe"

20220622 11:43:15 ERROR: No connection with localhost:3333, retry after 10 seconds
20220622 11:43:25 Using protocol: stratum1.
20220622 11:43:25 Authorizing...
!!! Can't write miner reply to the pool since its socket is closed
20220622 11:43:35 Wait on data is timed out, 10 seconds have passed, 0 bytes in socket remained
20220622 11:43:35 WARN: failed to ethproxy-subscribe on localhost:3333: can't parse json:
* Line 1, Column 1
  Syntax error: value, object or array expected.

Can't use Ethash with t-rex miner, it seems the interaction with meta-miner is bugged?

config file:

"ethash": "/home/seibel/sw/t-rex/t-rex -a ethash -o stratum+tcp://localhost:3333 -u <wallet hidden> -p gpu_miner"

Can this be worked-around or sovled somehow?

Hunch: Is it suposed to be interpreted as ethproxy?

SRBMiner

SRBMiner does not currently work with the mm wrapper. Any plans to add compatibility with this miner into the wrapper? While SRB does contain internal algoswitching, it is not the best miner on all algos; ideally, I'm trying to use the wrapper to pick and choose miners for each algo.

Only 2 things in the 1.9 zip

When I extracted the 1.9 zip, there are only the mm.exe and the read me files. aren't there supposed to be 7 total?

mm.js crashes with TypeError Cannot use 'in' operator to search for 'status' in null

mm.js v4.4 will occasionally crash with the following error message...

Feb 14 00:13:09 xps8300 mm.js[737]: /home/user/gitrepo/meta-miner/mm.js:652
Feb 14 00:13:09 xps8300 mm.js[737]:         if ("result" in grin_json && "status" in grin_json.result && grin_json.result.status === "OK") {
Feb 14 00:13:09 xps8300 mm.js[737]:                                               ^
Feb 14 00:13:09 xps8300 mm.js[737]: TypeError: Cannot use 'in' operator to search for 'status' in null
Feb 14 00:13:09 xps8300 mm.js[737]:     at pool_new_msg (/home/user/gitrepo/meta-miner/mm.js:652:47)
Feb 14 00:13:09 xps8300 mm.js[737]:     at Socket.<anonymous> (/home/user/gitrepo/meta-miner/mm.js:534:11)
Feb 14 00:13:09 xps8300 mm.js[737]:     at Socket.emit (events.js:198:13)
Feb 14 00:13:09 xps8300 mm.js[737]:     at addChunk (_stream_readable.js:288:12)
Feb 14 00:13:09 xps8300 mm.js[737]:     at readableAddChunk (_stream_readable.js:269:11)
Feb 14 00:13:09 xps8300 mm.js[737]:     at Socket.Readable.push (_stream_readable.js:224:10)
Feb 14 00:13:09 xps8300 mm.js[737]:     at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

It seems to happen once every day or two. I haven't determined if it only happens on certain algorithms. In this most recent case, it was running c29b

algo_min_time argument not working

I noticed that meta-miner doesn't seem to respect the algo minimum running time entered. I set it to 900 seconds (15 min) but it often changes before that. The most recent example; I was mining ETH and it switched to ERG from 1:36:32 pm to 1:46:35 pm, when it switched back to ETH. Pretty much exactly 10min.

version 4.3
using mm.exe file
Windows 10

Crash after pool socket close with Windows executable

I have been getting this error seemingly at random. I got it in 2.1 as well as in 2.2. Using the Windows executable with xmrig-amd.

!!! Pool (gulf.moneroocean.stream:10016) <-> miner link was broken due to closed miner socket
[2019-09-28 17:11:56] no active pools, stop mining
!!! Pool (gulf.moneroocean.stream:10016) socket error
!!! Pool (us.moneroocean.stream:10016) socket error
!!! Pool (ca.moneroocean.stream:10016) socket error
net.js:1048
throw new RangeError('"port" option should be >= 0 and < 65536: ' + port);
^

RangeError: "port" option should be >= 0 and < 65536: 100161
at lookupAndConnect (net.js:1048:13)
at Socket.connect (net.js:1021:5)
at Object.connect (net.js:113:35)
at connect_pool (C:\snapshot\meta-miner\mm.js:400:91)
at pool_err (C:\snapshot\meta-miner\mm.js:550:5)
at Socket. (C:\snapshot\meta-miner\mm.js:452:5)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)

Invalid Resource Handle when running KawPow

Microsoft Windows [Version 10.0.19042.928]
(c) Microsoft Corporation. All rights reserved.

C:\Users\arie\Crypto\meta-miner>mm.exe --perf_kawpow=0 -v

Meta Miner v4.1
Local miner server on 127.0.0.1:3333 port started
Checking miner performance for kawpow algo
Starting miner: xmrig.exe --config config.json -a kawpow --no-cpu

  • ABOUT XMRig/6.12.1-mo1 gcc/8.1.0
  • LIBS libuv/1.41.0 OpenSSL/1.1.1j hwloc/2.4.1
  • HUGE PAGES permission granted
  • 1GB PAGES unavailable
  • CPU Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (1) 64-bit AES
    L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1
  • MEMORY 2.0/7.9 GB (26%)
    DIMM_A0: 4 GB DDR3 @ 2400 MHz F3-2400C10-4GTX
    ChannelA-DIMM1:
    DIMM_B0: 4 GB DDR3 @ 2400 MHz F3-2400C10-4GTX
    ChannelB-DIMM1:
  • MOTHERBOARD Gigabyte Technology Co., Ltd. - Z97X-Gaming 3
  • DONATE 1%
  • ASSEMBLY auto:intel
  • POOL #1 localhost:3333 algo auto
  • COMMANDS 'h' hashrate, 'p' pause, 'r' resume, 's' results, 'c' connection
  • OPENCL disabled
  • CUDA 11.3/11.3/6.12.0
  • NVML 11.466.11/466.11 press e for health report
  • CUDA GPU #0 01:00.0 NVIDIA GeForce GTX 1660 1785/4001 MHz smx:22 arch:75 mem:5159/6144 MB
    [2021-04-26 11:53:50.580] config configuration saved to: "config.json"

Miner server on 127.0.0.1:3333 port connected from 127.0.0.1
[2021-04-26 11:53:50.580] net use pool localhost:3333 127.0.0.1
[2021-04-26 11:53:50.580] net new job from localhost:3333 diff 4294M algo kawpow height 0
[2021-04-26 11:53:50.580] nvidia use profile kawpow (1 thread) scratchpad 32 KB
| # | GPU | BUS ID | INTENSITY | THREADS | BLOCKS | BF | BS | MEMORY | NAME
| 0 | 0 | 01:00.0 | 11534336 | 256 | 45056 | 6 | 25 | 1024 | NVIDIA GeForce GTX 1660
[2021-04-26 11:53:50.737] nvidia READY threads 1/1 (165 ms)
[2021-04-26 11:53:51.846] miner KawPow light cache for epoch 0 calculated (1107ms)
[2021-04-26 11:53:59.106] nvidia KawPow DAG for epoch 0 calculated (7262ms)
[2021-04-26 11:53:59.106] nvidia thread #0 failed with error <KawPow_Raven::hash>:149 "invalid resource handle"

Miner socket error invalid algorithm: cuckaroo29s

unable to create mm.json after this error

mm.exe -p=gulf.moneroocean.stream:11024 --ethash="%GMINER% --algo ethash --proto stratum" --kawpow="%GMINER% --algo kawpow" --c29s="%GMINER% --algo cuckaroo29s" --c29b="%GMINER% --algo cuckaroo29b" --autolykos2="C:\Users\User\Desktop\gpu-miner-moneroocean/t-rex.exe -a autolykos2 -o stratum+tcp://localhost:3333 -u MY_WALLET -p gpu_miner"

Continually triggers IP restrictions on your pool

The meta miner never successfully submits to the pool, the meta miner manages to break the flow entirely and results in MoneroOcean starting to drop traffic with

"Error code: -1 - New connections from this IP address are temporarily suspended from mining (10 minutes max)"

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.