Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Bug report) Trilium fails to start after hard stop, hangs with full CPU utilization #3501

Open
johndoe0815 opened this issue Jan 8, 2023 · 3 comments

Comments

@johndoe0815
Copy link

Trilium Version

0.57.4

What operating system are you using?

Other Linux

What is your setup?

Server access only

Operating System Version

Linux trilium 5.15.83-1-pve #1 SMP PVE 5.15.83-1 (2022-12-15T00:00Z) x86_64 GNU/Linux

Description

I have trilium running in a proxmox container. Everything was working well, until the host had a power failure. After restart, all my containers started up again properly, except trilium.
The node process is continuously utilizing the CPU and trilium is not accessible anymore. Is there any way to fix my installation or do I need to recover the last backup (with which I would lose a few late changes)?

Error logs

No response

@sigaloid
Copy link
Contributor

sigaloid commented Jan 8, 2023

SQLite is supposed to be resistant to power failure, any ongoing transactions will be rolled back upon opening it the next time. Is there any log messages? Anything about performing a recovery especially with the -wal files? (These are crucial to recovery in the case of a power outage)

@johndoe0815
Copy link
Author

No, trilium was just not reachable over its web interface by IP:8080 and CPU remained fully utilized.
But as I needed my notes, I managed to download the last automatic weekly database backup and rolled back a previous complete backup with that. However with that experience I will now create even more frequent backups.

@zadam
Copy link
Owner

zadam commented Jan 8, 2023

Hi, it would help if you could provide log files from the container when you were experiencing the problem.s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants