Parity

奇偶校驗節點神秘地自行關閉

  • November 30, 2018

我注意到我的 Parity 節點每隔 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://<somenode>@<somehost>
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://<somenode>@<somehost>
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

我已將我的 Parity 節點設置為服務,因此每次它神秘地關閉時,它都會再次啟動,但無論何時啟動,它都會繼續重做相同的過程,並且不會繼續下載其他塊。

如何修復這個靜默自動終止節點?

Parity 對完整節點的硬體建議是:

4GB RAM 和 SSD 驅動器以及至少 100GB 可用空間

您的評論表明您只使用了 1 GB 的 RAM,這對於獲得完整節點同步來說太少了。

嘗試執行輕客戶端時,您可能會更好地應對這些硬體限制:

輕節點

使用標誌 –light 執行輕節點不需要下載和執行整個區塊鏈的驗證。輕節點依賴全節點對等方來接收塊頭並驗證交易。因此,它對資源的要求遠低於完整節點。

建議使用具有單核 CPU、512MB RAM 和 128MB 可用空間的 HDD 的電腦或手機來執行輕節點。

引用自:https://ethereum.stackexchange.com/questions/63334