Archive node is not syncing for >24 hours (stuck at block #993996)

[ArseniiPetrovich]

• Parity Ethereum version: 2.4.5, 2.4.7
• Operating system: Linux
• Installation: pre-built binary
• Fully synchronized: no
• Network: Ethereum Mainnet
• Restarted: yes

Parity config:

[parity]
base_path = "parity_data"

[network]
reserved_peers="bootnodes.txt"
allow_ips = "all"
warp = false
max_peers = 30

[rpc]
apis = ["web3", "eth", "net", "parity", "traces"]
processing_threads = 50
server_threads = 200
port = 8545
interface = "0.0.0.0"

[websockets]
port = 8546
interface = "0.0.0.0"
max_connections = 1000
apis = ["web3","eth","net","parity", "pubsub", "traces"]
origins = ["all"]
hosts = ["all"]

[ui]
disable = true

[snapshots]
disable_periodic = true

[footprint]
tracing = "on"
pruning = "archive"
cache_size = 65536

[misc]
log_file = "/data/logs/parity.log"

Expected behavior: Parity slowly sync all the blockchain data
Actual behavior: Parity stuck on block #993996

The logs are:

Jun 19 12:40:29 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:40:29 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µs
Jun 19 12:40:34 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:40:34 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µs
Jun 19 12:40:39 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:40:39 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µs
Jun 19 12:40:44 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:40:44 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µs
Jun 19 12:40:49 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:40:49 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µs
Jun 19 12:40:54 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:40:54 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µs
Jun 19 12:40:59 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:40:59 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µs
Jun 19 12:41:04 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:41:04 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µs
Jun 19 12:41:09 ip-10-0-0-99.poa.internal parity[17243]: 2019-06-19 12:41:09 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 t…   13 µ

[ArseniiPetrovich]

I believe this might also be related:

• Background verifier sometimes goes back #9300
• OverlayDB #7

2019-06-19 16:34:06 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed     #8666   20/25 peers     80 KiB chain  0 bytes db  0 bytes queue   36 MiB sync  RPC:  1 conn,    0 req/s,   16 µs
2019-06-19 16:34:11 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed      #254   21/25 peers     80 KiB chain  0 bytes db  0 bytes queue   28 MiB sync  RPC:  1 conn,    1 req/s,   16 µs
2019-06-19 16:34:16 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed    #17410   22/25 peers     80 KiB chain  0 bytes db  0 bytes queue   41 MiB sync  RPC:  1 conn,    0 req/s,   16 µs
2019-06-19 16:34:21 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed      #221   20/25 peers     80 KiB chain  0 bytes db  0 bytes queue   28 MiB sync  RPC:  1 conn,    1 req/s,   16 µs
2019-06-19 16:34:26 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed      #118   19/25 peers     80 KiB chain  0 bytes db  0 bytes queue   28 MiB sync  RPC:  1 conn,    1 req/s,   16 µs
2019-06-19 16:34:31 UTC Syncing  #993996 0x61d6…de17     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed      #131   23/25 peers     80 KiB chain  0 bytes db  0 bytes queue   28 MiB sync  RPC:  1 conn,    1 req/s,   16 µs

I'm facing the issue with random changing of the logs verified at background.

[ArseniiPetrovich]

We migrated to geth, so no chance to track is the issue still persists after #10772. Thanks.