monerod just quits at start #9255
Comments
|
Can you share the full logs of starting with log level 2? What you shared seems incomplete. Please also try to start without any config or startup options. |
The output with only the following config contents: |
|
Can you start it from command line like this to see if it segfaults? Please share the logs from the command line output and not the log file.
|
It says |
|
I would guess it's a corrupt database. Do you remember what happened the last time it worked? Did you have a power outage? Did you force shutdown monerod during sync? |
|
I had a couple of power outages, yes. Not sure if monerod stopped working after one of these, since i don't monitor it. |
|
If you have regular power outages I would recommend to keep a backup of the blockchain. |
|
I am having segmentation faults with the application, I've tried resyncing the database three times now but I'm still having this issue, it might be related. Using Arch Linux on Kernel 6.8.4-zen1-1-zen It's never gotten to the point of being online and the system should absolutely have enough RAM. Log: If I'm missing anything I can provide it ^^ |
|
@ChecksumDev what kind of hardware do you have? |
I'm running: |
|
@ChecksumDev can you also your config file? also how did you install monero? from package manager or getmonero website? |
|
I assume you mean this file: I installed monerod from the pacman extra repository. |
|
Can you try the monerod binary from https://www.getmonero.org/downloads/ to rule out it's related to how the package manager built monerod? Also can you rule out unstable hardware, e.g. overclocking? |
|
No unstable hardware, relatively new. I don't think any components in the system are more than three years old, not overclocking. I honestly expected the binary to work so now I'm a little more puzzled. |
|
|
|
dmesg output in case that's helpful: |
I don't know how they are compiling monero, that's why it would be good to try the getmonero.org binary in an attempt to isolate the issue. Also where is your blockchain stored? Local ssd? Local hdd? Network drive? |
|
Local NVME, I did try it from getmonero too. see IMG. |
Does it always happen around the same block height when you delete the blockchain and resync? If yes, which block? |
|
It seems like the same block every time if I estimated the time it took to crash, though I couldn't find logs going back that to the previous sync, another resync would take a while. |
|
Had the same issue after power outage. Unfortunately, daemon started working only after removing of data.lmdb database. Synchronization started from the beginning (sadly). Seems LMDB is not protected from power outage. But even so, monerod doesn't properly handle corrupted database data and that's bad. Maybe it could try to reverse or just remove some last entries. Below is a OpenLDAP discussion about LMDB behavior during power outage. But at the same time I saw plenty of sources that claim LMDB engine is protected from this. Important information: I observed this on the computer with HDD, not SSD. UPDATE
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The log output doesn't look interesting, nothing in dmesg too:
Tried
log-level=3, the tail of the log looks like this:I have no idea what's going on. Used to work fine.
The text was updated successfully, but these errors were encountered: