Why does synchronization stop intermittently?

[junghyun0783]

sepolia testnet sync stops intermittently, and I don't know the cause.
It runs normally, but it keeps stopping intermittently, and when I turn it off and on, the sync starts again.

The causes I guess are

1. Hardware problem
2. config setting problem
   I guess the above two...

I leave open the possibility that it is a hardware problem.
Spec.
os: windows
cpu: Xeon(R) CPU E5-2620
memory: 64G
hard: 2TB (no ssd)
What could be the problem?

this is my commands
geth : cmd /k geth -syncmode "snap" --http.api admin,eth,debug,net,txpool,personal,web3,engine -datadir ".\dataSepolia" -http --http.port 20201 --http.addr 0.0.0.0 --nat "any" --rpc.allow-unprotected-txs --snapshot=false -ipcdisable --au thrpc.jwtsecret ../consensus/jwt_sepolia.hex --authrpc.vhosts="*" --authrpc.addr=0.0.0.0 --lightkdf --cache 16384

sepolia prysm : prysm.bat beacon-chain --execution-endpoint=http://localhost:8551 --sepolia --datadir=./prysm_data_sepolia --jwt-secret=../jwt_sepolia.hex --rpc-host=0.0.0.0 --grpc-gateway-host=0.0.0.0 --genesis-state=sepolia_genesis.ssz --suggested-fee-recipient=0x67CDB8344FFCa7aaaeda9e7a4F4f1A9 cb4D1FC64

plz help me!

[jwasinger]

Can you post a snippet from the logs when it stops syncing?

[junghyun0783]

@jwasinger
I can't check the log right now...
I think this problem will occur again soon.

Is there a problem with the geth or prysm commands?

[jwasinger]

--au thrpc.jwtsecret well this should prevent geth from starting up. But given that you said it was syncing, it sounds like it started up correctly (maybe you pasted the command incorrectly).

[junghyun0783]

@jwasinger
Yes yes, it's a typo when you "paste" now.
Currently, it's working normally by entering "--authrpc.jwtsecret".
You're saying there's no problem with the command....
Then, does that mean there's no problem with the hardware?

[jwasinger]

I'm saying that if the node is syncing (even intermittently), that is a good indication that you have set it up correctly.

I have no clue what the underlying issue is, and logs would be a good start to try and diagnose what is going on..