starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #6787] Update script - Palmr #1448

New issue

Closed

opened 2026-02-26 12:48:56 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 12:48:56 +03:00

Owner

Originally created by @MarkMSP on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6787

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). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6787 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_

kerem

2026-02-26 12:48:56 +03:00

closed this issue
added the
bug

bugfix

json
labels

kerem commented

2026-02-26 12:48:57 +03:00

Author

Owner

@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.

kerem commented

2026-02-26 12:48:57 +03:00

Author

Owner

@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.

kerem commented

2026-02-26 12:48:57 +03:00

Author

Owner

@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.

kerem commented

2026-02-26 12:48:57 +03:00

Author

Owner

@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.

kerem commented

2026-02-26 12:48:57 +03:00

Author

Owner

@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.

kerem commented

2026-02-26 12:48:57 +03:00

Author

Owner

@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:

You ran update and due to the RELEASE parsing error the script thought an update was available.
The script deleted the /opt/palmr folder.
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.
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").

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#1448

No description provided.

Rows
Columns