[Solved] Mainnet mining - Ubuntu Multi GPU Tutorial


Hey brothers

  • I can’t open your website in China


perhaps you can use a vpn service


This is the problem I have encountered. Although I have been very careful about setting it up, it has been bothering me for a long time. I have checked a lot of information, including the buddies above, as well as the suggestions, including a git, which is specific to every blank space. It’s really frustrating. Can anyone tell me how to solve the configuration of epoch. yaml?

Validation failed
Position: mining/cuckoominer/instances
Value : #{<<101,100,103,101,95,98,105,116,115>>=>29,<<101,120,101,99,117,116,97,98,108,101>>=><<99,117,100,97,50,57>>,<<101,120,116,114,97,95,97,114,103,115>>=><<45,69,49>>,<<104,101,120,95,101,110,99,111,100,101,100,95,104,101,97,100,101,114>>=>true,<<105,110,115,116,97,110,99,101,115>>=>5}
Schema :
“additionalProperties”: false,
“properties”: {
“edge_bits”: {
“default”: 29,
“description”: “Number of bits used for representing an edge in the Cuckoo Cycle problem. It affects both PoW generation (mining) and verification. WARNING: Changing this makes the node incompatible with the chain of other nodes in the network, do not change from the default unless you know what you are doing.”,
“type”: “integer”
“executable”: {
“default”: “mean29-generic”,
“description”: “Executable binary of the miner. Options are: “mean29-generic” (memory-intensive), “mean29-avx2” (memory-intensive, benefits from faster CPU supporting AVX2 instructions), “lean29-generic” (CPU-intensive, useful if memory-constrained), “lean29-avx2” (CPU-intensive, useful if memory-constrained, benefits from faster CPU supporting AVX2 instructions).”,
“type”: “string”
“extra_args”: {
“default”: “-t 1”,
“description”: “Extra arguments to pass to the miner executable binary. The safest choice is specifying no arguments i.e. empty string.”,
“type”: “string”
“hex_encoded_header”: {
“default”: false,
“description”: “Hexadecimal encode the header argument that is send to the miner executable. CUDA executables expect hex encoded header.”,
“type”: “boolean”
“nice”: {
“description”: “Miner process priority (niceness) in a UNIX fashion. Higher nice means lower priority. Keep it unset to inherit parent process priority.”,
“type”: “integer”
“required”: [
“type”: “object”
Reason : No extra properties allowed
Configuration error (validation_failed)

This is my epoch. yaml configuration. What’s wrong with it? 1066/5

port: 3115
external_port: 3015

dir: keys
peer_password: “”

port: 3013
port: 3113

port: 3014

beneficiary: “ak_JzUNavH8jFornCSUor5xaRYB4DEdgCxTFSVcY8daqNRJ3EaSE”
autostart: true
executable: cuda29
extra_args: “-E1”
instances: 5
edge_bits: 29
hex_encoded_header: true

persist: true
db_path: ./chain

network_id: ae_mainnet


[email protected]:~/multi_gpu$ make prod-build

=ERROR REPORT==== 4-Dec-2018::05:37:30 ===
Loading of /home/mining/multi_gpu/rebar3/rebar/ebin/rebar3.beam failed: badfile

=ERROR REPORT==== 4-Dec-2018::05:37:30 ===
beam/beam_load.c(1189): Error loading module rebar3:
mandatory chunk of type ‘Atom’ not found

escript: exception error: undefined function rebar3:main/1
in function escript:run/2 (escript.erl, line 757)
in call from escript:start/1 (escript.erl, line 277)
in call from init:start_it/1
in call from init:start_em/1
Makefile:320: recipe for target ‘internal-build’ failed
make: *** [internal-build] Error 127


You are trying to use the multi_gpu parameter instances on a node that is not compiled with multi_gpu support. Make sure you checkout and build the right branch.


It looks like you are using the wrong version of Erlang, which version do you have installed?


Hello hanssv ! I setup a ae node and running successful ,everything looks Ok, As I started the node with command “bin/epoch foreground " , when the node running ,it shows so much Ignoring peer address change from ...:3015.

What do it mean?” I was puzzled and asked. and did these tips influence me recieve rewards ??? Could you help me ? Thank very much~~


Those messages means that a peer has changed its IP, but we give this info far more often than we should. It will be fixed in an upcoming release… https://www.pivotaltracker.com/story/show/162392588

It does not influence miner reward.


That’s great~~ thanks for reply.