status only shows 100% as daemon is synchronizing

[Gingeropolous]

Height: 1837972/1837972 (100.0%) on mainnet, not mining, net hash 318.13 MH/s, v11, 12(out)+0(in) connections, uptime 1d 0h 19m 45s

and a minute later or so..

2023-05-26 10:55:09.943	I Monero 'Fluorine Fermi' (v0.18.2.2-release)
Height: 1838352/1838352 (100.0%) on mainnet, not mining, net hash 310.89 MH/s, v11, 12(out)+0(in) connections, uptime 1d 0h 21m 4s

this is the result of the "status" command. The daemon is daemonized and managed by systemd. im using RPC to send the status command.

v0.18.2.2 . release binaries.

[selsta]

Does sync_info work? Also do you always have this behaviour with status or just now suddenly?

[Gingeropolous]

honestly it's been a while since I've done a fresh sync, but it just seems "now suddenly".

sync_info shows the same

user@phantom:~$ monerod --rpc-bind-port 12345 sync_info
2023-05-26 13:08:30.270	I Monero 'Fluorine Fermi' (v0.18.2.2-release)
Height: 1892752, target: 1892752 (100%)
Downloading at 612 kB/s
Next needed pruning seed: 1
12 peers

[selsta]

Is this on the machine with sync troubles?

[Gingeropolous]

it is on both machines. the login node had sync troubles. phantom already syncd once with fast-sync=1, now its trudging along doing fast-sync=0.

[Gingeropolous]

more information. I'm running the daemon with

rpc-restricted-bind-ip=192.168.1.22
rpc-bind-ip=0.0.0.0
confirm-external-bind=1
rpc-restricted-bind-port=18089
rpc-bind-port=12345
public-node=1
log-level=2

and throwing the status command at it with:

monerod --rpc-bind-port 12345 status

[Gingeropolous]

now it seems to be showing realistic things

2023-05-28 18:06:20.938	I Monero 'Fluorine Fermi' (v0.18.2.2-release)
Height: 2566652/2895883 (88.6%) on mainnet, not mining, net hash 2.94 GH/s, v14, 12(out)+0(in) connections, uptime 0d 5h 28m 33s