Manual installation using pre-built packages
The following setup is for a manual FIO API Node installation using pre-built packages.
Packages for Ubuntu 18.04
These packages are purpose-built to quickly bring up a node, have systemd integration, have logrotate, apparmor, compsec enabled, and have reasonable defaults in the config.
- Official releases: https://github.com/fioprotocol/fio/releases
Download and validate install packages
The FIO GPG signing key is available on keybase:
curl -s 'https://keybase.io/fiosec/pgp_keys.asc?fingerprint=0cfee764b06d009f7574a253c0e61f8441b6aad4' | gpg --import
Releases may be pulled from the Github release page or to retrieve the latest version, at the following URLs:
curl -sO https://bin.fioprotocol.io/mainnet/fioprotocol-3.4.x-latest-ubuntu-18.04-amd64.deb
curl -sO https://bin.fioprotocol.io/mainnet/fioprotocol-3.4.x-latest-ubuntu-18.04-amd64.deb.asc
Signature verification:
gpg --verify fioprotocol-3.4.x-latest-ubuntu-18.04-amd64.deb.asc fioprotocol-3.4.x-latest-ubuntu-18.04-amd64.deb
Should result in output similar to:
gpg: Signature made Thu 27 Aug 2020 08:22:06 PM UTC
gpg: using RSA key 0CFEE764B06D009F7574A253C0E61F8441B6AAD4
gpg: Good signature from "FIO Security <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 0CFE E764 B06D 009F 7574 A253 C0E6 1F84 41B6 AAD4
Remove existing history directories (optional):
This step should be performed only if you are upgrading from an older version and you are NOT running a History node.
cd /var/lib
sudo rm -fr fio/data fio/history fio/history_index
Install the release:
sudo apt install ./fioprotocol-3.4.x-latest-ubuntu-18.04-amd64.deb
rm fioprotocol-3.4.x-latest-ubuntu-18.04-amd64.deb
This will install the following files:
| Directory | File/Link | Type |
|---|---|---|
| /etc/apparmor.d/ | usr.local.bin.fio-nodeos | |
| /etc/apparmor.d/ | usr.local.bin.fio-wallet | |
| /etc/fio/nodeos/ | logging.json | |
| /etc/fio/nodeos/ | config.ini | |
| /etc/fio/nodeos/ | default-logging.json | |
| /etc/fio/nodeos/ | genesis-mainnet.json | |
| /etc/fio/nodeos/ | genesis-testnet.json | |
| /etc/fio/nodeos/ | mainnet-config.ini | |
| /etc/fio/nodeos/ | testnet-config.ini | |
| /etc/fio/nodeos/ | genesis.json | link |
| /etc/fio/nodeos/protocol_features | ||
| /etc/logrotate.d/ | fio-nodeos | |
| /etc/logrotate.d/ | fio-wallet | |
| /lib/systemd/system/ | fio-nodeos.service | |
| /lib/systemd/system/ | fio-wallet.service | |
| /usr/local/bin/ | clio | |
| /usr/local/bin/ | fio-nodeos | |
| /usr/local/bin/ | fio-nodeos-run | |
| /usr/local/bin/ | fio-wallet | |
| /usr/local/bin/ | cleos | link |
| /usr/local/bin/ | fio-cleos | link |
| /usr/local/bin/ | nodeos | link |
| /usr/local/share/fio/ | README | |
| /var/lib/fio/fio-wallet/ | config.ini | |
| /var/lib/fio/fio-wallet/fio-wallet | ||
| /var/log/fio/ | nodeos.log |
To Monitor AppArmor logging for issues
Inspect either the file ‘kern.log’ or ‘messages’ located in /var/log, i.e.:
tail -f /var/log/kern.log
To Disable an AppArmor profile
sudo ln -s /etc/apparmor.d/usr.local.bin.fio-nodeos /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/usr.local.bin.fio-wallet
Re-enable an AppArmor profile
sudo rm /etc/apparmor.d/disable/usr.local.bin.fio-nodeos
sudo apparmor_parser -r /etc/apparmor.d/usr.local.bin.fio-nodeos
Update fio-wallet environment
(Skip this step if you are not using fio-wallet to manage FIO keys for your users.)
fio-wallet (keosd)
This step is required if you are using fio-wallet(keosd) to manage FIO keys. As of release 3.0.0 keosd is known as fio-wallet. If you are using keosd to manage keys, you must update your server and scripts to use the new `/fio-wallet` directory and `fio-wallet.sock` naming.Rename the v2.0.0 wallet directory. The location of your eosio-wallet may be different depending on server configuration.
clio wallet stop
mv ~/eosio-wallet ~/fio-wallet
Replay from a snapshot, blocks.log, or V1 History archive (optional)
info
This step is optional to save time when syncing a node. If it is skipped, the node will sync from genesis and can take several hours.To save time on startup, your node may be bootstrapped with a snapshot of data from a running node. Refer to Nodeos Replay for instructions on replaying from a snapshot, blocks.log, or V1 History archive.
Configure nodeos settings
Edit the settings for nodeos:
sudo vi /etc/fio/nodeos/config.ini
P2P nodes are updated more frequently than the .deb package, if there are a large number of P2P nodes that are unreachable, it’s possible to get a list of healthy nodes from the FIO Mainnet Health page.
The default genesis file is for startup of a mainnet node. If running a testnet node, copy the testnet genesis configuration file into place:
sudo cp /etc/fio/nodeos/genesis-testnet.json /etc/fio/nodeos/genesis.json
V1 History configuration (optional)
If the light-history (v1 history) feature is needed, follow the V1 History configuration instructions.
Run nodeos
Enable nodeos daemon at runtime, and start:
sudo systemctl enable fio-nodeos
sudo systemctl start fio-nodeos
Block processing including synchronization will show in the logs:
tail -f /var/log/fio/nodeos.log