Closed rkunschke closed 3 weeks ago
@rkunschke Could you try removing /var/lib/firefly-iii/cache/config.php
and retrying?
Also, could you paste the contents of rld865prwn8v8r1yiz7xpkvgz5d70sgl-firefly-iii-maintenance.sh
here?
@savyajha Oh that was a quick answer, thank you :) removing the config.php in the cache directory fixed my issue. Firefly is running again :) the file is gone now (rld865prwn8v8r1yiz7xpkvgz5d70sgl-firefly-iii-maintenance.sh) but I looked it up at it's new directory (/nix/store/bmp10c984wa3d9bnayiz6hfj9266p9xy-firefly-iii-maintenance.sh):
#!/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash
set -a
APP_ENV=local
APP_URL=...
DB_CONNECTION=sqlite
DB_HOST=localhost
.... private mail config ....
APP_KEY="$(< /nix/store/x1x61bfvsjg9lzbclzid9fhybw5gybqx-keyfile)"
set +a
touch /var/lib/firefly-iii/storage/database/database.sqlite
/nix/store/86r39ckr1y52v7zs2ikcf6l2knr7xasy-firefly-iii-6.1.19/artisan cache:clear
/nix/store/86r39ckr1y52v7zs2ikcf6l2knr7xasy-firefly-iii-6.1.19/artisan package:discover
/nix/store/86r39ckr1y52v7zs2ikcf6l2knr7xasy-firefly-iii-6.1.19/artisan firefly-iii:upgrade-database
/nix/store/86r39ckr1y52v7zs2ikcf6l2knr7xasy-firefly-iii-6.1.19/artisan firefly-iii:laravel-passport-keys
/nix/store/86r39ckr1y52v7zs2ikcf6l2knr7xasy-firefly-iii-6.1.19/artisan view:cache
/nix/store/86r39ckr1y52v7zs2ikcf6l2knr7xasy-firefly-iii-6.1.19/artisan route:cache
/nix/store/86r39ckr1y52v7zs2ikcf6l2knr7xasy-firefly-iii-6.1.19/artisan config:cache
seems like the path of the maintainance.sh differs to the nix store paths in the bash-script as well. But I didn't fully understood that nix store-path things ever. Looks good for me now. Should we close the issue or try to find out why that happened?
Maybe it would be useful to make that cache-file automatically removed while upgrading firefly?
So /nix/store/86r39ckr1y52v7zs2ikcf6l2knr7xasy-firefly-iii-6.1.19/artisan cache:clear
is supposed to do that. In fact, if you run the command, config.php
should disappear. I do not know why it sometimes fails. If we get another bug report on this same issue sometime again, I'll make the change.
Also, were you upgrading to 6.1.19 from something like 6.1.15? I remember I moved the cache clear command to the very top around that time.
Ah okay. It's possible I missed that update since then. I think my auto-upgrade service failed for some time. I don't check my server that often. I should enable a mail notification for failing services because that seems to be kind of dangerous 😆
Hey :wave:
I had the same issue.
Could you try removing /var/lib/firefly-iii/cache/config.php and retrying?
Fixed it for me as well.
I've updated from:
[U.] #015 firefly-iii 6.1.19, 6.1.19-composer-repository -> 6.1.21, 6.1.21-composer-repository
Cool. For the next upgrade I'll just add this to the maintainer script.
Describe the bug
I've notices the update on my server failing and firefly III seems to be the reason.. I've looked up the problem with journalctl and got that log:
I opended up the firefly-iii-maintenance.sh and noticed the paths used in that sh-file seem to refer to an older nix store path of firefly which is not present.
I am unable to rebuild my system and found no way too work around that issue.
Notify maintainers
@savyajha @PatrickDaG
Metadata