SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-31 09:48:43 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

TriliumNext update fails when moving dump-db #868

New Issue
Closed
opened 2025-11-20 04:55:27 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 04:55:27 -05:00
Owner
Copy Link

Originally created by @jshprentz on GitHub (Apr 6, 2025).

✅ Have you read and understood the above guidelines?

Yes

📜 What is the name of the script you are using?

TriliumNext

📂 What was the exact command used to execute the script?

update

📝 Provide a clear and concise description of the issue.

The update fails while executing command mv /opt/trilium/{db,dump-db} /opt/trilium_backup/ because /opt/trilium/dump-db does not exist.

After the update failure, TriliumNext will not restart, even after rebooting the LXC. Additional Context below shows the commands needed to recover from the update failure.

The likely cause of the failure is the removal of /opt/trilium/dump-db from the TriliumNext distribution in version 0.92.4 as described in Additional Context below.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Step 1: Between March 16 and April 5, 2025, run this command in a Proxmox node console to create an LXC running TriliumNext 0.92.4:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/trilium.sh)"

The command is shown at https://community-scripts.github.io/ProxmoxVE/scripts?id=trilium.

Step 2: Await the next release of TriliumNext. Version 0.92.6 was released on April 6, 2025.

Step 3: Run this command in the LXC console to update TriliumNext:

update

Step 4: Choose 2 YES (Verbose Mode) from the update menu.

❌ Paste the full error output (if available).

Console output:

  ______     _ ___               
 /_  __/____(_) (_)_  ______ ___ 
  / / / ___/ / / / / / / __ `__ \
 / / / /  / / / / /_/ / / / / / /
/_/ /_/  /_/_/_/\__,_/_/ /_/ /_/ 
                                 

  ✔️   Stopped Trilium
⠋ Updating to 0.92.6mv: cannot stat '/opt/trilium/dump-db': No such file or directory
⠙ Updating to 0.92.6
[ERROR] in line 40: exit code 0: while executing command mv /opt/trilium/{db,dump-db} /opt/trilium_backup/

🖼️ Additional context (optional).

Recovering from the failed update

Execute these commands in the LXC console to

  • restore the TriliumNext database to its pre-update configuration,
  • remove the backup directory, and
  • restart TriliumNext.
mv /opt/trilium_backup/db /opt/trilium/
rmdir /opt/trilium_backup
systemctl start trilium

Likely cause

TriliumNext issue 1115 noted problems with the dump-db tool. As part of the mitigation, TriliumNext PR 1388 removed directory dump-db/ from the distribution. The PR was part of TriliumNext release 0.92.4.

The update from TriliumNext 0.92.4 to TriliumNext 0.92.6 "broke" the TriliumNext community script because it was the first update from a release that omitted /opt/trilium/dump-db, which the community script attempted to move.

Originally created by @jshprentz on GitHub (Apr 6, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? TriliumNext ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. The update fails while executing command ```mv /opt/trilium/{db,dump-db} /opt/trilium_backup/``` because ```/opt/trilium/dump-db``` does not exist. After the update failure, TriliumNext will not restart, even after rebooting the LXC. *Additional Context* below shows the commands needed to recover from the update failure. The likely cause of the failure is the removal of ```/opt/trilium/dump-db``` from the TriliumNext distribution in version 0.92.4 as described in *Additional Context* below. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Step 1: Between March 16 and April 5, 2025, run this command in a Proxmox node console to create an LXC running TriliumNext 0.92.4: ``` bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/trilium.sh)" ``` The command is shown at https://community-scripts.github.io/ProxmoxVE/scripts?id=trilium. Step 2: Await the next release of TriliumNext. Version 0.92.6 was released on April 6, 2025. Step 3: Run this command in the LXC console to update TriliumNext: ``` update ``` Step 4: Choose ```2 YES (Verbose Mode)``` from the update menu. ### ❌ Paste the full error output (if available). Console output: ``` ______ _ ___ /_ __/____(_) (_)_ ______ ___ / / / ___/ / / / / / / __ `__ \ / / / / / / / / /_/ / / / / / / /_/ /_/ /_/_/_/\__,_/_/ /_/ /_/ ✔️ Stopped Trilium ⠋ Updating to 0.92.6mv: cannot stat '/opt/trilium/dump-db': No such file or directory ⠙ Updating to 0.92.6 [ERROR] in line 40: exit code 0: while executing command mv /opt/trilium/{db,dump-db} /opt/trilium_backup/ ``` ### 🖼️ Additional context (optional). ## Recovering from the failed update Execute these commands in the LXC console to - restore the TriliumNext database to its pre-update configuration, - remove the backup directory, and - restart TriliumNext. ``` mv /opt/trilium_backup/db /opt/trilium/ rmdir /opt/trilium_backup systemctl start trilium ``` ## Likely cause [TriliumNext issue 1115](https://github.com/TriliumNext/trilium/issues/5459) noted problems with the ```dump-db``` tool. As part of the mitigation, [TriliumNext PR 1388](https://github.com/TriliumNext/Notes/pull/1388) removed directory ```dump-db/``` from the distribution. The PR was part of TriliumNext release 0.92.4. The update from TriliumNext 0.92.4 to TriliumNext 0.92.6 "broke" the TriliumNext community script because it was the first update from a release that omitted ```/opt/trilium/dump-db```, which the community script attempted to move.
saavagebueno added the bug label 2025-11-20 04:55:27 -05:00
saavagebueno commented 2025-11-20 04:55:28 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 8, 2025):

Done, thx for information

@MickLesk commented on GitHub (Apr 8, 2025): Done, thx for information
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#868
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?