db-worker-node failed to start: graph already locked
@RCmerci is already working on this.
Since Jul 7, 2026.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
### Search first
- [x] I searched and no similar issues were found
### What Happened?
I reloaded the application with CTRL + R.
Mabye that hard kills the app without closing the database gracefully and removing the lock.
In that case, i might not be supposed to do that.
I see the error message in terminal, but the issue i see as a user is that the validation message comes twice.
Demo: https://www.youtube.com/watch?v=xyVGurlRzf4
### Reproduce the Bug
0. Have Logseq open
1. Press CTRL + R to reload the app
### Expected Behavior
I can't remember where i picked up that you can do this. If it was official documentation or developer communication, it should not be recommended if it leads to issues.
No duplicate messages in any state.
### Screenshots
_No response_
### Files
_No response_
### Browser, Desktop or Mobile Platform Information
NixOS 25.11.10684.8fd9daa3db09
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260623
### Additional Context
To devs: Do you use this keyboard shortcut when testing?
### Are you willing to submit a PR? If you know how to fix the bug.
- [ ] I'm willing to submit a PR (Thank you!)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.