v1.3.1-beta stuck, updated from v1.3.0

[tebeletbl]

i just tried to update my geth from v1.3.0 to v.1.3.1

but stuck here

[CocoStarZ]

could you pls provide more info like your start cmd? besides, are you able to run 1.2.13?

[tebeletbl]

1.2.13 working just fine, i tried 1.3.0 but sometimes misses few pending tx, then i updated to 1.3.1 and node wont start, now i downgraded to 1.2.13 since 1.3.1 wont start and 1.3.0 seems unstable

[weiihann]

I just tried starting up a new node with v1.3.1-beta and it works fine. Perhaps there are some configurations previously that caused the issue. Can you provide the following details:

1. Node start-up command
2. Logs with trace enabled (i.e. --verbosity=5)

[tebeletbl]

this is my start up command
for 1.3.0 and 1.2.13, is there anything i need to change for 1.3.1 ?
./geth_linux --config ./config.toml --datadir ./mainnet --cache 48000 --rpc.allow-unprotected-txs --txlookuplimit 0 --http --maxpeers 850 --ws --syncmode=full --snapshot=true --tries-verify-mode=none --pruneancient=true --diffblock=5000

[weiihann]

can you try to run it again with --verbosity=5 and show the logs?

[tebeletbl]

Nov 13 15:21:01 mine2 bash[55126]: Fatal: Could not open database: open /home/geth/mainnet/geth/chaindata/ancient/bodies.cidx: no such file or directory
Nov 13 15:21:01 mine2 systemd[1]: geth.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 15:21:01 mine2 systemd[1]: geth.service: Failed with result 'exit-code'.

[tebeletbl]

thanks, waiting for next update