Geth doesnt recognize beacon client connected

[Demontager]

I'm trying to setup ETH test node using the latest Geth/v1.14.11-stable-f3c696fa and prysm beacon-chain-v5.1.2-modern-linux-amd64

To start geth i do

geth --sepolia --datadir /home/dem/eth_node/data --syncmode "snap" --http --http.addr "0.0.0.0" --http.api eth,net,engine,admin --http.corsdomain "http://localhost, http://192.168.1.0/24" --authrpc.jwtsecret /home/dem/eth_node/data/geth/jwtsecret

For beacon

beacon-chain-v5.1.2-modern-linux-amd64 --datadir=/home/dem/eth_node/consensus --sepolia --rpc-host 0.0.0.0 --execution-endpoint=http://localhost:8551 --jwt-secret=/home/dem/eth_node/data/geth/jwtsecret --genesis-state=/home/dem/eth_node/genesis.ssz --suggested-fee-recipient=0xbe8e1979048F5f8A084De1e7A26e770AA1d04fbe

And beacon logs says that it successfully connected to geth

[2024-11-15 22:32:25]  INFO execution: Finished reading JWT secret from /home/dem/eth_node/data/geth/jwtsecret
[2024-11-15 22:32:25]  INFO flags: Running on the Sepolia Beacon Chain Testnet
[2024-11-15 22:32:25]  INFO node: Default fee recipient is set to 0xbe8e1979048F5f8A084De1e7A26e770AA1d04fbe, recipient may be overwritten from validator client and persist in db. Default fee recipient will be used as a fall back
[2024-11-15 22:32:25]  INFO node: Checking DB databasePath=/home/dem/eth_node/consensus/beaconchaindata
[2024-11-15 22:32:25]  INFO db: Opening Bolt DB path=/home/dem/eth_node/consensus/beaconchaindata/beaconchain.db
[2024-11-15 22:32:25]  INFO genesis: Loading genesis state from disk. hash=0x01ab266308c8e3cd787be984e1f79251c6fcd8ea1444e7afb18cbbdde69ddce0
[2024-11-15 22:32:25]  INFO node: Deposit contract address=0x7f02C3E3c98b133055B8B348B2Ac625669Ed295D
[2024-11-15 22:32:25]  INFO filesystem: Blob filesystem cache warm-up complete. elapsed=161.861µs
[2024-11-15 22:32:25]  INFO p2p: Running node with peer id of 16Uiu2HAmFg1VAC7x7USE9aX2jymWUSp8F7vcUFaf19ZN6eSyMazM 
[2024-11-15 22:32:25]  INFO rpc: gRPC server listening on port address=0.0.0.0:4000
[2024-11-15 22:32:25]  WARN rpc: You are using an insecure gRPC server. If you are running your beacon node and validator on the same machines, you can ignore this message. If you want to know how to enable secure connections, see: https://docs.prylabs.network/docs/prysm-usage/secure-grpc
[2024-11-15 22:32:25]  INFO node: Starting beacon node version=Prysm/v5.1.2/944f94a9bf6cbd19699b319917499fd7262e2f73. Built at: 2024-10-16 19:18:56+00:00
[2024-11-15 22:32:25]  INFO backfill: Backfill service not enabled
[2024-11-15 22:32:25]  INFO initial-sync: Waiting for state to be initialized
[2024-11-15 22:32:25]  INFO blockchain: Blockchain data already exists in DB, initializing...
[2024-11-15 22:32:25]  INFO httprest: Starting HTTP server address=127.0.0.1:3500
[2024-11-15 22:32:25]  INFO initial-sync: Received state initialized event
[2024-11-15 22:32:25]  INFO initial-sync: Starting initial chain sync...
[2024-11-15 22:32:25]  INFO initial-sync: Waiting for enough suitable peers before syncing required=3 suitable=0
[2024-11-15 22:32:25]  INFO p2p: Started discovery v5 ENR=enr:-MK4QOeGqneVfB7aViPwgTQhVxFxNXFZJfQCTT0p_vaz1YuIfHvpO5s6y98xsQmMTbJ8XOAJN25mLAH4VMffEj6ev_GGAZMxhuo5h2F0dG5ldHOIAAAAAAAAAACEZXRoMpDTH2GRkAAAdP__________gmlkgnY0gmlwhMCoAQ-Jc2VjcDI1NmsxoQMs1ez7A75HyTyU6qfzrJYqfvXzaCMDBpLMm4GcmFfSoohzeW5jbmV0cwCDdGNwgjLIg3VkcIIu4A
[2024-11-15 22:32:25]  INFO p2p: Node started p2p server multiAddr=/ip4/192.168.1.15/tcp/13000/p2p/16Uiu2HAmFg1VAC7x7USE9aX2jymWUSp8F7vcUFaf19ZN6eSyMazM
[2024-11-15 22:32:30]  INFO initial-sync: Waiting for enough suitable peers before syncing required=3 suitable=1
[2024-11-15 22:32:35]  INFO initial-sync: Waiting for enough suitable peers before syncing required=3 suitable=1
[2024-11-15 22:32:40]  INFO execution: Connected to new endpoint endpoint=http://localhost:8551

