Go-ethereum: Light mode (not looking for peers ?)

[picatextra]

Geth VERSION: 1.9.24-stable-cc05b050

I've been using Geth with Light mode for 1 year, after a server reboot, it always take a few hours to find a peer.
But this time things looks different , the Looking for peers appears to have bigger intervals.
Also many tried=0 ... never saw that behavior before.

Nov 20 01:23:30 vultr.guest geth[2987]: INFO [11-20|01:23:30.799] Looking for peers peercount=0 tried=0 static=0
Nov 20 01:08:14 vultr.guest geth[2987]: INFO [11-20|01:08:14.799] Looking for peers peercount=0 tried=0 static=0
Nov 20 00:51:13 vultr.guest geth[2987]: INFO [11-20|00:51:13.799] Looking for peers peercount=0 tried=1 static=0
Nov 20 00:50:38 vultr.guest geth[2987]: INFO [11-20|00:50:38.799] Looking for peers peercount=0 tried=0 static=0

[picatextra]

Downloaded geth-linux-amd64-1.9.23-8c2f2715 , now it looks better

INFO [11-20|16:10:03.070] Looking for peers peercount=0 tried=11 static=0
INFO [11-20|16:10:13.142] Looking for peers peercount=1 tried=15 static=0

[turboboost55]

Just to chime in here ... I'm seeing pretty much the same thing with v1.9.24. It will not find any peers. For me it prints out the usual first 15 lines or so, ending with

...
...
INFO [11-24|21:08:34.524] HTTP server started                      endpoint=127.0.0.1:8545 cors= vhosts=localhost
WARN [11-24|21:08:34.524] Light client mode is an experimental feature 
INFO [11-24|21:08:34.524] New local node record                    seq=1 id=dadfd2474c4096bc ip=127.0.0.1 udp=30303 tcp=30303
INFO [11-24|21:08:34.525] Started P2P networking                   self=enode://[email protected]:30303

and then it just sits there and does nothing ... for hours. I downgraded to v1.9.23 and everything is back to normal.

[zsfelfoldi]

Sorry, my mistake, I accidentally disabled DNS discovery (regardless of the --nodiscover flag) and did not notice because my client already had known peers in the server pool. Fixed by https://github.com/ethereum/go-ethereum/pull/21906