IoP Full Node Installer is a tool that helps installing the following components of IoP network infrastructure:
- IoP Core Wallet
- IoP LOC Server
- IoP CAN Server
- IoP Profile Server
In the current version of the installer, the installation process can not be fully automatic. Manual interaction from the user is required especially for opening several firewall ports for installed servers.
Download an unpack the latest full node installer binary release for your operating system. You should find a single script and a single folder inside. All you need to do is run the script and then follow the instructions on the screen.
Windows users need to execute the script with administrator privileges.
Linux users need to execute the script using sudo. Linux users may execute the script when they are logged in as root, but they should avoid
running the script under sudo su as this will produce wrong file access rights in many cases.
The full node installer does not check that every operation completes successfully or that all user inputs are actually valid. For example when the installer runs the servers for the first time, it does not check whether they start start successfullly and work as expected. Another example is when the full node installer installs scheduled tasks on Windows, it asks for a password and does not verify if the entered password is correct.
Things can go wrong especially during the first start of the servers (it is known that CAN server sometimes fails for some reason when started for the first time). This behavior can be improved in the future, but until then, you can do the following:
- there should be 4 server processes running once the installer is complete - IoPd, iop-locnet, ipfs, and ProfileServer,
- if not, you can try to start the servers that are missing - use Task Scheduler on Windows and init.d scripts on Linux, or simply reboot the machine,
- it is always safer to use default values in the installer,
- except for the CAN server, all components create logs in their application data folders, you can inspect the logs to find the problem,
- on Linux, it is safer to run the installation script as non-root with sudo, rather than as root.
If the installation fails, please find the log file in Logs directory that will be created in the installer folder. Analyzing the log will help you identify and understand the problem.
Copyright © 2017 Libertaria Corp., Decentralized Society Foundation, IoP Ventures LLC
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
See COPYING for more information or see http://www.gnu.org/licenses/.