starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Update script - Palmr #1448

New Issue
Closed
opened 2026-02-05 00:52:09 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-05 00:52:09 +03:00
Owner
Copy Link

Originally created by @MarkMSP on GitHub (Aug 13, 2025).

Originally assigned to: @vhsdream on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

Palmr

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

Hi, could you please check why the Palmr update script is failing? The message says that the /opt/palmr/apps/server folder doesn't exist.

The folder isn't there even after installing the Palmr script. Thanks.

🔄 Steps to reproduce the issue.

Step 1: Install with the script in Proxmox shell

Step 2: Type update in the LXC console

❌ Paste the full error output (if available).

jq: error: Could not open file /opt/palmr/package.json: No such file or directory

[ERROR] in line 41: exit code 0: while executing command PNPM="$(jq -r '.packageManager' /opt/palmr/package.json)"

🖼️ Additional context (optional).

No response

Originally created by @MarkMSP on GitHub (Aug 13, 2025). Originally assigned to: @vhsdream on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Palmr ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/palmr.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. Hi, could you please check why the Palmr update script is failing? The message says that the /opt/palmr/apps/server folder doesn't exist. The folder isn't there even after installing the Palmr script. Thanks. ### 🔄 Steps to reproduce the issue. Step 1: Install with the script in Proxmox shell Step 2: Type update in the LXC console ### ❌ Paste the full error output (if available). jq: error: Could not open file /opt/palmr/package.json: No such file or directory [ERROR] in line 41: exit code 0: while executing command PNPM="$(jq -r '.packageManager' /opt/palmr/package.json)" ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bugbugfixjson labels 2026-02-05 00:52:09 +03:00
OVERLORD commented 2026-02-05 00:52:15 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Aug 13, 2025):

Hey @MarkMSP could you please run the install script again, this time with the verbose flag? It would help to have some more output.

@vhsdream commented on GitHub (Aug 13, 2025): Hey @MarkMSP could you please run the install script again, this time with the verbose flag? It would help to have some more output.
OVERLORD commented 2026-02-05 00:52:18 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Aug 13, 2025):

Update: good thing you for whatever reason decided to run the update script, even though Palmr hasn't had an update since this script was released. Found something wrong with the version parsing.

@vhsdream commented on GitHub (Aug 13, 2025): Update: good thing you for whatever reason decided to run the update script, even though Palmr hasn't had an update since this script was released. Found something wrong with the version parsing.
OVERLORD commented 2026-02-05 00:52:21 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Aug 13, 2025):

Another update: This thing is a real problem. I think it's going to need 6GB RAM to be able to update. Just tried with 4GB and it either maxed it out and froze the LXC or crashed.

@vhsdream commented on GitHub (Aug 13, 2025): Another update: This thing is a real problem. I think it's going to need 6GB RAM to be able to update. Just tried with 4GB and it either maxed it out and froze the LXC or crashed.
OVERLORD commented 2026-02-05 00:52:27 +03:00
Author
Owner
Copy Link

@MarkMSP commented on GitHub (Aug 13, 2025):

Sorry for the late reply. I tried increasing the RAM to 6GB and simply starting the process with "Update" in the LXC shell. Yes, there are currently no updates, but it destroys the LXC. I have to restore the lxc every time after the update command.

@MarkMSP commented on GitHub (Aug 13, 2025): Sorry for the late reply. I tried increasing the RAM to 6GB and simply starting the process with "Update" in the LXC shell. Yes, there are currently no updates, but it destroys the LXC. I have to restore the lxc every time after the update command.
OVERLORD commented 2026-02-05 00:52:30 +03:00
Author
Owner
Copy Link

@MarkMSP commented on GitHub (Aug 13, 2025):

I will install again with the verbos flag later and report back.

@MarkMSP commented on GitHub (Aug 13, 2025): I will install again with the verbos flag later and report back.
OVERLORD commented 2026-02-05 00:52:32 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Aug 13, 2025):

@MarkMSP no need to run it again - I've found the issue 😸

I think I know what you were trying to do; as the script currently stands, if you run 'update', even if the version is the same it will proceed, and one of the steps is to delete /opt/palmr although I've since learned that that step is already handled by a function. But the function will also simply not proceed with downloading and deploying if it detects there is no new version. So, what happened was:

  1. You ran update and due to the RELEASE parsing error the script thought an update was available.
  2. The script deleted the /opt/palmr folder.
  3. The script ran it's function to download and deploy the app, but I guess has it's own version check, determined that no new version was available, so didn't download/deploy the app.
  4. Script continued but failed because there was no /opt/palmr anymore.

As an aside though, if you're gonna run update make sure you edit the /root/.palmr file and change the version to something else, if you want to "force" an update (ie there is no update but you want to "reinstall").

@vhsdream commented on GitHub (Aug 13, 2025): @MarkMSP no need to run it again - I've found the issue 😸 I think I know what you were trying to do; as the script currently stands, if you run 'update', even if the version is the same it will proceed, and one of the steps is to delete `/opt/palmr` although I've since learned that that step is already handled by a function. But the function will also simply not proceed with downloading and deploying if it detects there is no new version. So, what happened was: 1. You ran `update` and due to the RELEASE parsing error the script thought an update was available. 2. The script deleted the `/opt/palmr` folder. 3. The script ran it's function to download and deploy the app, but I guess has it's own version check, determined that no new version was available, so didn't download/deploy the app. 4. Script continued but failed because there was no `/opt/palmr` anymore. As an aside though, if you're gonna run `update` make sure you edit the `/root/.palmr` file and change the version to something else, if you want to "force" an update (ie there is no update but you want to "reinstall").
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 bugfix json
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#1448
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?