3 ms·
>> just killing the process will never corrupt the blockchain DB > I would love to show you how easy this is to reproduce, even on fresh installs of Ubuntu and
by hyc_symas 5mo ago
>> just killing the process will never corrupt the blockchain DB
> I would love to show you how easy this is to reproduce, even on fresh installs of Ubuntu and/or MacOS on otherwise-stable hardware (never tried Windows... easier?).
If it's so easy to reproduce, you should be able to screen record a session with two terminal windows:
1 with monerod running and syncing the blockchain
2 send a `kill -9` to the monerod
1b restart monerod
And then we should see the error message you're referring to.
- ProllyInfamous 5mo agoAwesome; let me rsyncd this bitch and then I'll try to help out. I'll do another with a brand new fresh install (do you have a Linux varient, otherwise it'll be Ubuntu v24). Will also provide the perplexity.ai chatlogs that I used to both find other similar crashouts and resolve my issues. Again, I am not a programmer but have been accepting crypto (with client discount) since 2012. Thanks again for your contributions to this community. ---- As you're capable, do you happen to know why the default configuration doesn't sync in background – this is just wild... anybody installing XMR-adjacent software isn't going to expect this behavior. ...the re-sync (after stopping due to timeout) is always where my issue appears. The LMDB backend (I know it's you're baby) could possibly be having a freakout when Linux comes back online?! (from e.g. sleep) – I genuinely don't know – but am happy do demonstrate my frustrations (that I've had literally & reproducably on both Linus and MacOS distros (across YEARS). Thanks for the approachability.