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 12 Packages Projects Releases 10 Wiki Activity

Cannot update Hoarderr LXC from v0.20.0 to v0.21.0 #337

New Issue
Closed
opened 2026-02-04 18:03:26 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 18:03:26 +03:00
Owner
Copy Link

Originally created by @scetu on GitHub (Jan 15, 2025).

✅ Have you read and understood the above guidelines?

yes

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

hoarder

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

update

📝 Provide a clear and concise description of the issue.

While updating Hoarder LXC installation from v0.20.0 to v0.21.0 by executing update inside of LXC container, an error is thrown and requested file .env by systemd service is not present on filesystem thus hoarder cannot be started.

Only .env.sample is available in /opt/hoarder but not .env

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  • have Hoarder v0.20.0 installed
  • execute update command in LXC container

❌ Paste the full error output (if available).

    __  __                     __         
   / / / /___  ____ __________/ /__  _____
  / /_/ / __ \/ __ `/ ___/ __  / _ \/ ___/
 / __  / /_/ / /_/ / /  / /_/ /  __/ /    
/_/ /_/\____/\__,_/_/   \__,_/\___/_/     
                                          

  ✔️  Stopped Services
  ✔️  Updated Hoarder to v0.21.0
 ⠋Job for hoarder-workers.service failed because of unavailable resources or another system error.
See "systemctl status hoarder-workers.service" and "journalctl -xeu hoarder-workers.service" for details.
 ⠹Job for hoarder-web.service failed because of unavailable resources or another system error.
See "systemctl status hoarder-web.service" and "journalctl -xeu hoarder-web.service" for details.

[ERROR] in line 64: exit code 0: while executing command systemctl start hoarder-browser hoarder-workers hoarder-web

root@hoarder:~# journalctl -xeu hoarder-web.service
░░ The unit hoarder-web.service has entered the 'failed' state with result 'resources'.
Jan 15 11:09:01 hoarder systemd[1]: Failed to start hoarder-web.service - Hoarder Web.
░░ Subject: A start job for unit hoarder-web.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit hoarder-web.service has finished with a failure.
░░ 
░░ The job identifier is 6340 and the job result is failed.
Jan 15 11:09:01 hoarder systemd[1]: hoarder-web.service: Scheduled restart job, restart counter is at 4.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit hoarder-web.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jan 15 11:09:01 hoarder systemd[1]: Stopped hoarder-web.service - Hoarder Web.
░░ Subject: A stop job for unit hoarder-web.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit hoarder-web.service has finished.
░░ 
░░ The job identifier is 6401 and the job result is done.
**Jan 15 11:09:01 hoarder systemd[1]: hoarder-web.service: Failed to load environment files: No such file or directory
Jan 15 11:09:01 hoarder systemd[1]: hoarder-web.service: Failed to run 'start' task: No such file or directory
Jan 15 11:09:01 hoarder systemd[1]: hoarder-web.service: Failed with result 'resources'.**
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit hoarder-web.service has entered the 'failed' state with result 'resources'.
Jan 15 11:09:01 hoarder systemd[1]: Failed to start hoarder-web.service - Hoarder Web.
░░ Subject: A start job for unit hoarder-web.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
root@hoarder:~# systemctl status hoarder-
hoarder-browser.service  hoarder-web.service      hoarder-workers.service  
root@hoarder:~# systemctl status hoarder-web.service 
× hoarder-web.service - Hoarder Web
     Loaded: loaded (/etc/systemd/system/hoarder-web.service; enabled; preset: enabled)
     Active: failed (Result: resources) since Wed 2025-01-15 11:09:02 CET; 54s ago
   Duration: 1w 4d 21h 2min 11.222s
        CPU: 0

Jan 15 11:09:02 hoarder systemd[1]: hoarder-web.service: Scheduled restart job, restart counter is at 5.
Jan 15 11:09:02 hoarder systemd[1]: Stopped hoarder-web.service - Hoarder Web.
Jan 15 11:09:02 hoarder systemd[1]: hoarder-web.service: Start request repeated too quickly.
Jan 15 11:09:02 hoarder systemd[1]: hoarder-web.service: Failed with result 'resources'.
Jan 15 11:09:02 hoarder systemd[1]: Failed to start hoarder-web.service - Hoarder Web.
root@hoarder:/opt/hoarder# cat /etc/systemd/system/hoarder-web.service
[Unit]
Description=Hoarder Web
Wants=network.target hoarder-workers.service
After=network.target hoarder-workers.service

[Service]
ExecStart=pnpm start
WorkingDirectory=/opt/hoarder/apps/web
EnvironmentFile=/opt/hoarder/.env
Restart=always

[Install]
WantedBy=multi-user.target
root@hoarder:~# cd /opt/hoarder
root@hoarder:/opt/hoarder# ls -la
total 1264
drwxr-xr-x   14 root root    4096 Jan 15 11:08 .
drwxr-xr-x    4 root root    4096 Jan 15 11:06 ..
drwxr-xr-x    8 root root    4096 Jan  5 16:08 apps
drwxr-xr-x    3 root root    4096 Jan  5 16:08 docker
-rw-r--r--    1 root root     100 Jan  5 16:08 .dockerignore
drwxr-xr-x    7 root root    4096 Jan  5 16:08 docs
-rw-r--r--    1 root root     106 Jan  5 16:08 .env.sample
drwxr-xr-x    4 root root    4096 Jan  5 16:08 .github
-rw-r--r--    1 root root     643 Jan  5 16:08 .gitignore
-rw-r--r--    1 root root    8778 Jan  5 16:08 hoarder-linux.sh
drwxr-xr-x    2 root root    4096 Jan  5 16:08 .husky
drwxr-xr-x    2 root root    4096 Jan  5 16:08 kubernetes
-rw-r--r--    1 root root   34523 Jan  5 16:08 LICENSE
drwxr-xr-x 1673 root root   69632 Jan 15 11:08 node_modules
-rw-r--r--    1 root root      20 Jan  5 16:08 .npmrc
-rw-r--r--    1 root root    1695 Jan  5 16:08 package.json
drwxr-xr-x    9 root root    4096 Jan  5 16:08 packages
drwxr-xr-x    2 root root    4096 Jan  5 16:08 patches
-rw-r--r--    1 root root 1067266 Jan  5 16:08 pnpm-lock.yaml
-rw-r--r--    1 root root      67 Jan  5 16:08 pnpm-workspace.yaml
-rw-r--r--    1 root root     217 Jan  5 16:08 .prettierignore
-rw-r--r--    1 root root      49 Jan  5 16:08 .prettierrc
-rw-r--r--    1 root root    7640 Jan  5 16:08 README.md
drwxr-xr-x    2 root root    4096 Jan  5 16:08 screenshots
-rw-r--r--    1 root root     105 Jan  5 16:08 SECURITY.md
drwxr-xr-x    7 root root    4096 Jan  5 16:08 tooling
-rw-r--r--    1 root root     985 Jan  5 16:08 turbo.json
drwxr-xr-x    3 root root    4096 Jan 15 11:06 v8-compile-cache-0

🖼️ Additional context (optional).

No response

edit: Update formating for full log output

Originally created by @scetu on GitHub (Jan 15, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? hoarder ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. While updating Hoarder LXC installation from v0.20.0 to v0.21.0 by executing `update` inside of LXC container, an error is thrown and requested file `.env` by systemd service is not present on filesystem thus hoarder cannot be started. Only `.env.sample` is available in `/opt/hoarder` but not `.env` ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. - have Hoarder v0.20.0 installed - execute update command in LXC container ### ❌ Paste the full error output (if available). ``` __ __ __ / / / /___ ____ __________/ /__ _____ / /_/ / __ \/ __ `/ ___/ __ / _ \/ ___/ / __ / /_/ / /_/ / / / /_/ / __/ / /_/ /_/\____/\__,_/_/ \__,_/\___/_/ ✔️ Stopped Services ✔️ Updated Hoarder to v0.21.0 ⠋Job for hoarder-workers.service failed because of unavailable resources or another system error. See "systemctl status hoarder-workers.service" and "journalctl -xeu hoarder-workers.service" for details. ⠹Job for hoarder-web.service failed because of unavailable resources or another system error. See "systemctl status hoarder-web.service" and "journalctl -xeu hoarder-web.service" for details. [ERROR] in line 64: exit code 0: while executing command systemctl start hoarder-browser hoarder-workers hoarder-web root@hoarder:~# journalctl -xeu hoarder-web.service ░░ The unit hoarder-web.service has entered the 'failed' state with result 'resources'. Jan 15 11:09:01 hoarder systemd[1]: Failed to start hoarder-web.service - Hoarder Web. ░░ Subject: A start job for unit hoarder-web.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit hoarder-web.service has finished with a failure. ░░ ░░ The job identifier is 6340 and the job result is failed. Jan 15 11:09:01 hoarder systemd[1]: hoarder-web.service: Scheduled restart job, restart counter is at 4. ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ Automatic restarting of the unit hoarder-web.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. Jan 15 11:09:01 hoarder systemd[1]: Stopped hoarder-web.service - Hoarder Web. ░░ Subject: A stop job for unit hoarder-web.service has finished ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A stop job for unit hoarder-web.service has finished. ░░ ░░ The job identifier is 6401 and the job result is done. **Jan 15 11:09:01 hoarder systemd[1]: hoarder-web.service: Failed to load environment files: No such file or directory Jan 15 11:09:01 hoarder systemd[1]: hoarder-web.service: Failed to run 'start' task: No such file or directory Jan 15 11:09:01 hoarder systemd[1]: hoarder-web.service: Failed with result 'resources'.** ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit hoarder-web.service has entered the 'failed' state with result 'resources'. Jan 15 11:09:01 hoarder systemd[1]: Failed to start hoarder-web.service - Hoarder Web. ░░ Subject: A start job for unit hoarder-web.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ root@hoarder:~# systemctl status hoarder- hoarder-browser.service hoarder-web.service hoarder-workers.service root@hoarder:~# systemctl status hoarder-web.service × hoarder-web.service - Hoarder Web Loaded: loaded (/etc/systemd/system/hoarder-web.service; enabled; preset: enabled) Active: failed (Result: resources) since Wed 2025-01-15 11:09:02 CET; 54s ago Duration: 1w 4d 21h 2min 11.222s CPU: 0 Jan 15 11:09:02 hoarder systemd[1]: hoarder-web.service: Scheduled restart job, restart counter is at 5. Jan 15 11:09:02 hoarder systemd[1]: Stopped hoarder-web.service - Hoarder Web. Jan 15 11:09:02 hoarder systemd[1]: hoarder-web.service: Start request repeated too quickly. Jan 15 11:09:02 hoarder systemd[1]: hoarder-web.service: Failed with result 'resources'. Jan 15 11:09:02 hoarder systemd[1]: Failed to start hoarder-web.service - Hoarder Web. root@hoarder:/opt/hoarder# cat /etc/systemd/system/hoarder-web.service [Unit] Description=Hoarder Web Wants=network.target hoarder-workers.service After=network.target hoarder-workers.service [Service] ExecStart=pnpm start WorkingDirectory=/opt/hoarder/apps/web EnvironmentFile=/opt/hoarder/.env Restart=always [Install] WantedBy=multi-user.target root@hoarder:~# cd /opt/hoarder root@hoarder:/opt/hoarder# ls -la total 1264 drwxr-xr-x 14 root root 4096 Jan 15 11:08 . drwxr-xr-x 4 root root 4096 Jan 15 11:06 .. drwxr-xr-x 8 root root 4096 Jan 5 16:08 apps drwxr-xr-x 3 root root 4096 Jan 5 16:08 docker -rw-r--r-- 1 root root 100 Jan 5 16:08 .dockerignore drwxr-xr-x 7 root root 4096 Jan 5 16:08 docs -rw-r--r-- 1 root root 106 Jan 5 16:08 .env.sample drwxr-xr-x 4 root root 4096 Jan 5 16:08 .github -rw-r--r-- 1 root root 643 Jan 5 16:08 .gitignore -rw-r--r-- 1 root root 8778 Jan 5 16:08 hoarder-linux.sh drwxr-xr-x 2 root root 4096 Jan 5 16:08 .husky drwxr-xr-x 2 root root 4096 Jan 5 16:08 kubernetes -rw-r--r-- 1 root root 34523 Jan 5 16:08 LICENSE drwxr-xr-x 1673 root root 69632 Jan 15 11:08 node_modules -rw-r--r-- 1 root root 20 Jan 5 16:08 .npmrc -rw-r--r-- 1 root root 1695 Jan 5 16:08 package.json drwxr-xr-x 9 root root 4096 Jan 5 16:08 packages drwxr-xr-x 2 root root 4096 Jan 5 16:08 patches -rw-r--r-- 1 root root 1067266 Jan 5 16:08 pnpm-lock.yaml -rw-r--r-- 1 root root 67 Jan 5 16:08 pnpm-workspace.yaml -rw-r--r-- 1 root root 217 Jan 5 16:08 .prettierignore -rw-r--r-- 1 root root 49 Jan 5 16:08 .prettierrc -rw-r--r-- 1 root root 7640 Jan 5 16:08 README.md drwxr-xr-x 2 root root 4096 Jan 5 16:08 screenshots -rw-r--r-- 1 root root 105 Jan 5 16:08 SECURITY.md drwxr-xr-x 7 root root 4096 Jan 5 16:08 tooling -rw-r--r-- 1 root root 985 Jan 5 16:08 turbo.json drwxr-xr-x 3 root root 4096 Jan 15 11:06 v8-compile-cache-0 ``` ### 🖼️ Additional context (optional). _No response_ edit: Update formating for full log output
OVERLORD commented 2026-02-04 18:03:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 15, 2025):

