starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Docmost update fails with error in line 961 #791

New Issue
Closed
opened 2026-02-04 21:34:53 +03:00 by OVERLORD · 9 comments
OVERLORD commented 2026-02-04 21:34:53 +03:00
Owner
Copy Link

Originally created by @Zixim on GitHub (Apr 10, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Docmost

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

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

📝 Provide a clear and concise description of the issue.

Updating Docmost results in an error.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

In the lxc execute script as per command above (or run update),
Select either option 1 (silent) or option 2 (verbose).

❌ Paste the full error output (if available).

Output:

    ____                                  __ 
   / __ \____  _________ ___  ____  _____/ /_
  / / / / __ \/ ___/ __ `__ \/ __ \/ ___/ __/
 / /_/ / /_/ / /__/ / / / / / /_/ (__  ) /_  
/_____/\____/\___/_/ /_/ /_/\____/____/\__/  
                                             


[ERROR] in line 961: exit code 0: while executing command return

root@docmost:~#

🖼️ Additional context (optional).

No response

Originally created by @Zixim on GitHub (Apr 10, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Docmost ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/docmost.sh)" ### 📝 Provide a clear and concise description of the issue. Updating Docmost results in an error. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. In the lxc execute script as per command above (or run `update`), Select either option 1 (silent) or option 2 (verbose). ### ❌ Paste the full error output (if available). Output: ``` ____ __ / __ \____ _________ ___ ____ _____/ /_ / / / / __ \/ ___/ __ `__ \/ __ \/ ___/ __/ / /_/ / /_/ / /__/ / / / / / /_/ (__ ) /_ /_____/\____/\___/_/ /_/ /_/\____/____/\__/ [ERROR] in line 961: exit code 0: while executing command return root@docmost:~# ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 21:34:53 +03:00
OVERLORD commented 2026-02-04 21:34:59 +03:00
Author
Owner
Copy Link

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

only in this, or other too?

@MickLesk commented on GitHub (Apr 10, 2025): only in this, or other too?
OVERLORD commented 2026-02-04 21:35:02 +03:00
Author
Owner
Copy Link

@Zixim commented on GitHub (Apr 10, 2025):

I've got another lxc (wikijs), here the update runs fine (but no update available) :

  ✔️   No update required. Wikijs is already at v2.5.307
@Zixim commented on GitHub (Apr 10, 2025): I've got another lxc (wikijs), here the update runs fine (but no update available) : ``` ✔️ No update required. Wikijs is already at v2.5.307 ```
OVERLORD commented 2026-02-04 21:35:06 +03:00
Author
Owner
Copy Link

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

can you try following:

      apt-get purge -y nodejs
      rm -f /etc/apt/sources.list.d/nodesource.list
      rm -f /etc/apt/keyrings/nodesource.gpg

  mkdir -p /etc/apt/keyrings
  curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
  echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main" >/etc/apt/sources.list.d/nodesource.list
  apt-get update
  apt-get install -y nodejs
  npm install -g pnpm@10.4.0
  export NODE_OPTIONS="--max_old_space_size=4096"

after this, hit "update" again?

@MickLesk commented on GitHub (Apr 10, 2025): can you try following: ```bash apt-get purge -y nodejs rm -f /etc/apt/sources.list.d/nodesource.list rm -f /etc/apt/keyrings/nodesource.gpg mkdir -p /etc/apt/keyrings curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main" >/etc/apt/sources.list.d/nodesource.list apt-get update apt-get install -y nodejs npm install -g pnpm@10.4.0 export NODE_OPTIONS="--max_old_space_size=4096" ``` after this, hit "update" again?
OVERLORD commented 2026-02-04 21:35:10 +03:00
Author
Owner
Copy Link

@Zixim commented on GitHub (Apr 10, 2025):

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  nodejs*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 223 MB disk space will be freed.
(Reading database ... 28664 files and directories currently installed.)
Removing nodejs (22.14.0-1nodesource1) ...
dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules' not empty so not removed
Processing triggers for man-db (2.11.2-2) ...
root@docmost:~# rm -f /etc/apt/sources.list.d/nodesource.list
root@docmost:~# rm -f /etc/apt/keyrings/nodesource.gpg
root@docmost:~# mkdir -p /etc/apt/keyrings
root@docmost:~# curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
root@docmost:~# echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main" >/etc/apt/sources.list.d/nodesource.list
root@docmost:~# apt-get update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]                       
Get:3 http://security.debian.org bookworm-security InRelease [48.0 kB]                        
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease                                 
Get:5 http://security.debian.org bookworm-security/main amd64 Packages [252 kB]
Get:6 http://security.debian.org bookworm-security/main Translation-en [152 kB]
Fetched 508 kB in 3s (191 kB/s)                                
Reading package lists... Done
root@docmost:~# apt-get install -y nodejs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  nodejs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/36.4 MB of archives.
After this operation, 223 MB of additional disk space will be used.
Selecting previously unselected package nodejs.
(Reading database ... 22765 files and directories currently installed.)
Preparing to unpack .../nodejs_22.14.0-1nodesource1_amd64.deb ...
Unpacking nodejs (22.14.0-1nodesource1) ...
Setting up nodejs (22.14.0-1nodesource1) ...
Processing triggers for man-db (2.11.2-2) ...
root@docmost:~# npm install -g pnpm@10.4.0

changed 1 package in 3s

1 package is looking for funding
  run `npm fund` for details
root@docmost:~# export NODE_OPTIONS="--max_old_space_size=4096"

update results in the exact same error :/

@Zixim commented on GitHub (Apr 10, 2025): ```root@docmost:~# apt-get purge -y nodejs Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: nodejs* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 223 MB disk space will be freed. (Reading database ... 28664 files and directories currently installed.) Removing nodejs (22.14.0-1nodesource1) ... dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules' not empty so not removed Processing triggers for man-db (2.11.2-2) ... root@docmost:~# rm -f /etc/apt/sources.list.d/nodesource.list root@docmost:~# rm -f /etc/apt/keyrings/nodesource.gpg root@docmost:~# mkdir -p /etc/apt/keyrings root@docmost:~# curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg root@docmost:~# echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main" >/etc/apt/sources.list.d/nodesource.list root@docmost:~# apt-get update Hit:1 http://deb.debian.org/debian bookworm InRelease Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:3 http://security.debian.org bookworm-security InRelease [48.0 kB] Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Get:5 http://security.debian.org bookworm-security/main amd64 Packages [252 kB] Get:6 http://security.debian.org bookworm-security/main Translation-en [152 kB] Fetched 508 kB in 3s (191 kB/s) Reading package lists... Done root@docmost:~# apt-get install -y nodejs Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: nodejs 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/36.4 MB of archives. After this operation, 223 MB of additional disk space will be used. Selecting previously unselected package nodejs. (Reading database ... 22765 files and directories currently installed.) Preparing to unpack .../nodejs_22.14.0-1nodesource1_amd64.deb ... Unpacking nodejs (22.14.0-1nodesource1) ... Setting up nodejs (22.14.0-1nodesource1) ... Processing triggers for man-db (2.11.2-2) ... root@docmost:~# npm install -g pnpm@10.4.0 changed 1 package in 3s 1 package is looking for funding run `npm fund` for details root@docmost:~# export NODE_OPTIONS="--max_old_space_size=4096" ``` `update` results in the exact same error :/
OVERLORD commented 2026-02-04 21:35:13 +03:00
Author
Owner
Copy Link

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

Okay, i have an idea, but you need to test it after merge ^^ (maybe 1-2h)

@MickLesk commented on GitHub (Apr 10, 2025): Okay, i have an idea, but you need to test it after merge ^^ (maybe 1-2h)
OVERLORD commented 2026-02-04 21:35:17 +03:00
Author
Owner
Copy Link

@Zixim commented on GitHub (Apr 10, 2025):

fwiw, creating a fresh Docmost instance from scratch works just fine, but that was to be expected i guess...
A fresh install still has the same update issue though :/

@Zixim commented on GitHub (Apr 10, 2025): fwiw, creating a fresh Docmost instance from scratch works just fine, but that was to be expected i guess... A fresh install still has the same update issue though :/
OVERLORD commented 2026-02-04 21:35:24 +03:00
Author
Owner
Copy Link

@Zixim commented on GitHub (Apr 10, 2025):

e7529a9c25

The logic in lines 29-38 needs reworking? It would cause the app update to never happen and always return 0.

@Zixim commented on GitHub (Apr 10, 2025): https://github.com/community-scripts/ProxmoxVE/commit/e7529a9c2511e5734c8e8efcd6c6531f70ae89a3 The logic in lines 29-38 needs reworking? It would cause the app update to never happen and always return 0.
OVERLORD commented 2026-02-04 21:35:27 +03:00
Author
Owner
Copy Link

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

work?

@MickLesk commented on GitHub (Apr 10, 2025): work?
OVERLORD commented 2026-02-04 21:35:35 +03:00
Author
Owner
Copy Link

@Zixim commented on GitHub (Apr 10, 2025):

tried & tested !
@MickLesk thx & have a great end-of-week !

@Zixim commented on GitHub (Apr 10, 2025): tried & tested ! @MickLesk thx & have a great end-of-week !
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#791
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?