[Node Operator Question] OP-Geth not showing relevant messages in Log

[gflow33]

Are you running the most up to date node software?

• Yes

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I want to upgrade from v1.101411.7 to v1.101500.0 but I cannot find the messages required to determine if I should upgrade in the logs. When I shut opgeth down, my logs look like this

As part of the steps I am supposed to see Persisting dirty state to disk and layer after shutting down.

Steps to Reproduce

Shutdown op geth v1.101411.7 and monitor Logs

Which component is affected?

• op-geth
• op-node
• Other

Expected vs. Actual Behavior

I expect to see these messages in the log after shutting down Persisting dirty state to disk and layer
vs
Not seeing these messages

Environment Details

• Ubuntu 22.04 LTS
• CPU - AMD EPYC 7313P
• RAM - 32GB
• SSD - 6.8TB

Protocol Information

• op-geth - v1.101411.7
• op-node - v1.10.3
• optimism sepolia
• 0xaa37dc
• Ethereum Sepolia

Node Logs

Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.375] Imported new potential chain segment     number=23,736,157 hash=f1e91c..35823b blocks=1 txs=2  mgas=0.586  elapsed=3.403ms     mgasps=172.021  triedirty=0.00B
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.376] Chain head was updated                   number=23,736,157 hash=f1e91c..35823b root=4c63df..c321e7 elapsed="390.207µs"
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.407] Got interrupt, shutting down...
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.407] HTTP server stopped                      endpoint=[::]:8545
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.407] HTTP server stopped                      endpoint=[::]:8546
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.407] HTTP server stopped                      endpoint=127.0.0.1:8551
Feb 11 11:54:14 juju-95ecee-0 systemd[1]: Stopping op-geth Client...
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.407] IPC endpoint closed                      url=/home/op/.datadir/geth.ipc
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.930] Ethereum protocol stopped
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.931] Transaction pool stopped
Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.931] Blockchain stopped
Feb 11 11:54:18 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:18.546] Looking for peers                        peercount=0 tried=169 static=0
Feb 11 11:54:22 juju-95ecee-0 systemd[1]: opgeth.service: Deactivated successfully.
Feb 11 11:54:22 juju-95ecee-0 systemd[1]: Stopped op-geth Client.
Feb 11 11:54:22 juju-95ecee-0 systemd[1]: opgeth.service: Consumed 12min 2.130s CPU time.

Troubleshooting Attempts

I have allowed to run for longer before shutting down to see if that influences the logs

Additional Information

No response

Feedback

No response

[imtipi]

I expect to see these messages in the log after shutting down Persisting dirty state to disk

Feb 11 11:54:14 juju-95ecee-0 op-geth[1879297]: INFO [02-11|11:54:14.375] Imported new potential chain segment number=23,736,157 hash=f1e91c..35823b blocks=1 txs=2 mgas=0.586 elapsed=3.403ms mgasps=172.021 triedirty=0.00B

but you don't have triedirty needs to save,can to try shutdown when triedirty isn't zero?

[gflow33]

How can I determine if I can upgrade to the latest version then?

[imtipi]

How can I determine if I can upgrade to the latest version then?

try shutdown when triedirty isn't zero?

[gflow33]

I have been running opgeth for quite sometime and the size of triedirty is still 0, which I have come to understand might be the size of the state that needs to be updated from the imported blocks? So given this current situation with the assumption that it will always be 0.00B for my node, how then do I upgrade my node. And also what conditions will warrant the size changing assuming this is also normal behavior?

[Chomtana]

I think you have to upgrade to exactly version v1.101411.8 first.

[gflow33]

I have been running v1.101411.8 for a while and triedirty from the logs is still 0.00B and I still do not know if seeing the Persisting dirty state to disk and buffer_layers message after shutdown is absolutely necessary before upgrading. Also I see the release notes mention full nodes, I run an archive node for both mainnet and sepolia, should I expect different behaviour?

Edit: I just came across this release https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101500.0 and since I run an archive node these steps are unnecessary. Thank you for your responses