having some weird daemon issues after a reboot. daemon was previously working fine. Monero GUI wouldn't connect to the daemon, first, then said it connected to the daemon but wouldn't finish syncing, so I closed that and opened the daemon in a console window. Daemon now says its synced, but the GUI says there's 1 daemon block remaining. opening a

different wallet in CLI gives an error, "no connection to daemon, please make sure daemon is running". This screen shot shows all three concurrently: the fully synced daemon, the CLI wallet error, and the state of the GUI wallet: i.imgur.com/dktkpnm.png

Now the GUI says "4 blocks remaining" while the GUI still says it's synced.It's like....some RPC calls are going through and some aren't? Idk, happy to provide logs and stuff though

I mean the daemon says it's synced

GUI is frozen after I clicked "Stop daemon"

also if this isn't the place to go for support / reporting issues I apologize and somebody please lmk where would be more appropriate

lyza: Can you try completely rebooting your PC?

@selsta I have already tried rebooting but I can try again?

windows does this half reboot crap, might need a full shutdown I suppose

half reboot?

well fuck me. after closing everything (including force closing the frozen GUI) and restarting the GUI, everything connects and is synced.....

but yeah, a standard reboot on Windows 10 doesn't actually fully shut everything down, is my understanding

ok, not sure why the daemon got confused

but good that it’s working again

yeah it's been weird for me after reboots sometimes since the last update. I can usually get it working eventually but I haven't found like, any particular one thing that fixes it....

anyway, would logs be helpful / desired or nah?

hi it's me again. I still can't get the daemon to work with the GUI reliably. and this seems.... very wrong. i.imgur.com/Axn24dD.png

Started the GUI. GUI says it's starting the daemon. GUI says daemon can't start. Task manager says, actually, the daemon IS running. However, the Node ta udner settings still has the option for "start daemon". so I click it. GUI says it's starting the daemon. Spawns ANOTHER instance of monerod in the task manager. Tells me again the GUI can't

start. Now there are 2 instances of monerod in task manager

so the daemon is running but the GUI for some reason thinks it isn't and keeps trying to start it? idk -- I've been having lots of weird issues with the daemon + GUI since the last update, it seems to me

lyza: can you try closing everything, then start the daemon manually and make sure it's fully-synced before starting the gui?

@sgp_ I am trying that now, but earlier today I was running the daemon in a console window, it was reporting fully synced, and the GUI was still having issues connecting. Sometimes would say disconnected, sometimes would say the daemon was behind, again while the daemon reported fully synced

it's been an intermittent thing, but usually the problem happens after a reboot. so far I've always been able to get it working by just like, restarting stuff a lot. but yeah.

@sgp_ like this. just took this screenshot. daemon says synced, GUI says daemon is 4 blocks behind. i.imgur.com/1rwIlEr.png

looks from my ignorant perspective like RPC calls are only being answered sometimes

at the moment it looks ok, no?

no

the daemon says sync'd but the GUI says 4 blocks behind

restarted the GUI now it just says 'disconnected'. the daemon seems really unresponsive. I typed 'status' into it like a couple minutes ago and it still hasn't shown me the status. this is a beefy desktop though.

that makes me think the daemon isn't synced

yeah I'm restarting it again

got it running with log level one so I'm getting pretty constant output and it reports synced (2018491)

seems like the daemon locks up again when I try to open the GUI

any logs you can provide that show the issue would be useful

binmonero.log: pastebin.com/FLRUMsR7

doesn't seem like much,but just in case, here us monero-wallet-gui.log: pastebin.com/8xWn3KiR

lyza: can you post the monerod log in #monero ? maybe moneromooo can help you

absolutely