-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from 22.1.0-apache to 22.1.1-apache - PostgreSQL issues #1579
Comments
Same here. Can't get it run with Postgres on a Pi4B. |
I have the same issue - after upgrading via |
Same here (with Postgresql 11.13). Tried to restore my backup of the database and the html folder, but same error when restarting the container. |
i am using docker-compose to create my containers. If i use for example "nextcloud:21.0.2-apache" image, I can access my fresh installation. So it's not a Postgres issue I think. I tested also a fresh install with SQLite which didn't work too. |
It seems to me, that the latest apache2 image is broken then... |
The fpm image is broken too. Seems to be related to the arm image because on my x64 Maschine everything works fine. |
just to be clear - you tested a brand new installation with 21.0.2 and not the "broken" updated one? @BorussiaPlayer17 |
Yes. Because you get an error if you want to downgrade to an older version. Didn’t wanted to figure out if you can manually downgrade the DB. It looks like every 22.1.0 version works on arm. |
Don‘t know what happened, but now a new fresh install works fine with the latest image. |
Now i updated my old production system and it's working too. Don't know what was updated, but it's working now on my Pi4. Latest image with apache and latest postgres. |
I tried to start a fresh instance, but without luck. I am not able to install a new instance, as I am getting a "time" - error, that seems to be related to #1589 . So I am not able to start a new instance and restore a backup. |
Ok, I got my instance working again. It seems like the timesync problem (#1589) (old version of
With the new version of I added the backports repo to my Buster installation and installed a newer version of
Also, I had to uninstall docker from the buster repository and reinstalled it with the official docker repostitory. So, unless the raspberry foundation does not update their repositories (or jumps to bullseye), this seems to be the workaround. Source of the solution: |
Duplicate of #1589 |
Hi everyone,
I recently upgraded my Nextcloud instance from 22.1.0-apache to 22.1.1-apache and now i'm getting errors related to PostgreSQL initialization. Even tried with a fresh install but same result :/
Steps to reproduce:
Server not started and this got this error on the logs :
Server configuration
Operating system (
lsb_release -a
):Web server: Handled in the docker image (Apache)
Database: PostgreSQL
Where did you install Nextcloud from: Docker with Docker-compose
Are you using external storage, if yes which one: Yes (ssd mounted to the RaspberryPi)
Are you using encryption: No
Are you using an external user-backend, if yes which one: No
Don't know if it helps, but here are the Docker Image IDs (in case new versions are pushed):
I checked the GitHub actions and there are some failing workflows even form version 22.1.1-apache. Don't know if that's related.
Thanks in advance for your help !
The text was updated successfully, but these errors were encountered: