Klaytn Node Stop to Sync Issue: Removed the node without any response

We set up a self host klaytn node to sync the blocks with main net with below configure setting:

# cypress, baobab is only available if you don't specify NETWORK_ID.
NETWORK="cypress"
# if you specify NETWORK_ID, a private network is created.
NETWORK_ID=
PORT=32323
SERVER_TYPE="fasthttp"
SYNCMODE="full"
VERBOSITY=3
MAXCONNECTIONS=10
# txpool options setting
TXPOOL_EXEC_SLOTS_ALL=4096
TXPOOL_NONEXEC_SLOTS_ALL=4096
TXPOOL_EXEC_SLOTS_ACCOUNT=4096
TXPOOL_NONEXEC_SLOTS_ACCOUNT=4096
TXPOOL_LIFE_TIME="30m"
# rpc options setting
RPC_ENABLE=1 # if this is set, the following options will be used
RPC_API="rpc,admin,debug,klay,web3" # available apis: admin,debug,klay,miner,net,personal,rpc,txpool,web3
RPC_PORT=8551
RPC_ADDR="0.0.0.0"
RPC_CORSDOMAIN="*"
RPC_VHOSTS="*"
# ws options setting
WS_ENABLE=1 # if this is set, the following options will be used
WS_API="rpc,admin,debug,klay,web3" # available apis: admin,debug,klay,miner,net,personal,rpc,txpool,web3
WS_ADDR="0.0.0.0"
WS_PORT=8552
WS_ORIGINS="*"
# service chain options setting
SC_MAIN_BRIDGE=0 # if this is set, the following options will be used.
SC_MAIN_BRIDGE_PORT=50505
SC_MAIN_BRIDGE_INDEXING=0  # this option will be deprecated.
# Setting 1 is to enable options, otherwise disabled.
AUTO_RESTART=0
METRICS=1
PROMETHEUS=1
DB_NO_PARALLEL_WRITE=0
MULTICHANNEL=1
SUBPORT=$((PORT + 1)) # used for multi channel option
# discover options
NO_DISCOVER=0 # setting 1 to disable discovery
BOOTNODES=""
# Raw options e.g) "--txpool.nolocals"
ADDITIONAL="--gcmode archive --sendertxhashindexing --state.tries-in-memory 50 --state.trie-cache-limit 10240"
DATA_DIR = /var/klaytn/data
LOG_DIR=$DATA_DIR/logs

we can successfully sync the data until block number 135xxxxx, it looks like our klaytn node will stop running with below message:

INFO[12/30,09:24:08 Z] [34] Removed the node without any response Discover=Simple StorageName=BN NodeID=94cc15e2014b8658 NodeType=BN

If we restart the klaytn node, it will continue to work but just after a few minutes, it will stop again and the logs are same.
Please refer below screenshot for reference and share any suggestion if you have, thanks!

@bao1018

Hi, sorry to late reply.
Are the issues still unresolved?

If so, please share your Hardware Spec (Cpu, Ram, IOPS), OS info, and binary version of KEN you are using with us.

As just to clarify the issue, does node always stop after that message “Removed the node without any response”?.
Is it correct situation?