Tutorial: Mining AE on Ubuntu 18.04


#21

I am trying this in ubuntu18 and the miner is crashing with:

2018-10-24 23:12:44 =ERROR REPORT====
Failed to start Ranch listener internal in ranch_tcp:listen([{port,3013},{ip,{127,0,0,1}}]) for reason eaddrinuse (address already in use)

I stop apache2 and retry with no luck

This is my epoch.yaml, any ideas?


sync:
port: 3115
external_port: 3015

keys:
dir: keys
password: “(hidden)”

http:
external:
port: 3013
internal:
port: 3013

websocket:
internal:
port: 3114
channel:
port: 3014

mining:
beneficiary: “ak_(hidden)”
autostart: true
cuckoo:
miner:
executable: lean30
extra_args: “”
node_bits: 30
chain:
persist: true
db_path: ./my_db


New to mining Guidelines
#22

You have to use different ports for internal/external API listeners, try changing the section to:

http:
  external:
    port: 3013
  internal:
    port: 3113

#23

It worked, thanks much!


#24

That is funny, the tutorial used same ports for both in the sync part. are you saying it is possible in sync but not in http ?


#25

Yes, it’s OK with sync ports. Actually that’s it’s idea. I tried to explain it here: Top of local chain is empty


#26

Hi, I am considering to be part of test mining as well, but before I do, I like to get a perspective on the computing specs that I minimally need. I am planning to run it on an older computer with Linux on it. Thanks for any guidance on the Specs.


#27

Hello, I have executed the epoch and everything is working except synchronization. After 2 hours of running, when I check: http://127.0.0.1:3013/v2/blocks/top “height” was only 3

In epoch docs was mentioned that it should take only few minutes. What is the problem can it be because of my hardware performance ?

Thank You


#28

It is most likely a configuration problem, the hardware requirements for syncing the chain at this stage should be very low.

You should see errors in log/epoch_sync.log if there is something wrong.


#29

I found only:
[email protected]:~/tmp/node$ grep error log/epoch_sync.log
2018-11-30 10:41:21.280 [debug] <0.2813.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“3.0.86.27”>>,3015}: {error,timeout}
2018-11-30 10:45:49.594 [debug] <0.5824.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“34.209.38.2”>>,3015}: {error,timeout}
2018-11-30 10:53:19.436 [debug] <0.1338.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“35.177.192.219”>>,3015}: {error,timeout}
2018-11-30 10:54:50.008 [debug] <0.2524.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“3.0.86.27”>>,3015}: {error,timeout}
2018-11-30 10:57:49.455 [debug] <0.4530.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“35.177.165.232”>>,3015}: {error,timeout}
2018-11-30 11:50:20.340 [debug] <0.2266.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“35.177.212.38”>>,3015}: {error,timeout}
2018-11-30 11:54:50.528 [debug] <0.2496.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“3.17.17.128”>>,3015}: {error,timeout}
2018-11-30 12:16:41.244 [debug] <0.3484.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“3.0.221.40”>>,3015}: {error,timeout}
2018-11-30 12:54:50.126 [debug] <0.5132.0>@aec_peer_connection:handle_info:276 Failed to connected to {<<“54.214.159.45”>>,3015}: {error,timeout}

my config

sync:
port: 3115
external_port: 3015

keys:
dir: keys
peer_password: <>

http:
external:
port: 3013
internal:
port: 3113

websocket:
channel:
port: 3014

mining:
beneficiary: <>
autostart: true

chain:
persist: true
db_path: ./my_db

fork_management:
network_id: ae_uat


#30

You have to change

fork_management:
  network_id: ae_uat

into

fork_management:
  network_id: ae_mainnet

Or just remove it since ae_mainnet is the default.


#31

I have removed it from yaml file. Now I cant start node.
I found:
2018-11-30 13:52:35.934 [error] <0.1207.0>@aecore_app:start:25 Persisted chain has a different genesis block than the one being expected. Aborting


#32

Yes, that makes sense since you have been trying to sync with the testnet. You have to remove the database directory (./my_db).


#33

Great It is working now :slight_smile:

Thanks a lot for fast response.


#34

Hello one question regarding accounts When I use:
At the moment I am using Benneficiary account that was generated using Keys_gen.
But I alredy have one which I created for migrationpurposes using AirGap.
Cau I use this publick key as Benneficiary account ? If yes how can I set it up ? How can I regenerate keys and generated_keys directories?
Thanks


#35

There is no connection between the beneficiary and the generated_keys directory. You can put any public key/account as the beneficiary.


#36

Have you found a block? If yes can you share some log lines? You will find them at log/epoch_pow_cuckoo.log
just paste them here: https://github.com/Zwilla/BitCaine5_aeternity_miner/issues/new
thx