BCSkill (Block chain skill )
区块链中文技术社区

只讨论区块链底层技术
遵守一切相关法律政策!

安装EOS 数据获取API Server EOSTracker-API

获取源代码

git clone https://github.com/EOSEssentials/EOSTracker-API.git

开始编译

cd EOSTracker-API
composer install

开始运行

php bin/console server:run


常见问题

  • ubuntu add-apt-repository command not found解决方法
    apt-get install software-properties-common
  • Ubuntu PHP升级到最新版本
    add-apt-repository ppa:ondrej/php
    apt-get update
    apt-get upgrade php
  • The requested PHP extension ext-apcu * is missing from your system. Install or enable PHP's apcu extension
    apt-get install php7.2-apcu //修改为当前版本  php -v
  • The requested PHP extension ext-intl * is missing from your system. Install or enable PHP's intl extension
    apt-get install php7.2-intl //修改为当前版本  php -v
  • The requested PHP extension ext-mbstring * is missing from your system. Install or enable PHP's mbstring extension
    apt-get install php7.2-mbstring //修改为本地版本  php -v
  • The requested PHP extension ext-redis * is missing from your system. Install or enable PHP's redis extension
    apt-get install php7.2-redis //修改为本地版本  php -v
  • Installation request for symfony/symfony v3.4.11 -> satisfiable by symfony/symfony[v3.4.11].
    symfony/symfony v3.4.11 requires ext-xml * -> the requested PHP extension xml is missing from your system.
       apt-get install php7.2-xml //修改为本地版本 PHP -v

EOSIO各版本含义

  • Dawn = Alpha
  • V1.. = Beta
  • EOS Mainnet 版本 = Stable

Alpha:是内部测试版,一般不向外部发布,会有很多Bug.一般只有测试人员使用。Beta:也是测试版,这个阶段的版本会一直加入新的功能。在Alpha版之后推出。Stable:稳定版;来自预览版本释出使用与改善而修正完成。

--replay-blockchain does not work

try --hard-replay-blockchain
参考:github

更新EOS 1.1.0 后无法RPC访问

更新 ~/.local/share/eosio/nodeos/config/config.ini
修改或添加
http-validate-host=false

或者 nodeos 启动时添加参数 --http-validate-host=false

如何正常停止nodeos?(database dirty flag set (likely due to unclean shutdown): replay required)

kill 命令再次执行时会导致以下错误。

pkill -9 nodeos or kill -9 {pid}
database dirty flag set (likely due to unclean shutdown): replay required

当重新运行nodeos时,必须使用--replay-blockchain命令忽略它。

让我们安全的结束nodeos 进程

This appears to be two different issues.

Startup after a crash or ungraceful shutdown nearly always fails due to corruption of the boost shared memory cache of the in-memory database. --resync is required to clean up the mess.

For normal shutdown, never kill with -9. Always use either the default (no argument) signal (which is SIGTERM) or SIGINT. Numerically, those are 15 and 2, respectively.

pkill nodeos | Safe
pkill -15 nodeos | Safe
pkill -2 nodeos | Safe
pkill -TERM nodeos | Safe
pkill -SIGTERM nodeos | Safe
pkill -INT nodeos | Safe
pkill -SIGINT nodeos | Safe
pkill -9 nodeos | Not Safe
pkill -KILL nodeos | Not Safe
pkill -SIGKILL nodeos | Not Safe

The core dump is a different problem. That looks like a corrupted network packet, specifically a signed_block_summary. Summary messages are being eliminated from the protocol, so this particular error will no longer be possible soon.

参考自:github