Read Breaking Changes and done

@MickLesk commented on GitHub (Jan 15, 2025): Read Breaking Changes and done
OVERLORD commented 2026-02-04 18:03:47 +03:00
Author
Owner
Copy Link

@scetu commented on GitHub (Jan 15, 2025):

I am maybe totally dumb, but you mean which Breaking Changes? I do not see any at https://github.com/hoarder-app/hoarder/releases/tag/v0.21.0

Oh you mean this breaking change... Migration guide: https://github.com/community-scripts/ProxmoxVE/pull/1325#issuecomment-2587512616

Never thought that I have to look into script breaking changes itself.

Thanks

@scetu commented on GitHub (Jan 15, 2025): ~~I am maybe totally dumb, but you mean which Breaking Changes? I do not see any at https://github.com/hoarder-app/hoarder/releases/tag/v0.21.0~~ Oh you mean this breaking change... Migration guide: https://github.com/community-scripts/ProxmoxVE/pull/1325#issuecomment-2587512616 Never thought that I have to look into script breaking changes itself. Thanks
OVERLORD commented 2026-02-04 18:04:08 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 15, 2025):

Yes, we mark breaking changes in the changelog. These must be made manually, as we cannot catch every issue completely.

@MickLesk commented on GitHub (Jan 15, 2025): Yes, we mark breaking changes in the changelog. These must be made manually, as we cannot catch every issue completely.
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
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#337
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?