奇偶校验节点神秘地自行关闭。

Question

我注意到我的奇偶节点每隔15分钟就会自动关闭一次。

我使用以下命令运行它：

/usr/bin/parity --jsonrpc-interface=all --jsonrpc-port=8545 --log-file=/root/parity/parity.log

下面是日志文件的快照：

2018-11-30 13:18:39 UTC Starting Parity-Ethereum/v2.1.7-stable-126208c-20181128/x86_64-linux-gnu/rustc1.30.1
2018-11-30 13:18:39 UTC Keys path /root/.local/share/io.parity.ethereum/keys/ethereum
2018-11-30 13:18:39 UTC DB path /root/.local/share/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d
2018-11-30 13:18:39 UTC State DB configuration: fast
2018-11-30 13:18:39 UTC Operating mode: active
2018-11-30 13:18:39 UTC Configured for Foundation using Ethash engine
2018-11-30 13:18:41 UTC Removed existing file '/root/.local/share/io.parity.ethereum/jsonrpc.ipc'.
2018-11-30 13:18:42 UTC Updated conversion rate to Ξ1 = US$113.46 (41969896 wei/gas)
2018-11-30 13:18:46 UTC Public node URL: enode://@
2018-11-30 13:18:51 UTC Snapshot initializing (5 chunks restored)  #2427249   15/25 peers     80 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:19:01 UTC Snapshot initializing (13 chunks restored)  #2427249   20/25 peers     80 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:19:11 UTC Snapshot initializing (19 chunks restored)  #2427249   22/25 peers     80 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:19:21 UTC Snapshot initializing (25 chunks restored)  #2427249   23/25 peers     80 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:19:31 UTC Snapshot initializing (29 chunks restored)  #2427249   23/25 peers     80 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:19:41 UTC Snapshot initializing (35 chunks restored)  #2427249   26/50 peers     80 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:19:51 UTC Snapshot initializing (40 chunks restored)  #2427249   25/25 peers      1 MiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:20:01 UTC Snapshot initializing (45 chunks restored)  #2427249   28/50 peers      1 MiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:20:11 UTC Snapshot initializing (49 chunks restored)  #2427249   30/50 peers      1 MiB chain  224 MiB db  0 bytes queue   22 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:25:50 UTC Starting Parity-Ethereum/v2.1.7-stable-126208c-20181128/x86_64-linux-gnu/rustc1.30.1
2018-11-30 13:25:50 UTC Keys path /root/.local/share/io.parity.ethereum/keys/ethereum
2018-11-30 13:25:50 UTC DB path /root/.local/share/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d
2018-11-30 13:25:50 UTC State DB configuration: fast
2018-11-30 13:25:50 UTC Operating mode: active
2018-11-30 13:25:50 UTC Configured for Foundation using Ethash engine
2018-11-30 13:25:52 UTC Removed existing file '/root/.local/share/io.parity.ethereum/jsonrpc.ipc'.
2018-11-30 13:25:53 UTC Updated conversion rate to Ξ1 = US$113.61 (41914484 wei/gas)
2018-11-30 13:25:57 UTC Public node URL: enode://@
2018-11-30 13:25:57 UTC Snapshot initializing (2 chunks restored)  #2427249   15/25 peers     80 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:26:07 UTC Snapshot initializing (10 chunks restored)  #2427249   15/25 peers     80 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:26:17 UTC Snapshot initializing (16 chunks restored)  #2427249   19/25 peers    781 KiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:26:27 UTC Snapshot initializing (22 chunks restored)  #2427249   22/25 peers      3 MiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:26:37 UTC Snapshot initializing (27 chunks restored)  #2427249   22/25 peers      3 MiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:26:47 UTC Snapshot initializing (33 chunks restored)  #2427249   24/25 peers      3 MiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2018-11-30 13:26:57 UTC Snapshot initializing (38 chunks restored)  #2427249   27/50 peers      3 MiB chain  224 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    0 req/s,    0 µs

我已经将奇偶校验节点设置为服务，所以每次它神秘地关闭时，它都会再次启动，但是每当它启动时，它就会继续重做相同的进程，而不会继续下载其他块。

如何修复这个无声的自终止节点？

Answer 1

硬件建议来自完整节点的奇偶校验是：

4GB内存和SSD驱动器，以及至少100 4GB的空闲空间

您的评论表明，您只使用1GB的RAM，这是太少，以获得一个完整的节点同步。

您最好使用这些硬件限制来运行一个轻量级客户端：

Light节点使用标志运行轻量级节点--轻型不需要下载并执行整个块链的验证。轻型节点依赖于完全节点对等点来接收块头和验证事务。因此，它比一个完整的节点所需要的资源少得多。建议使用具有单核CPU、512 to和128 to空闲空间的计算机或移动电话来运行轻节点。