search

openethereum / parity-ethereum

The fast, light, and robust client for Ethereum-like networks.
Other
6.83k stars 1.69k forks source link

Parity Kovan Stopped Suddenly #11599

Open mo-masmoudi opened 4 years ago

mo-masmoudi commented 4 years ago

Config.toml

[parity]
chain = "kovan"
base_path = "/opt/share/io.parity.ethereum"
[network]
warp = false

Actual

My node is well synced and works.

Strange Behaviour

I started my kovan node as a user service without any problems on 05/03, and suddenly it stopped for no reason on 11/03.

Mar 11 18:50:52 kovan01 parity[12585]: 2020-03-11 18:50:52    24/25 peers      6 MiB chain   97 MiB db  0 bytes queue   51 MiB sync  RPC:  0 conn,    0 req/s,   20 µs
Mar 11 18:50:54 kovan01 parity[12585]: 2020-03-11 18:50:54  Snapshot: 418001 accounts, 0 blocks, 375190510 bytes
Mar 11 18:50:57 kovan01 parity[12585]: 2020-03-11 18:50:57  Imported #17320516 0x8440…0fce (0 txs, 0.00 Mgas, 2 ms, 0.58 KiB)
Mar 11 18:51:00 kovan01 parity[12585]: 2020-03-11 18:51:00  Imported #17320517 0x74f6…e228 (0 txs, 0.00 Mgas, 2 ms, 0.58 KiB)
Mar 11 18:51:04 kovan01 parity[12585]: 2020-03-11 18:51:04  Imported #17320518 0x3e5d…3ae1 (2 txs, 0.52 Mgas, 31 ms, 0.89 KiB)
Mar 11 18:51:05 kovan01 parity[12585]: 2020-03-11 18:51:05  Snapshot: 418001 accounts, 0 blocks, 375190510 bytes
Mar 11 18:51:08 kovan01 parity[12585]: 2020-03-11 18:51:08  Imported #17320519 0x6a4a…572a (1 txs, 0.24 Mgas, 4 ms, 1.50 KiB)
Mar 11 23:17:19 kovan01 parity[12585]: 2020-03-11 23:17:19  Took a snapshot at #17320000 of 2265424 accounts
Mar 11 23:17:19 kovan01 parity[12585]: 2020-03-11 23:17:19  produced 1929 state chunks and 1 block chunks.
Mar 11 23:17:19 kovan01 parity[12585]: 2020-03-11 23:17:19  Finished taking snapshot at #17320000, in 17651s

Yesterday, I restarted the user service (restarted the node) and that launches synchronization again, but an other time the node was stopped

Apr 02 23:08:16 kovan01 parity[1119]: 2020-04-02 23:08:16  Imported #17696563 0x2799…6979 (1 txs, 0.13 Mgas, 6 ms, 0.81 KiB)
Apr 02 23:08:19 kovan01 parity[1119]: 2020-04-02 23:08:19  Snapshot: 690653 accounts, 0 blocks, 1705170489 bytes
Apr 02 23:08:20 kovan01 parity[1119]: 2020-04-02 23:08:20  Imported #17696564 0xbf2e…038f (0 txs, 0.00 Mgas, 2 ms, 0.58 KiB)
Apr 02 23:08:27 kovan01 parity[1119]: 2020-04-02 23:08:27  Imported #17696565 0x5ab7…011a (0 txs, 0.00 Mgas, 2 ms, 0.58 KiB)
Apr 02 23:08:29 kovan01 parity[1119]: 2020-04-02 23:08:29  Snapshot: 690653 accounts, 0 blocks, 1705170489 bytes
Apr 02 23:08:32 kovan01 parity[1119]: 2020-04-02 23:08:32  Imported #17696566 0xde49…3048 (4 txs, 0.53 Mgas, 17 ms, 1.64 KiB)
Apr 02 23:08:36 kovan01 parity[1119]: 2020-04-02 23:08:36  Imported #17696567 0x0089…ea5b (1 txs, 0.07 Mgas, 7 ms, 0.72 KiB)
Apr 03 03:14:07 kovan01 parity[1119]: 2020-04-03 03:14:07  Took a snapshot at #17695000 of 2316294 accounts
Apr 03 03:14:07 kovan01 parity[1119]: 2020-04-03 03:14:07  produced 1953 state chunks and 1 block chunks.
Apr 03 03:14:07 kovan01 parity[1119]: 2020-04-03 03:14:07  Finished taking snapshot at #17695000, in 22015s

So, I restarted the user service an other time, for now, it works fine, but I want to know why the node did stopped and how to prevent such behaviour in the future.

Thank you.

jleeh commented 4 years ago

I'm seeing the same issue. I've had 4 separate instances seize up without any log output, while any API requests during that time indefinitely time out. When the instance seizes up, you can leave it forever and it will not get any blocks in or serve API requests.

Like @DalyIng, a restart fixed the issue.

Same version: Parity-Ethereum/v2.7.2-stable-2662d19-20200206/x86_64-unknown-linux-gnu/rustc1.41.0

kevinibt commented 4 years ago

I have been seeing this behavior as well. Been running OE 3.0.1 on an AWS Debian Linux instance. My node is synched. So far, the node stops operating, my OS is hung and I have no recourse but to restart. This happened 3 times over the course of 5 days.