4
1 Megabyte.
Block producers can change that, so it's dynamic and it doesn't need a hard fork.
3
It looks like the nodeos process is still running judging by this output:
std::exception::what: bind: Address already in use
(your current nodeos process is trying to use the same address/port that's being used by the previous process that never exited)
Usually when this happens to me I find the process number with:
ps aux | grep nodeos
This will give ...
1
This is not a direct way, but you can check whether ***_api_plugin is activated by calling /v1/node/get_supported_apis. Run the next command in command line (in the case of local testnet). You should stop nodeos first to toggle plugin activation.
curl http://127.0.0.1:8888/v1/node/get_supported_apis
1
It looks like you ran out of disk space, the chain is getting large!
If you just want to test getting a node up and running, you could restore from a snapshot rather than using a blocks backup. With ansible, set up a node with:
ansible-playbook eos.yml
ansible-playbook mainnet.yml
Then follow the snapshot instructions from: https://eosnode.tools/...
1
I would look into EOS Rio's Hyperion Solution for producing a light full history node. This could help achieve your goal of reducing the node's storage requirements as well as decreasing the syncing time.
From their announcement:
Changing format and cutting data redundancies reduces database size in
about 85%, from almost 5 Tb to approximately 650 Gb. ...
1
The built-in keypair of eosio is set as follows. You can also solve this problem by importing this key.
5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
This keypair is created automatically when you create a wallet.
I do not use v1.0.5, so I do not know if this is the case.
1
It sounds like you are not trying to connect to the main net which is a production EOSIO network with 21 block producers with BP's like EOS New York, Canada, etc.
If you're trying to run a single node test net I highly recommend using the Docker image that's provided by Block One, it's fantastic for development purposes and if you screw anything up you can ...
Only top voted, non community-wiki answers of a minimum length are eligible
Related Tags
single-node × 12nodeos × 6
testnet × 4
history × 3
cleos × 2
blocks × 2
transactions × 1
eosjs × 1
permissions × 1
mainnet × 1
keosd × 1
eosio.system × 1
node × 1
plugin × 1
full-node × 1
irreversible × 1