search

pixelfed / support

Issue tracker for installations of Pixelfed, before a bug is identified.
https://docs.pixelfed.org/running-pixelfed/troubleshooting.html
8 stars 3 forks source link

Unsuccessful update broke the instance #87

Open Victor-Morel opened 4 years ago

Victor-Morel commented 4 years ago

Hello, I wanted to apply some changes in the user quota of my pixelfed instance, but decided to run an update of my pixelfed instance beforehand. I consciously made a snapshot of the VM running pixelfed, but the update (following the recommendations) couldn't be brought to a satisfying end: composer install warns me with

Installing dependencies (including require-dev) from lock file Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.

[ErrorException]
"continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"?

But the most inconvenient part is that when I rollback to before the update, my pixelfed instance cannot be accessed! It's quite surprising because I was able to access to the web interface before the update... This is the error message when rollbacking:

ErrorException thrown with message "syntax error, unexpected ''pixelfed.v' (T_ENCAPSED_AND_WHITESPACE) (View: /home/pixelfed/resources/views/layouts/partial/footer.blade.php) (View: /home/pixelfed/resources/views/layouts/partial/footer.blade.php)"

Stacktrace:

0 Symfony\Component\Debug\Exception\FatalThrowableError in /home/pixelfed/storage/framework/views/21ca9e8b2ef6e9423dc092dbea398ef0e4811614.php:15

Note that the previously-uploaded pictures are still available (their URL is not broken).

Victor-Morel commented 4 years ago

Hello, is there a technique to export the database (and the stored pictures) to a new instance? I'm considering installing a new one, but I wouldn't want to lose all the previous images.

Victor-Morel commented 4 years ago

Hello, any idea to help me?

dansup commented 4 years ago

Run composer update, delete composer.lock if you have issues.

You can backup your instance by running php artisan backup:run, or just the database with php artisan backup:run --only-database

Victor-Morel commented 4 years ago

Ok thanks for the answer.
However, I tried to update again (deleting composer.lock), and it doesn't change anything :/
I will try to investigate, and/or backup the instance using artisan.
Note that the broken instance is in debug mode regardless of what the .env states.