Instead geth log periodically throwing that beacon not seen therefore it cant sync.

 INFO [11-15|22:32:02.256] HTTP server started                      endpoint=[::]:8545 auth=false prefix= cors=http://localhost,http://192.168.1.0/24 vhosts=localhost
INFO [11-15|22:32:02.257] WebSocket enabled                        url=ws://127.0.0.1:8551
INFO [11-15|22:32:02.257] HTTP server started                      endpoint=127.0.0.1:8551 auth=true  prefix= cors=localhost                              vhosts=localhost
INFO [11-15|22:32:02.264] NAT mapped port                          proto=TCP extport=30303 intport=30303 interface=NAT-PMP(192.168.1.1)
INFO [11-15|22:32:02.273] NAT mapped port                          proto=UDP extport=30303 intport=30303 interface=NAT-PMP(192.168.1.1)
INFO [11-15|22:32:18.076] Looking for peers                        peercount=0 tried=49 static=0
INFO [11-15|22:32:28.423] Looking for peers                        peercount=0 tried=58 static=0
WARN [11-15|22:32:37.235] Post-merge network, but no beacon client seen. Please launch one to follow the chain!
INFO [11-15|22:32:38.458] Looking for peers                        peercount=0 tried=45 static=0
INFO [11-15|22:32:49.215] Looking for peers                        peercount=0 tried=62 static=0
INFO [11-15|22:32:59.297] Looking for peers                        peercount=0 tried=34 static=0
INFO [11-15|22:33:09.329] Looking for peers                        peercount=0 tried=41 static=0
INFO [11-15|22:33:19.636] Looking for peers                        peercount=0 tried=79 static=0
INFO [11-15|22:33:29.672] Looking for peers                        peercount=0 tried=32 static=0
INFO [11-15|22:33:40.193] Looking for peers                        peercount=0 tried=41 static=0
INFO [11-15|22:33:50.205] Looking for peers                        peercount=0 tried=53 static=0
INFO [11-15|22:34:00.315] Looking for peers                        peercount=0 tried=42 static=0
INFO [11-15|22:34:10.371] Looking for peers                        peercount=0 tried=54 static=0
INFO [11-15|22:34:20.379] Looking for peers                        peercount=0 tried=70 static=0
INFO [11-15|22:34:30.520] Looking for peers                        peercount=0 tried=63 static=0
INFO [11-15|22:34:40.548] Looking for peers                        peercount=0 tried=27 static=0
INFO [11-15|22:34:51.146] Looking for peers                        peercount=0 tried=23 static=0
INFO [11-15|22:35:01.167] Looking for peers                        peercount=0 tried=72 static=0
INFO [11-15|22:35:11.190] Looking for peers                        peercount=0 tried=27 static=0
INFO [11-15|22:35:22.101] Looking for peers                        peercount=0 tried=58 static=0
INFO [11-15|22:35:32.121] Looking for peers                        peercount=1 tried=40 static=0
INFO [11-15|22:35:42.391] Looking for peers                        peercount=1 tried=57 static=0
INFO [11-15|22:35:52.441] Looking for peers                        peercount=1 tried=22 static=0
INFO [11-15|22:36:02.500] Looking for peers                        peercount=2 tried=44 static=0
INFO [11-15|22:36:12.755] Looking for peers                        peercount=2 tried=45 static=0
INFO [11-15|22:36:22.855] Looking for peers                        peercount=1 tried=42 static=0
INFO [11-15|22:36:32.873] Looking for peers                        peercount=1 tried=43 static=0
INFO [11-15|22:36:42.984] Looking for peers                        peercount=1 tried=45 static=0
INFO [11-15|22:36:53.032] Looking for peers                        peercount=1 tried=23 static=0
INFO [11-15|22:37:03.089] Looking for peers                        peercount=1 tried=34 static=0
INFO [11-15|22:37:13.530] Looking for peers                        peercount=1 tried=28 static=0
INFO [11-15|22:37:24.054] Looking for peers                        peercount=1 tried=48 static=0
INFO [11-15|22:37:34.525] Looking for peers                        peercount=1 tried=45 static=0
WARN [11-15|22:37:37.274] Post-merge network, but no beacon client seen. Please launch one to follow the chain!
INFO [11-15|22:37:44.599] Looking for peers                        peercount=1 tried=48 static=0

