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

OpenArchiver - Update fails #2213

New Issue
Closed
opened 2025-11-20 05:25:18 -05:00 by saavagebueno · 9 comments
saavagebueno commented 2025-11-20 05:25:18 -05:00
Owner
Copy Link

Originally created by @tomfrenzel on GitHub (Oct 30, 2025).

✅ Have you read and understood the above guidelines?

yes

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

OpenArchiver

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.0.11

📝 Provide a clear and concise description of the issue.

The update command fails when not running from /opt/openarchiver directory. Also, when running from /opt/openarchiver, the update goes trough without any errors but the service crashes directly after starting it.

🔄 Steps to reproduce the issue.

  1. Enter LXC console (/root directory)
  2. run update command

❌ Paste the full error output (if available).

Update errors:

✔️ Update available: openarchiver 0.3.4 → 0.4.0
✔️ Stopped Services
✔️ Deployed: openarchiver (0.4.0)
⏳ Updating Open Archiver ERR_PNPM_NO_PKG_MANIFEST  No package.json found in /root

[ERROR] in line 41: exit code 0: while executing command $STD pnpm install --shamefully-hoist --frozen-lockfile --prod=false

Service errors:
Oct 30 17:58:46 open-archiver pnpm[1322]:  ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "docker-start" not found
Oct 30 17:58:46 open-archiver pnpm[1322]: Did you mean "pnpm docker-start:oss"?
Oct 30 17:58:46 open-archiver systemd[1]: openarchiver.service: Main process exited, code=exited, status=254/n/a

🖼️ Additional context (optional).

Originally created by @tomfrenzel on GitHub (Oct 30, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? OpenArchiver ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.0.11 ### 📝 Provide a clear and concise description of the issue. The `update` command fails when not running from `/opt/openarchiver` directory. Also, when running from `/opt/openarchiver`, the update goes trough without any errors but the service crashes directly after starting it. ### 🔄 Steps to reproduce the issue. 1. Enter LXC console (`/root` directory) 2. run `update` command ### ❌ Paste the full error output (if available). Update errors: ✔️ Update available: openarchiver 0.3.4 → 0.4.0 ✔️ Stopped Services ✔️ Deployed: openarchiver (0.4.0) ⏳ Updating Open Archiver ERR_PNPM_NO_PKG_MANIFEST  No package.json found in /root [ERROR] in line 41: exit code 0: while executing command $STD pnpm install --shamefully-hoist --frozen-lockfile --prod=false Service errors: Oct 30 17:58:46 open-archiver pnpm[1322]:  ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "docker-start" not found Oct 30 17:58:46 open-archiver pnpm[1322]: Did you mean "pnpm docker-start:oss"? Oct 30 17:58:46 open-archiver systemd[1]: openarchiver.service: Main process exited, code=exited, status=254/n/a ### 🖼️ Additional context (optional).
saavagebueno added the bugexternal labels 2025-11-20 05:25:18 -05:00
saavagebueno commented 2025-11-20 05:25:19 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 30, 2025):

Report this to openarchiver Repo please

@MickLesk commented on GitHub (Oct 30, 2025): Report this to openarchiver Repo please
saavagebueno commented 2025-11-20 05:25:19 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 30, 2025):

Wait, its missing one command in CT script...

@tremor021 commented on GitHub (Oct 30, 2025): Wait, its missing one command in CT script...
saavagebueno commented 2025-11-20 05:25:19 -05:00
Author
Owner
Copy Link

@tomfrenzel commented on GitHub (Oct 30, 2025):

@tremor021 @MickLesk

I just tried creating a new OpenArchiver LXC and that does not work either. The installation does not report any errors but the openarchiver service fails to start with the ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "docker-start" not found error.

OpenArchiver itself is only supporting docker as installation method. I suppose the person who developed this LXC script did some workaround to get it working without docker. It seems like the workaround broke with the new update

@tomfrenzel commented on GitHub (Oct 30, 2025): @tremor021 @MickLesk I just tried creating a new OpenArchiver LXC and that does not work either. The installation does not report any errors but the openarchiver service fails to start with the `ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "docker-start" not found` error. OpenArchiver itself is only supporting docker as installation method. I suppose the person who developed this LXC script did some workaround to get it working without docker. It seems like the workaround broke with the new update
saavagebueno commented 2025-11-20 05:25:19 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 30, 2025):

Yeah they Changes the pnpm Files... (Im currently only on mobile)

@MickLesk commented on GitHub (Oct 30, 2025): Yeah they Changes the pnpm Files... (Im currently only on mobile)
saavagebueno commented 2025-11-20 05:25:20 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 30, 2025):

I'm looking at it... Hold up

