on an aws machine, lighthouse say it is synced. but Geth is not, for a few days now its syncing but keep the same distance between current and highest block(from eth_syncing response):
Geth recent print is that:
Jan 04 12:50:35 ip-172-31-23-187 geth: INFO [01-04|12:50:35.949] Forkchoice requested sync to new head number=16,333,536 hash=b5851f..98ff42 Jan 04 12:50:36 ip-172-31-23-187 geth: INFO [01-04|12:50:36.599] Imported new block headers count=1 elapsed="338.72µs" number=16,333,536 hash=b5851f..98ff42 Jan 04 12:50:39 ip-172-31-23-187 geth: INFO [01-04|12:50:39.690] State heal in progress accounts=2,445,firstname.lastname@example.orgMiB slots=5,617,email@example.comMiB firstname.lastname@example.orgMiB nodes=56,687,email@example.comGiB pending=23018
--cacheflag when you did run Geth? if yes, what number did you write after that? You should use
--cache <a number in MB>to determine how much of memory should be assigned to Geth when it is running. If you didn't use this flag it sets the default value, that is 1024 MB. Try Geth by this flag instead unlimited and let I know the result.