[thevops]

I had the same issue with (docker images):

• ethereum/client-go:v1.14.8
• gcr.io/prysmaticlabs/prysm/beacon-chain:v5.1.0

After X restart (I don't remember the number) and waiting ten minutes, it worked on the above logs.
Another time, I waited 30 minutes after it worked.

[thevops]

It looks that Prysm is doing something in the background. I have the following logs after it started to running and syncing:

time="2024-11-22 14:55:43" level=warning msg="Execution client is not syncing" prefix=execution
time="2024-11-22 14:55:29" level=warning msg="Execution client is not syncing" prefix=execution
time="2024-11-22 14:55:22" level=info msg="Processing blocks" batchSize=63 blocksPerSecond=4.7 estimatedTimeRemaining=2m25s latestProcessedSlot/currentSlot="10454592/10455274" peers=68 prefix=initial-sync startingFrom=0x692bdd09...
time="2024-11-22 14:55:16" level=warning msg="Skip processing batched blocks" error="beacon node doesn't have a parent in db with root: 0x9cea347c77add181ff408e96c98c024683bcd69e1a03de79c77964096bd49440 (in processBatchedBlocks, slot=10454720)" prefix=initial-sync
time="2024-11-22 14:55:15" level=warning msg="Skip processing batched blocks" error="beacon node doesn't have a parent in db with root: 0xefded58ab27039b1beed89311937186a4610ed8883b8535552c7aa044cfd3951 (in processBatchedBlocks, slot=10454656)" prefix=initial-sync
time="2024-11-22 14:55:15" level=warning msg="Execution client is not syncing" prefix=execution
time="2024-11-22 14:55:08" level=info msg="Processing blocks" batchSize=31 blocksPerSecond=1.6 estimatedTimeRemaining=7m39s latestProcessedSlot/currentSlot="10454561/10455273" peers=69 prefix=initial-sync startingFrom=0x93a4bb06...
time="2024-11-22 14:55:07" level=info msg="Blob filesystem cache warm-up complete." elapsed=1h4m35.139423451s prefix=filesystem
time="2024-11-22 14:55:06" level=info msg="Connected peers" inboundTCP=60 outboundTCP=8 prefix=p2p total=68
time="2024-11-22 14:55:01" level=warning msg="Execution client is not syncing" prefix=execution
time="2024-11-22 14:54:47" level=warning msg="Execution client is not syncing" prefix=execution
time="2024-11-22 14:54:33" level=warning msg="Execution client is not syncing" prefix=execution
time="2024-11-22 14:54:19" level=warning msg="Execution client is not syncing" prefix=execution