[Node Operator Question] stopped listening network address

[DaraDoyoung]

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

op-node stopped after leaving this log:

t=2023-12-23T06:58:31+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x1c0c20ff9bcbbef92a2a63b4d05d1468aedb3922083b3f556c1337c831e63cac:113857967
t=2023-12-23T06:58:31+0000 lvl=info msg="Sync progress"                          reason="unsafe payload from sequencer"        l2_finalized=0x7462a987af9691f4e3addcf71f259dd517f4af80443ef6376f2b49dc11cefc85:113857207 l2_safe=0x1c3626b8b68600aa27528d12bc99fa27c2910ae65bb88d2f842bf018d8567117:113857957 l2_unsafe=0x1c0c20ff9bcbbef92a2a63b4d05d1468aedb3922083b3f556c1337c831e63cac:113857967 l2_time=1,703,314,711 l1_derived=0xd03155112c89c6bcdf0da086b0cda8632ec28e981d34859b97212b62c67a53b8:18846881
t=2023-12-23T06:58:32+0000 lvl=info msg="stopped listening network address"      addr=/ip4/0.0.0.0/tcp/9222
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAm7UoHprg8qFre4zHfRv4Nmrr3Ugg4moXqYZwRRFNgufPQ addr=/ip4/65.109.88.121/tcp/21367
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAmSWN6QAnqpwmZCWuXYfuWBfyBzkg8L8naAVbH5CoUBMxq addr=/ip4/87.117.243.29/tcp/9003
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAkudScb74GPGx87UYXQ7zbHJeMTEnYrrdBYeTb3tUta77U addr=/ip4/47.104.64.197/tcp/9222
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAkznTF6tHNtLQSwF8U8SRXE97HqjKGVU8h7kcG8hn2XFv3 addr=/ip4/15.204.212.177/tcp/9222
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAkudU3yZyjdDGfxoPNqz1XNLiEdjhREgQqw6yFhD7JuDsh addr=/ip4/18.177.241.6/tcp/9222
...
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAmABWpMiSz7hrTY1VCvcMTivnuKvtnmHgngvZuL9zXhPHs addr=/ip4/137.220.40.10/tcp/9222
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAkzHdvxeF4kS4ajqP71ZKwwFRXoRYM4nfJb8R7Ry14QUgW addr=/ip4/176.9.111.210/tcp/9222
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAmQ6c2TAvz7qUcouCepUSfSN1hStmWaVDTxbS4b98Dyvrz addr=/ip4/204.29.146.5/tcp/9222
t=2023-12-23T06:58:32+0000 lvl=info msg="disconnected from peer"                 peer=16Uiu2HAkyzJuWiJnGnPesVnjMH2ALomge2AbBMB6ujugNbkfc6gG addr=/ip4/13.124.109.29/tcp/9222
t=2023-12-23T06:58:32+0000 lvl=info msg="stopped peer discovery"```

op-geth stopped as op-node stopped. 
op-geth log:

INFO [12-23|06:58:31.240] Chain head was updated number=113,857,967 hash=1c0c20..e63cac root=93ca73..8f6330 elapsed="337.237µs"
INFO [12-23|07:11:53.962] Writing clean trie cache to disk path=/home/ubuntu/data/op-geth-data/geth/triecache threads=1
INFO [12-23|07:11:53.978] Regenerated local transaction journal transactions=0 accounts=0
INFO [12-23|07:11:56.402] Persisted the clean trie cache path=/home/ubuntu/data/op-geth-data/geth/triecache elapsed=2.439s

why would this happen with op-node?

### Protocol Description

optimism mainnet

$ op-geth version
Geth
Version: 0.1.0-unstable
Git Commit: 13ee9ab9153baee7e4169c9a265eeb76aa440c86
Upstream Version: 1.11.2-stable
Architecture: arm64
Go Version: go1.20.2
Operating System: linux
GOPATH=
GOROOT=/usr/local/go

op-node --version
op-node version v0.0.0-89ed69d8-1687165076

### Node Logs

_No response_

### Additional Information

_No response_

### Feedback

_No response_

[Chomtana]

You shouldn't use op-node v0.0.0

op-node that works with op mainnet needs to be at least v1.3.0

You should try op-node v1.4.0 and latest op-geth
https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.4.0

[sbvegan]

If the op-node was built from source, the version is responds with isn't right. Its a known bug. However, it still looks old, especially because op-geth has an older commit hash.

Depending on the network you're running, our node software minimum release version can be found on the Software Releases page of the docs. You'll want to stay up to date to ensure things are working as expected.

If you upgrade and still run into an issue. Please feel free to re-open this discussion.

[github-actions[bot]]

Hey @DaraDoyoung, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community.