<b​chainplayer:matrix.org> currently, my solution is to remove the ~/.bitmonero/* to back to square one.

<b​chainplayer:matrix.org> but I know, there should be easier solution for this.

<b​chainplayer:matrix.org> anyone can help. thx

<t​bcode:matrix.org> Perhaps what error did ur pc get?

<t​bcode:matrix.org> > <@bchainplayer:matrix.org> Hi guys, my pc reboot with some error, and after reboot finish, the GUI wallet cannot start connect to dameo processes...

<t​bcode:matrix.org> > currently, my solution is to remove the ~/.bitmonero/* to back to square one.

<t​bcode:matrix.org> > but I know, there should be easier solution for this.

<t​bcode:matrix.org> > anyone can help. thx

<t​bcode:matrix.org> What error did ur pc get? Did it reset as ur wallet syncing?

<b​chainplayer:matrix.org> thx, for the reply. yes. it rebooted during the syncing.

<b​chainplayer:matrix.org> I guess there should be some consistency between the sync meta data and block data. I tried to set the blk to an earlier one, but no help

<t​bcode:matrix.org> I wud stop syncing if ur pc is still running & reboot again. If the problem persists clear the block data and reboot then resync

<t​bcode:matrix.org> Did u back up ur keys?

<b​chainplayer:matrix.org> yes, keys backed up.

<b​chainplayer:matrix.org> actually, wallet and nodes are 2 separated things, right?

<b​chainplayer:matrix.org> so, there should be NO big business with the keys.

<b​chainplayer:matrix.org> for now, my solution is just clear all the data and sync from the beginning...

<t​bcode:matrix.org> Ok worst case scenario u just import keys to another wallet software or do a clean install on the current and re sync

<b​chainplayer:matrix.org> but, this solution obviously not the right one.

<b​chainplayer:matrix.org> hh, no need re-install. just remove the synced data. and then start from the beginning.

<t​bcode:matrix.org> Yea that shud work. Rebooting while syncing mustve corrupted something

<t​bcode:matrix.org> Yea that shud work. Rebooting while syncing mustve corrupted the data

<b​chainplayer:matrix.org> hmm, actually, there is syncing work process during the minting, right?

<b​chainplayer:matrix.org> what I am worrying is that, during the daily minting,,, the pc crash,,, then, another cycle of syncing...

<b​chainplayer:matrix.org> that's bad. I think

<t​bcode:matrix.org> I'm not sure I'm still new at this 😅

<b​chainplayer:matrix.org> That's why I am trying to find some RIGHT solution to this situation.

<b​chainplayer:matrix.org> anyone old birds can help this?

<t​bcode:matrix.org> Hopefully l8r in the day, try the solutions we thought of in the meantime.

<r​4v3r23:monero.social> scheduled reminder to get 8619 background-sync PR merged

<r​4v3r23:monero.social> jeffro256 & rbrunner both signed off on it, and ive been using it daily for nearly 6 months

.merges

does anyone have an idea why running a node with a lower `--max-txpool-weight` causes monerod to have difficulty keeping connections? are other nodes requesting something and since it can't reply it due to incomplete txpool they disconnect?

.merge+ 9282 9259 9260 9257 9252 9232 9211 9205 9204 9202 9200 9199 9194

r​4v3r23: i would prefer to merge it to master branch first, it's too large of a change to include in a small release

<b​oog900:monero.social> selsta it might be because when monerod receives a tx it queues it for broadcasting, if that tx is then removed from the txpool and monerod receives the tx again it is queued for broadcasting again. If this was to happen in a short space of time (between diffusion flushes) monerod would broadcast both txs in the same message causing the peers it sends this message to to disconnect.

<r​ucknium:monero.social> There's no log setting or anything in `monerod` that could get you the ping network latency between your node and its peers, right?

.merge+ 9064 9291 9254 9149 9267 9268

Added

<s​yntheticbird:monero.social> can we merge 9211 before I commit murder ?

<s​yntheticbird:monero.social> (i'm just waiting for it to be merged so I can go edit the openrpc doc)