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

FireFly-iii update issue - nesting storage direcrories after multiple fails #694

New Issue
Closed
opened 2026-02-04 20:54:49 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 20:54:49 +03:00
Owner
Copy Link

Originally created by @LapplandsCohan on GitHub (Mar 24, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Firefly III LXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/firefly.sh)"

📝 Provide a clear and concise description of the issue.

Not sure if this is a script issue or a Firefly issue.

I found a number of closed issues with the Firefly update script, but I couldn't find any regarding this nesting directory problem.

I ran the upgrade script, which after several minuted ended with a out of disc space error message. Increased storage size from default 2 GiB to 3 GiB and reran, but got the same error message. Increased storage space to 3, 4, 5, 6, and finally 8 GiB retrying the upgrade until I finally got another error message:

                                       
  Target class [hash] does not exist.  
                                       

In Container.php line 959:
                               
  Class "hash" does not exist  
                               

⠦ Updating Firefly to v6.2.10
[ERROR] in line 48: exit code 0: while executing command $STD php artisan migrate --seed --force

I googled, and this error seems to not be specific to Firefly, but can happen when any php artisan application is rebuilt if there is a problem with the cache, and the first recommendation is to delete the cache and try again.

Searching for cache gave me the following hits:

/opt/storage/storage/storage/storage/storage/framework/cache
/opt/storage/storage/storage/storage/framework/cache
/opt/storage/storage/storage/framework/cache
/opt/storage/storage/framework/cache
/opt/storage/framework/cache
/opt/firefly/storage/storage/storage/storage/storage/storage/framework/cache
/opt/firefly/storage/storage/storage/storage/storage/framework/cache
/opt/firefly/storage/storage/storage/storage/framework/cache
/opt/firefly/storage/storage/storage/framework/cache
/opt/firefly/storage/storage/framework/cache
/opt/firefly/storage/framework/cache
/opt/firefly/bootstrap/cache
/opt/firefly/vendor/psr/cache
/opt/firefly/vendor/symfony/cache

It seems like every failed upgrade attempt created a nested storage level under /opt/storage/ and /opt/firefly/storage/

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. Run the upgrade script with not enough disk space
  2. Run the upgrade script again

❌ Paste the full error output (if available).

⠇ Updating Firefly to v6.2.10In Container.php line 961:
                                       
  Target class [hash] does not exist.  
                                       

In Container.php line 959:
                               
  Class "hash" does not exist  
                               

⠦ Updating Firefly to v6.2.10
[ERROR] in line 48: exit code 0: while executing command $STD php artisan migrate --seed --force

🖼️ Additional context (optional).

No response

Originally created by @LapplandsCohan on GitHub (Mar 24, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Firefly III LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/firefly.sh)" ### 📝 Provide a clear and concise description of the issue. Not sure if this is a script issue or a Firefly issue. I found a number of closed issues with the Firefly update script, but I couldn't find any regarding this nesting directory problem. I ran the `upgrade` script, which after several minuted ended with a out of disc space error message. Increased storage size from default 2 GiB to 3 GiB and reran, but got the same error message. Increased storage space to 3, 4, 5, 6, and finally 8 GiB retrying the upgrade until I finally got another error message: ``` Target class [hash] does not exist. In Container.php line 959: Class "hash" does not exist ⠦ Updating Firefly to v6.2.10 [ERROR] in line 48: exit code 0: while executing command $STD php artisan migrate --seed --force ``` I googled, and this error seems to not be specific to Firefly, but can happen when any php artisan application is rebuilt if there is a problem with the cache, and the first recommendation is to delete the cache and try again. Searching for cache gave me the following hits: ``` /opt/storage/storage/storage/storage/storage/framework/cache /opt/storage/storage/storage/storage/framework/cache /opt/storage/storage/storage/framework/cache /opt/storage/storage/framework/cache /opt/storage/framework/cache /opt/firefly/storage/storage/storage/storage/storage/storage/framework/cache /opt/firefly/storage/storage/storage/storage/storage/framework/cache /opt/firefly/storage/storage/storage/storage/framework/cache /opt/firefly/storage/storage/storage/framework/cache /opt/firefly/storage/storage/framework/cache /opt/firefly/storage/framework/cache /opt/firefly/bootstrap/cache /opt/firefly/vendor/psr/cache /opt/firefly/vendor/symfony/cache ``` It seems like every failed upgrade attempt created a nested storage level under `/opt/storage/` and `/opt/firefly/storage/` ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. Run the upgrade script with not enough disk space 2. Run the upgrade script again ### ❌ Paste the full error output (if available). ``` ⠇ Updating Firefly to v6.2.10In Container.php line 961: Target class [hash] does not exist. In Container.php line 959: Class "hash" does not exist ⠦ Updating Firefly to v6.2.10 [ERROR] in line 48: exit code 0: while executing command $STD php artisan migrate --seed --force ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:54:49 +03:00
OVERLORD commented 2026-02-04 20:54:56 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 25, 2025):

@quantumryuu

@MickLesk commented on GitHub (Mar 25, 2025): @quantumryuu
OVERLORD commented 2026-02-04 20:55:12 +03:00
Author
Owner
Copy Link

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

i cant reproduce this. I wait for an newer release, but for me it still works.

@MickLesk commented on GitHub (Apr 14, 2025): i cant reproduce this. I wait for an newer release, but for me it still works.
OVERLORD commented 2026-02-04 20:55:15 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Apr 23, 2025):

I also can not reproduce this.
Also this would be a Laravell/Firefly bug and not a script issue.

@michelroegl-brunner commented on GitHub (Apr 23, 2025): I also can not reproduce this. Also this would be a Laravell/Firefly bug and not a script issue.
OVERLORD commented 2026-02-04 20:55:18 +03:00
Author
Owner
Copy Link

@ilfuriano commented on GitHub (Sep 8, 2025):

I have the same issue

@ilfuriano commented on GitHub (Sep 8, 2025): I have the same issue
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#694
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?