@tremor021 commented on GitHub (Oct 30, 2025): I'm looking at it... Hold up
saavagebueno commented 2025-11-20 05:25:20 -05:00
Author
Owner
Copy Link

@tomfrenzel commented on GitHub (Oct 30, 2025):

Changing pnpm build to pnpm build:oss (in the install and update script) and ExecStart=/usr/bin/pnpm docker-start to ExecStart=/usr/bin/pnpm docker-start:oss in the service seems to have fixed the issue

@tomfrenzel commented on GitHub (Oct 30, 2025): Changing `pnpm build` to `pnpm build:oss` (in the install and update script) and `ExecStart=/usr/bin/pnpm docker-start` to `ExecStart=/usr/bin/pnpm docker-start:oss` in the service seems to have fixed the issue
saavagebueno commented 2025-11-20 05:25:20 -05:00
Author
Owner
Copy Link

@tomfrenzel commented on GitHub (Oct 30, 2025):

Never mind, i see you already added that to you PR 😄

@tomfrenzel commented on GitHub (Oct 30, 2025): Never mind, i see you already added that to you PR 😄
saavagebueno commented 2025-11-20 05:25:20 -05:00
Author
Owner
Copy Link

@tomfrenzel commented on GitHub (Oct 30, 2025):

@tremor021 The Update script misses the systemctl daemon-reload command. Without it, the service won't start after the update:

  ✔️   Update available: openarchiver 0.3.4 → 0.4.0
  ✔️   Stopped Services
  ✔️   Deployed: openarchiver (0.4.0)
  ✔️   Updated Open Archiver
⠋ Starting ServicesWarning: The unit file, source configuration file or drop-ins of openarchiver.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  ✔️   Started Services
  ✔️   Updated successfully!
root@open-archiver:~# service openarchiver status
Warning: The unit file, source configuration file or drop-ins of openarchiver.service changed on disk. Run 'systemctl daemon-reload' to reload units.
× openarchiver.service - Open Archiver Service
     Loaded: loaded (/etc/systemd/system/openarchiver.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2025-10-30 19:14:01 CET; 23s ago
   Duration: 617ms
 Invocation: 36373c5e71bb40bcaeaa86fbf50d4d9c
    Process: 3238 ExecStart=/usr/bin/pnpm docker-start (code=exited, status=254)
   Main PID: 3238 (code=exited, status=254)

Oct 30 19:14:01 open-archiver systemd[1]: openarchiver.service: Scheduled restart job, restart counter is at 5.
Oct 30 19:14:01 open-archiver systemd[1]: openarchiver.service: Start request repeated too quickly.
Oct 30 19:14:01 open-archiver systemd[1]: openarchiver.service: Failed with result 'exit-code'.
Oct 30 19:14:01 open-archiver systemd[1]: Failed to start openarchiver.service - Open Archiver Service.
@tomfrenzel commented on GitHub (Oct 30, 2025): @tremor021 The Update script misses the `systemctl daemon-reload` command. Without it, the service won't start after the update: ``` ✔️ Update available: openarchiver 0.3.4 → 0.4.0 ✔️ Stopped Services ✔️ Deployed: openarchiver (0.4.0) ✔️ Updated Open Archiver ⠋ Starting ServicesWarning: The unit file, source configuration file or drop-ins of openarchiver.service changed on disk. Run 'systemctl daemon-reload' to reload units. ✔️ Started Services ✔️ Updated successfully! root@open-archiver:~# service openarchiver status Warning: The unit file, source configuration file or drop-ins of openarchiver.service changed on disk. Run 'systemctl daemon-reload' to reload units. × openarchiver.service - Open Archiver Service Loaded: loaded (/etc/systemd/system/openarchiver.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2025-10-30 19:14:01 CET; 23s ago Duration: 617ms Invocation: 36373c5e71bb40bcaeaa86fbf50d4d9c Process: 3238 ExecStart=/usr/bin/pnpm docker-start (code=exited, status=254) Main PID: 3238 (code=exited, status=254) Oct 30 19:14:01 open-archiver systemd[1]: openarchiver.service: Scheduled restart job, restart counter is at 5. Oct 30 19:14:01 open-archiver systemd[1]: openarchiver.service: Start request repeated too quickly. Oct 30 19:14:01 open-archiver systemd[1]: openarchiver.service: Failed with result 'exit-code'. Oct 30 19:14:01 open-archiver systemd[1]: Failed to start openarchiver.service - Open Archiver Service. ```
saavagebueno commented 2025-11-20 05:25:20 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 30, 2025):

Correct, its fixed now

@tremor021 commented on GitHub (Oct 30, 2025): Correct, its fixed now
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 external
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#2213
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?