SOLVED Help! Nextcloud wont start after upgrade

[KristofferLindberg]

Hello all. After upgrading Nextcloud to latest release 27.1.0_1.6.48 from 46 it just wont start. I have no idea why. Anyone that have any idea based on the logs?
As far as I can see it has something to do with postgres not starting but no idea why

 

[Patrick M. Hausen]

If you post text via copy&paste instead of screenshots I am willing to take a look at your logs ...

 

[KristofferLindberg]

Thanks, have pasted in the logs as far as I know

Application Name:nextcloudPod Name:nextcloud-77f48f565-47p72Container Name:nextcloud

Error​

Received 400 response code from '/api/v1/namespaces/ix-nextcloud/pods/nextcloud-77f48f565-47p72/log?follow=true×tamps=true&timeoutSeconds=1800&container=nextcloud&tailLines=500'


Application Name:nextcloudPod Name:nextcloud-77f48f565-47p72Container Name:init-postgresdb
2023-09-20 21:20:15.225713+00:00waiting for postgres
2023-09-20 21:20:17.253331+00:00nextcloud-postgres:5432 - no response
2023-09-20 21:20:17.255390+00:00waiting for postgres
2023-09-20 21:20:19.287965+00:00nextcloud-postgres:5432 - no response
2023-09-20 21:20:19.287999+00:00waiting for postgres



Application Name:nextcloudPod Name:nextcloud-postgres-84b9f864ff-vlzt9Container Name:nextcloud-postgres
2023-09-20 21:21:12.359022+00:002023-09-20T21:21:12.359022151Z
2023-09-20 21:21:12.359051+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-09-20 21:21:12.359060+00:002023-09-20T21:21:12.359060142Z
2023-09-20 21:21:12.399196+00:002023-09-20 21:21:12.399 UTC [1] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2023-09-20 21:21:12.399321+00:002023-09-20 21:21:12.399 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-09-20 21:21:12.399342+00:002023-09-20 21:21:12.399 UTC [1] LOG: listening on IPv6 address "::", port 5432
2023-09-20 21:21:12.424633+00:002023-09-20 21:21:12.424 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-09-20 21:21:12.466140+00:002023-09-20 21:21:12.451 UTC [26] LOG: database system was interrupted; last known up at 2023-09-16 06:49:50 UTC
2023-09-20 21:21:12.513699+00:002023-09-20 21:21:12.513 UTC [26] LOG: invalid resource manager ID in primary checkpoint record
2023-09-20 21:21:12.513727+00:002023-09-20 21:21:12.513 UTC [26] PANIC: could not locate a valid checkpoint record
2023-09-20 21:21:12.515155+00:002023-09-20 21:21:12.514 UTC [1] LOG: startup process (PID 26) was terminated by signal 6: Aborted
2023-09-20 21:21:12.515214+00:002023-09-20 21:21:12.514 UTC [1] LOG: aborting startup due to startup process failure
2023-09-20 21:21:12.516751+00:002023-09-20 21:21:12.516 UTC [1] LOG: database system is shut down

Application Name:nextcloudPod Name:pre-upgrade-hook2-dnd9cContainer Name:nextcloud-postgres-backup
2023-09-20 20:34:21.028750+00:00/bin/backup_entrypoint.sh: 3: /bin/backup_entrypoint.sh: disown: not found
2023-09-20 20:34:21.245404+00:002023-09-20T20:34:21.245404042Z
2023-09-20 20:34:21.245432+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-09-20 20:34:21.245443+00:002023-09-20T20:34:21.245443706Z
2023-09-20 20:34:21.412599+00:002023-09-20 20:34:21.412 UTC [8] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2023-09-20 20:34:21.413047+00:002023-09-20 20:34:21.412 UTC [8] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-09-20 20:34:21.413073+00:002023-09-20 20:34:21.412 UTC [8] LOG: listening on IPv6 address "::", port 5432
2023-09-20 20:34:21.487273+00:002023-09-20 20:34:21.487 UTC [8] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-09-20 20:34:21.659710+00:002023-09-20 20:34:21.659 UTC [30] LOG: database system was interrupted; last known up at 2023-09-16 06:49:50 UTC
2023-09-20 20:34:21.812195+00:002023-09-20 20:34:21.811 UTC [31] FATAL: the database system is starting up
2023-09-20 20:34:21.833640+00:002023-09-20 20:34:21.833 UTC [30] LOG: invalid resource manager ID in primary checkpoint record
2023-09-20 20:34:21.833761+00:002023-09-20 20:34:21.833 UTC [30] PANIC: could not locate a valid checkpoint record
2023-09-20 20:34:21.836305+00:002023-09-20 20:34:21.836 UTC [8] LOG: startup process (PID 30) was terminated by signal 6: Aborted
2023-09-20 20:34:21.836347+00:002023-09-20 20:34:21.836 UTC [8] LOG: aborting startup due to startup process failure
2023-09-20 20:34:21.837540+00:002023-09-20 20:34:21.837 UTC [8] LOG: database system is shut down
2023-09-20 20:34:21.842069+00:00/var/run/postgresql:5432 - rejecting connections
2023-09-20 20:34:26.872614+00:00/var/run/postgresql:5432 - no response

 

[Patrick M. Hausen]

Sorry, SCALE, apps ... I'm out. No idea. Still please don't post images instead of text. I hope someone knowledgable will step in.
I'm working my way through the forums by the "whats new" page - so I missed that your post was about SCALE.

 

[KristofferLindberg]

Ok thanks anyway

 

[KristofferLindberg]

Solved it. Found another problem with the same solution. Check out https://medium.com/@rich_liberty_el...istant-database-on-truenas-scale-b37fd0ef0008 and switch to nextcloud instead. Problem happens because corrupted postrgresql db due to incorrect shutdown when doing the upgrade