Nextcloud web not working after last update

[raud3rs]

Splendid tidings: the ‘Greät’ team is flourishing, and the administrator has resumed their duties. Regarding my device:

May 02 17:45:40 syncloud platform.backend[432]: info cli/executor.go:23 execute {“cmd”: “/usr/bin/journalctl -n 1000 --no-pager”}

May 02 17:45:40 syncloud platform.backend[432]: info rest/middleware.go:102 GET: /rest/logs

May 02 17:45:26 syncloud dhclient[983]: XMT: Solicit on eth0, interval 116160ms.

May 02 17:45:26 syncloud sh[289]: XMT: Solicit on eth0, interval 116160ms.

May 02 17:45:26 syncloud sh[289]: XMT: | X-- Request rebind in +5400

May 02 17:45:26 syncloud sh[289]: XMT: | X-- Request renew in +3600

May 02 17:45:26 syncloud sh[289]: XMT: X-- IA_PD 32:22:9f:c2

May 02 17:45:26 syncloud sh[289]: XMT: Forming Solicit, 655350 ms elapsed.

May 02 17:45:24 syncloud ld-2.31.so[1404]: syncloud nginx: my ip - - [02/May/2026:17:45:24 +0000] “GET /rest/app?app_id=nextcloud HTTP/2.0” 200 306 “https://raud3rs.syncloud.it:10443/app?id=nextcloud” “Mozilla/5.0 (X11; Linux x86_64; rv:150.0) Gecko/20100101 Firefox/150.0”

May 02 17:45:24 syncloud platform.backend[432]: info snap/server.go:228 find {“query”: “nextcloud”}

May 02 17:45:24 syncloud platform.backend[432]: info snap/server.go:257 find in store

May 02 17:45:23 syncloud platform.backend[432]: info rest/middleware.go:102 GET: /rest/app?app_id=nextcloud

May 02 17:45:23 syncloud ld-2.31.so[1404]: syncloud nginx: my ip- - [02/May/2026:17:45:23 +0000] “GET /rest/installer/status HTTP/2.0” 200 58 “https://raud3rs.syncloud.it:10443/app?id=nextcloud” “Mozilla/5.0 (X11; Linux x86_64; rv:150.0) Gecko/20100101 Firefox/150.0”

May 02 17:45:23 syncloud slapd[1449]: conn=1045 fd=13 closed (connection lost)

May 02 17:45:23 syncloud slapd[1449]: conn=1045 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text=

May 02 17:45:23 syncloud slapd[1449]: <= mdb_equality_candidates: (memberUid) not indexed

May 02 17:45:23 syncloud slapd[1449]: conn=1045 op=1 SRCH attr=memberUid

May 02 17:45:23 syncloud platform.backend[432]: info snap/changes_client.go:27 snap changes

May 02 17:45:23 syncloud slapd[1449]: conn=1045 op=1 SRCH base=“cn=syncloud,ou=groups,dc=syncloud,dc=org” scope=2 deref=3 filter=“(memberUid=raud3rs)”

May 02 17:45:23 syncloud slapd[1449]: conn=1045 op=0 RESULT tag=97 err=0 text=

May 02 17:45:23 syncloud slapd[1449]: conn=1045 op=0 BIND dn=“cn=admin,dc=syncloud,dc=org” mech=SIMPLE ssf=0

May 02 17:45:23 syncloud slapd[1449]: conn=1045 op=0 BIND dn=“cn=admin,dc=syncloud,dc=org” method=128

May 02 17:45:23 syncloud slapd[1449]: conn=1045 fd=13 ACCEPT from IP=127.0.0.1:54646 (IP=127.0.0.1:389)

May 02 17:45:23 syncloud platform.backend[432]: info rest/middleware.go:102 GET: /rest/installer/status

May 02 17:45:21 syncloud ld-2.31.so[1404]: syncloud nginx: my ip - - [02/May/2026:17:45:21 +0000] “GET /rest/installer/status HTTP/2.0” 200 146 “https://raud3rs.syncloud.it:10443/app?id=nextcloud” “Mozilla/5.0 (X11; Linux x86_64; rv:150.0) Gecko/20100101 Firefox/150.0”

May 02 17:45:21 syncloud platform.backend[432]: info snap/changes_client.go:64 in-progress change {“id”: “5457”, “summary”: “Refresh \“nextcloud\” snap”, “parsed_app”: “nextcloud”}

May 02 17:45:21 syncloud slapd[1449]: conn=1044 fd=13 closed (connection lost)

May 02 17:45:21 syncloud platform.backend[432]: info snap/changes_client.go:27 snap changes

May 02 17:45:21 syncloud slapd[1449]: conn=1044 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text=

May 02 17:45:21 syncloud slapd[1449]: <= mdb_equality_candidates: (memberUid) not indexed

May 02 17:45:21 syncloud slapd[1449]: conn=1044 op=1 SRCH attr=memberUid

May 02 17:45:21 syncloud slapd[1449]: conn=1044 op=1 SRCH base=“cn=syncloud,ou=groups,dc=syncloud,dc=org” scope=2 deref=3 filter=“(memberUid=raud3rs)”

May 02 17:45:21 syncloud slapd[1449]: conn=1044 op=0 RESULT tag=97 err=0 text=

May 02 17:45:21 syncloud slapd[1449]: conn=1044 op=0 BIND dn=“cn=admin,dc=syncloud,dc=org” mech=SIMPLE ssf=0

May 02 17:45:21 syncloud slapd[1449]: conn=1044 op=0 BIND dn=“cn=admin,dc=syncloud,dc=org” method=128

May 02 17:45:21 syncloud slapd[1449]: conn=1044 fd=13 ACCEPT from IP=127.0.0.1:54640 (IP=127.0.0.1:389)

May 02 17:45:21 syncloud platform.backend[432]: info rest/middleware.go:102 GET: /rest/installer/status

May 02 17:45:21 syncloud systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid → /run/fancontrol.pid; please update the unit file accordingly.

May 02 17:45:20 syncloud systemd[1]: Reloading.

May 02 17:45:20 syncloud systemd[1]: snap-nextcloud-935.mount: Succeeded.

May 02 17:45:20 syncloud snapd[355]: -----

May 02

[boris]

Sorry did you have Nextcloud installed on this device, what version do you when you try to upgrade?

[boris]

Can you run this and show the output

snap refresh nextcloud

[raud3rs]

Yes, I have always used Nextcloud and was always on the latest version you offer. The snap command has started the download of nextcloud 937

-----)
root@syncloud:~# snap refresh nextcloud
error: cannot perform the following tasks:

• Run pre-refresh hook of “nextcloud” snap if present (run hook “pre-refresh”:

---

2026-05-03 08:50:03,204 - database - INFO - postgres executing: snap run nextcloud.pgdumpall -f /v
ar/snap/nextcloud/current/database.dump
pg_dumpall: error: connection to server on socket “/var/snap/nextcloud/current/database/.s.PGSQL.5
436” failed: No such file or directory
Is the server running locally and accepting connections on that socket?
2026-05-03 08:50:03,541 - database - ERROR - postgres error:
Traceback (most recent call last):
File “/snap/nextcloud/906/meta/hooks/pre-refresh”, line 7, in
Installer().pre_refresh()
File “/snap/nextcloud/906/hooks/installer.py”, line 127, in pre_refresh
self.db.backup()
File “/snap/nextcloud/906/hooks/postgres.py”, line 45, in backup
self.run(‘snap run nextcloud.pgdumpall -f {0}’.format(self.backup_file))
File “/snap/nextcloud/906/hooks/postgres.py”, line 55, in run
raise e
File “/snap/nextcloud/906/hooks/postgres.py”, line 51, in run
output = check_output(cmd, shell=True).decode()
File “/snap/nextcloud/current/python/usr/local/lib/python3.8/subprocess.py”, line 415, in check_
output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File “/snap/nextcloud/current/python/usr/local/lib/python3.8/subprocess.py”, line 516, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command ‘snap run nextcloud.pgdumpall -f /var/snap/nextcloud/curren
t/database.dump’ returned non-zero exit status 1.
-----)

[boris]

Could you run it again and send logs from settings please?

[boris]

Hi raud3rs,

Looking at your last refresh output, pg_dumpall is failing immediately because Postgres isn’t running at the moment the pre-refresh hook fires — that’s why you see:

connection to server on socket "/var/snap/nextcloud/current/database/.s.PGSQL.5436" failed:
No such file or directory

So this isn’t really a refresh problem yet — Postgres on the device you’re refreshing is in a stopped/failed state, and the refresh is just inheriting that. We need to figure out why Postgres won’t run before another refresh attempt will get anywhere.

On the device where the refresh fails, could you paste the output of:

snap services nextcloud
systemctl status snap.nextcloud.postgresql.service --no-pager
sudo journalctl -u snap.nextcloud.postgresql.service --since=-1h --no-pager | tail -50
ls -la /var/snap/nextcloud/current/database/postmaster.pid 2>/dev/null
sudo ls -la /var/snap/nextcloud/current/database/ | head -20

Also helpful:

snap list nextcloud
df -h /
snap changes | tail -10

That should tell us whether Postgres is crashing on start (and why), or whether it’s been stopped, or whether the data directory itself is in a bad state. Once we know that we can fix the underlying issue and your refresh should go through.

Thanks!

[raud3rs]

@boris

snap services nextcloud

This is my private raspi:

root@syncloud:\~# snap services nextcloud
Service               Startup   Current   Notes
nextcloud.nats        disabled  inactive  -
nextcloud.nginx       disabled  inactive  -
nextcloud.php-fpm     disabled  inactive  -
nextcloud.postgresql  disabled  inactive  -
nextcloud.redis       disabled  inactive  -
nextcloud.signaling   disabled  inactive  -
root@syncloud:\~# systemctl status snap.nextcloud.postgresql.service --no-pager
● snap.nextcloud.postgresql.service - Service for snap application nextcloud.postgresql
Loaded: loaded (/etc/systemd/system/snap.nextcloud.postgresql.service; disabled; vendor preset: enabled)
Active: inactive (dead)
root@syncloud:\~# sudo journalctl -u snap.nextcloud.postgresql.service --since=-1h --no-pager | tail -50
-- Logs begin at Thu 2019-02-14 10:11:58 UTC, end at Mon 2026-05-04 10:50:59 UTC. --
-- No entries --
oot@syncloud:\~# ls -la /var/snap/nextcloud/current/database/postmaster.pid 2>/dev/null
root@syncloud:\~# sudo ls -la /var/snap/nextcloud/current/database/ | head -20
total 124
drwx------ 19 nextcloud nextcloud  4096 Apr 30 23:09 .
drwxr-xr-x  6 nextcloud nextcloud  4096 Apr 30 23:38 ..
-rw-------  1 nextcloud nextcloud     3 Apr 23 23:34 PG_VERSION
drwx------  7 nextcloud nextcloud  4096 Apr 23 23:37 base
drwx------  2 nextcloud nextcloud  4096 Apr 27 15:34 global
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_commit_ts
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_dynshmem
-rw-------  1 nextcloud nextcloud  5711 Apr 23 23:34 pg_hba.conf
-rw-------  1 nextcloud nextcloud  2640 Apr 23 23:34 pg_ident.conf
drwx------  4 nextcloud nextcloud  4096 Apr 30 23:09 pg_logical
drwx------  4 nextcloud nextcloud  4096 Apr 23 23:34 pg_multixact
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_notify
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_replslot
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_serial
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_snapshots
drwx------  2 nextcloud nextcloud  4096 Apr 30 23:09 pg_stat
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_stat_tmp
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_subtrans
drwx------  2 nextcloud nextcloud  4096 Apr 23 23:34 pg_tblspc
root@syncloud:\~# snap list nextcloud
Name       Version  Rev  Tracking       Publisher  Notes
nextcloud  906      906  latest/stable  syncloud✓  -
root@syncloud:\~# df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G   15G   14G  52% /
root@syncloud:\~# snap changes | tail -10
5539  Error   yesterday at 17:17 UTC  yesterday at 17:17 UTC  Initialize device
5540  Error   yesterday at 17:32 UTC  yesterday at 17:32 UTC  Initialize device
5541  Error   yesterday at 17:57 UTC  yesterday at 17:57 UTC  Initialize device
5542  Error   yesterday at 18:42 UTC  yesterday at 18:42 UTC  Initialize device
5543  Error   yesterday at 19:52 UTC  yesterday at 19:53 UTC  Refresh "nextcloud" snap
5544  Error   yesterday at 20:02 UTC  yesterday at 20:02 UTC  Initialize device
5545  Error   yesterday at 22:47 UTC  yesterday at 22:47 UTC  Initialize device
5546  Error   yesterday at 23:47 UTC  yesterday at 23:48 UTC  Auto-refresh snap "nextcloud"
5547  Error   today at 04:07 UTC      today at 04:07 UTC      Initialize device

OUR Business raspi:

root@syncloud:\~# snap services nextcloud
Service                      Startup   Current   Notes
nextcloud.nats               disabled  inactive  -
nextcloud.nginx              disabled  inactive  -
nextcloud.php-fpm            disabled  inactive  -
nextcloud.post-start-repair  disabled  inactive  -
nextcloud.postgresql         disabled  inactive  -
nextcloud.redis              disabled  inactive  -
nextcloud.signaling          disabled  inactive  -
root@syncloud:\~# systemctl status snap.nextcloud.postgresql.service --no-pager
● snap.nextcloud.postgresql.service - Service for snap application nextcloud.postgresql
Loaded: loaded (/etc/systemd/system/snap.nextcloud.postgresql.service; disabled; vendor preset: enabled)
Active: inactive (dead) since Mon 2026-05-04 13:12:48 CEST; 9min ago
Main PID: 9160 (code=exited, status=0/SUCCESS)

May 04 13:12:02 syncloud systemd\[1\]: Started Service for snap application nextcloud.postgresql.
May 04 13:12:48 syncloud nextcloud.postgres\[9160\]: \[5-1\] 2026-05-04 11:12:48.534 GMT \[9160\] LOG:  received smart shut...request
May 04 13:12:48 syncloud systemd\[1\]: Stopping Service for snap application nextcloud.postgresql...
May 04 13:12:48 syncloud nextcloud.postgres\[9160\]: \[6-1\] 2026-05-04 11:12:48.548 GMT \[9160\] LOG:  background worker "... code 1
May 04 13:12:48 syncloud nextcloud.postgres\[9165\]: \[4-1\] 2026-05-04 11:12:48.552 GMT \[9165\] LOG:  shutting down
May 04 13:12:48 syncloud nextcloud.postgres\[9165\]: \[5-1\] 2026-05-04 11:12:48.561 GMT \[9165\] LOG:  checkpoint starting...mediate
May 04 13:12:48 syncloud nextcloud.postgres\[9165\]: \[6-1\] 2026-05-04 11:12:48.668 GMT \[9165\] LOG:  checkpoint complete: wrote...
May 04 13:12:48 syncloud nextcloud.postgres\[9160\]: \[7-1\] 2026-05-04 11:12:48.735 GMT \[9160\] LOG:  database system is ...ut down
May 04 13:12:48 syncloud systemd\[1\]: snap.nextcloud.postgresql.service: Succeeded.
May 04 13:12:48 syncloud systemd\[1\]: Stopped Service for snap application nextcloud.postgresql.
Hint: Some lines were ellipsized, use -l to show in full.
oot@syncloud:\~# sudo journalctl -u snap.nextcloud.postgresql.service --since=-1h --no-pager | tail -50
May 04 13:02:00 syncloud nextcloud.postgres\[3292\]: \[7-1\] 2026-05-04 11:02:00.618 GMT \[3292\] LOG:  database system is shut dow
n
May 04 13:02:00 syncloud systemd\[1\]: snap.nextcloud.postgresql.service: Succeeded.
May 04 13:02:00 syncloud systemd\[1\]: Stopped Service for snap application nextcloud.postgresql.
May 04 13:07:59 syncloud systemd\[1\]: Starting Service for snap application nextcloud.postgresql...
May 04 13:07:59 syncloud nextcloud.postgres\[8638\]: \[1-1\] 2026-05-04 11:07:59.956 GMT \[8638\] LOG:  ending log output to stderr
May 04 13:07:59 syncloud nextcloud.postgresql\[8591\]: 2026-05-04 11:07:59.956 GMT \[8638\] LOG:  ending log output to stderr
May 04 13:07:59 syncloud nextcloud.postgresql\[8591\]: 2026-05-04 11:07:59.956 GMT \[8638\] HINT:  Future log output will go to l
og destination "syslog".
May 04 13:07:59 syncloud nextcloud.postgres\[8638\]: \[1-2\] 2026-05-04 11:07:59.956 GMT \[8638\] HINT:  Future log output will go
to log destination "syslog".
May 04 13:07:59 syncloud nextcloud.postgres\[8638\]: \[2-1\] 2026-05-04 11:07:59.957 GMT \[8638\] LOG:  starting PostgreSQL 16.9 (D
ebian 16.9-1.pgdg110+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
May 04 13:07:59 syncloud nextcloud.postgres\[8638\]: \[3-1\] 2026-05-04 11:07:59.969 GMT \[8638\] LOG:  listening on Unix socket "/
var/snap/nextcloud/current/database/.s.PGSQL.5436"
May 04 13:08:00 syncloud nextcloud.postgres\[8645\]: \[4-1\] 2026-05-04 11:08:00.016 GMT \[8645\] LOG:  database system was shut do
wn at 2026-05-04 11:07:56 GMT
May 04 13:08:00 syncloud nextcloud.postgres\[8638\]: \[4-1\] 2026-05-04 11:08:00.064 GMT \[8638\] LOG:  database system is ready to
accept connections
May 04 13:08:00 syncloud systemd\[1\]: Started Service for snap application nextcloud.postgresql.
May 04 13:09:02 syncloud nextcloud.postgres\[8831\]: \[5-1\] 2026-05-04 11:09:02.560 GMT \[8831\] FATAL:  role "oc_installer" does
not exist
May 04 13:09:02 syncloud nextcloud.postgres\[8832\]: \[5-1\] 2026-05-04 11:09:02.609 GMT \[8832\] FATAL:  role "oc_installer" does
not exist
May 04 13:09:03 syncloud nextcloud.postgres\[8852\]: \[5-1\] 2026-05-04 11:09:03.852 GMT \[8852\] FATAL:  role "oc_installer" does
not exist
May 04 13:09:03 syncloud nextcloud.postgres\[8853\]: \[5-1\] 2026-05-04 11:09:03.873 GMT \[8853\] FATAL:  role "oc_installer" does
not exist
May 04 13:09:06 syncloud nextcloud.postgres\[8905\]: \[5-1\] 2026-05-04 11:09:06.280 GMT \[8905\] ERROR:  role "nextcloud" already
exists
May 04 13:09:06 syncloud nextcloud.postgres\[8905\]: \[5-2\] 2026-05-04 11:09:06.280 GMT \[8905\] STATEMENT:  CREATE ROLE nextcloud
;
May 04 13:10:20 syncloud nextcloud.postgres\[8929\]: \[5-1\] 2026-05-04 11:10:20.205 GMT \[8929\] LOG:  skipping vacuum of "oc_acti
vity" --- lock not available
May 04 13:10:32 syncloud nextcloud.postgres\[8929\]: \[6-1\] 2026-05-04 11:10:32.176 GMT \[8929\] ERROR:  canceling autovacuum task
May 04 13:10:32 syncloud nextcloud.postgres\[8929\]: \[6-2\] 2026-05-04 11:10:32.176 GMT \[8929\] CONTEXT:  automatic vacuum of tab
le "nextcloud.public.oc_filecache"
May 04 13:11:31 syncloud nextcloud.postgres\[8638\]: \[5-1\] 2026-05-04 11:11:31.671 GMT \[8638\] LOG:  received smart shutdown req
uest
May 04 13:11:31 syncloud systemd\[1\]: Stopping Service for snap application nextcloud.postgresql...
May 04 13:11:31 syncloud nextcloud.postgres\[8638\]: \[6-1\] 2026-05-04 11:11:31.684 GMT \[8638\] LOG:  background worker "logical
replication launcher" (PID 8648) exited with exit code 1
May 04 13:11:31 syncloud nextcloud.postgres\[8643\]: \[4-1\] 2026-05-04 11:11:31.693 GMT \[8643\] LOG:  shutting down
May 04 13:11:31 syncloud nextcloud.postgres\[8643\]: \[5-1\] 2026-05-04 11:11:31.703 GMT \[8643\] LOG:  checkpoint starting: shutdo
wn immediate
May 04 13:11:37 syncloud nextcloud.postgres\[8643\]: \[6-1\] 2026-05-04 11:11:37.600 GMT \[8643\] LOG:  checkpoint complete: wrote
14029 buffers (85.6%); 0 WAL file(s) added, 0 removed, 19 recycled; write=2.990 s, sync=2.677 s, total=5.908 s; sync files=17
36, longest=0.873 s, average=0.002 s; distance=317474 kB, estimate=317474 kB; lsn=0/14AEEA20, redo lsn=0/14AEEA20
May 04 13:11:37 syncloud nextcloud.postgres\[8638\]: \[7-1\] 2026-05-04 11:11:37.811 GMT \[8638\] LOG:  database system is shut dow
n
May 04 13:11:37 syncloud systemd\[1\]: snap.nextcloud.postgresql.service: Succeeded.
May 04 13:11:37 syncloud systemd\[1\]: Stopped Service for snap application nextcloud.postgresql.
May 04 13:12:00 syncloud systemd\[1\]: Starting Service for snap application nextcloud.postgresql...
May 04 13:12:01 syncloud nextcloud.postgres\[9160\]: \[1-1\] 2026-05-04 11:12:01.980 GMT \[9160\] LOG:  ending log output to stderr
May 04 13:12:01 syncloud nextcloud.postgres\[9160\]: \[1-2\] 2026-05-04 11:12:01.980 GMT \[9160\] HINT:  Future log output will go
to log destination "syslog".
May 04 13:12:01 syncloud nextcloud.postgresql\[9130\]: 2026-05-04 11:12:01.980 GMT \[9160\] LOG:  ending log output to stderr
May 04 13:12:01 syncloud nextcloud.postgresql\[9130\]: 2026-05-04 11:12:01.980 GMT \[9160\] HINT:  Future log output will go to l
og destination "syslog".
May 04 13:12:01 syncloud nextcloud.postgres\[9160\]: \[2-1\] 2026-05-04 11:12:01.980 GMT \[9160\] LOG:  starting PostgreSQL 16.9 (D
ebian 16.9-1.pgdg110+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
May 04 13:12:01 syncloud nextcloud.postgres\[9160\]: \[3-1\] 2026-05-04 11:12:01.992 GMT \[9160\] LOG:  listening on Unix socket "/
var/snap/nextcloud/current/database/.s.PGSQL.5436"
May 04 13:12:02 syncloud nextcloud.postgres\[9167\]: \[4-1\] 2026-05-04 11:12:02.040 GMT \[9167\] LOG:  database system was shut do
wn at 2026-05-04 11:02:00 GMT
May 04 13:12:02 syncloud nextcloud.postgres\[9160\]: \[4-1\] 2026-05-04 11:12:02.081 GMT \[9160\] LOG:  database system is ready to
accept connections
May 04 13:12:02 syncloud systemd\[1\]: Started Service for snap application nextcloud.postgresql.
May 04 13:12:48 syncloud nextcloud.postgres\[9160\]: \[5-1\] 2026-05-04 11:12:48.534 GMT \[9160\] LOG:  received smart shutdown req
uest
May 04 13:12:48 syncloud systemd\[1\]: Stopping Service for snap application nextcloud.postgresql...
May 04 13:12:48 syncloud nextcloud.postgres\[9160\]: \[6-1\] 2026-05-04 11:12:48.548 GMT \[9160\] LOG:  background worker "logical
replication launcher" (PID 9170) exited with exit code 1
May 04 13:12:48 syncloud nextcloud.postgres\[9165\]: \[4-1\] 2026-05-04 11:12:48.552 GMT \[9165\] LOG:  shutting down
May 04 13:12:48 syncloud nextcloud.postgres\[9165\]: \[5-1\] 2026-05-04 11:12:48.561 GMT \[9165\] LOG:  checkpoint starting: shutdo
wn immediate
May 04 13:12:48 syncloud nextcloud.postgres\[9165\]: \[6-1\] 2026-05-04 11:12:48.668 GMT \[9165\] LOG:  checkpoint complete: wrote
23 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.024 s, sync=0.051 s, total=0.116 s; sync files=11, lon
gest=0.042 s, average=0.005 s; distance=127 kB, estimate=127 kB; lsn=0/164399A8, redo lsn=0/164399A8
May 04 13:12:48 syncloud nextcloud.postgres\[9160\]: \[7-1\] 2026-05-04 11:12:48.735 GMT \[9160\] LOG:  database system is shut dow
n
May 04 13:12:48 syncloud systemd\[1\]: snap.nextcloud.postgresql.service: Succeeded.
May 04 13:12:48 syncloud systemd\[1\]: Stopped Service for snap application nextcloud.postgresql.
root@syncloud:\~# ls -la /var/snap/nextcloud/current/database/postmaster.pid 2>/dev/null
root@syncloud:\~# sudo ls -la /var/snap/nextcloud/current/database/ | head -20
total 124
drwx------ 19 nextcloud nextcloud  4096 May  4 13:12 .
drwxr-xr-x  6 nextcloud nextcloud  4096 May  4 13:12 ..
drwx------  7 nextcloud nextcloud  4096 May  2 19:25 base
drwx------  2 nextcloud nextcloud  4096 May  4 13:12 global
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_commit_ts
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_dynshmem
-rw-------  1 nextcloud nextcloud  5711 May  2 19:22 pg_hba.conf
-rw-------  1 nextcloud nextcloud  2640 May  2 19:22 pg_ident.conf
drwx------  4 nextcloud nextcloud  4096 May  4 13:12 pg_logical
drwx------  4 nextcloud nextcloud  4096 May  2 19:22 pg_multixact
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_notify
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_replslot
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_serial
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_snapshots
drwx------  2 nextcloud nextcloud  4096 May  4 13:12 pg_stat
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_stat_tmp
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_subtrans
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_tblspc
drwx------  2 nextcloud nextcloud  4096 May  2 19:22 pg_twophase

root@syncloud:\~# snap list nextcloud 
Name       Version  Rev  Tracking       Publisher  Notes 
nextcloud  935      935  latest/stable  syncloud✓  -

root@syncloud:\~# df -h / 
Filesystem      Size  Used Avail Use% Mounted on 
/dev/root       117G   15G   98G  13% / 
root@syncloud:\~# snap changes | tail -10 
3932  Error   today at 09:21 CEST      today at 09:22 CEST      Refresh "nextcloud" snap 
3934  Error   today at 09:32 CEST      today at 09:32 CEST      Initialize device 
3935  Error   today at 09:40 CEST      today at 09:55 CEST      Refresh "nextcloud" snap 
3936  Error   today at 09:42 CEST      today at 09:42 CEST      Initialize device 
3937  Error   today at 10:07 CEST      today at 10:07 CEST      Initialize device 
3938  Error   today at 10:52 CEST      today at 10:52 CEST      Initialize device 
3939  Error   today at 12:12 CEST      today at 12:12 CEST      Initialize device 
3940  Error   today at 12:59 CEST      today at 13:12 CEST      Refresh "nextcloud" snap 
3941  Error   today at 13:17 CEST      today at 13:18 CEST      Refresh "nextcloud" snap 

No update possible

[boris]

Hi raud3rs,

Thanks for the dump from both Pis. The pattern is the same on both — every nextcloud snap service is administratively disabled (Startup: disabled, Current: inactive), so postgres isn’t running, which is why pre-refresh pg_dumpall fails with the socket-missing error. Your DB directories on both Pis look intact, so the data is fine — we just need to bring services back up.

Please run these on each Pi separately, paste the output, and DO NOT trigger a refresh yet — we want to confirm Nextcloud is healthy at the running revision first.

=== Private Pi (rev 906) ===

echo --- enable + start ---
snap start --enable nextcloud
sleep 10
echo --- services ---
snap services nextcloud
echo --- postgres journal last 2m ---
journalctl -u snap.nextcloud.postgresql.service --since=-2m --no-pager | tail -30
echo --- can we connect ---
snap run nextcloud.psql -d nextcloud -c "\du" 2>&1 | head -20

=== Business Pi (rev 935) ===

echo --- enable + start ---
snap start --enable nextcloud
sleep 10
echo --- services ---
snap services nextcloud
echo --- postgres journal last 2m ---
journalctl -u snap.nextcloud.postgresql.service --since=-2m --no-pager | tail -30
echo --- config.php dbuser/installed ---
grep -E "dbuser|dbname|installed" /var/snap/nextcloud/current/nextcloud/config/config.php 2>/dev/null
echo --- can we connect ---
snap run nextcloud.psql -d nextcloud -c "\du" 2>&1 | head -20

What we expect to see:

• Private Pi: services come up, postgres reports “database system is ready to accept connections”, and \du lists role nextcloud. If that’s the case, your web UI may already be working again — please test it before considering a refresh.

• Business Pi: same start-up flow, plus we want to see what config.php currently has for dbuser/installed. The journal showed Nextcloud trying to log in as oc_installer (which doesn’t exist as a Postgres role) and a separate CREATE ROLE nextcloud failing because it already exists — that suggests the Configure hook on rev 935 ran the fresh-install path on top of an existing cluster. We need to see the current config.php contents before deciding how to fix it.

If postgres does NOT come up cleanly on either Pi, please don’t delete the data directory — paste the journal output and we’ll work out the real cause. The DB is the only copy of your data.

Thanks!

[raud3rs]

Private Pi (rev 906)

It Works but I try to make the update…now I wait..no update.

root@syncloud:\~# echo --- enable + start ---
--- enable + start ---
root@syncloud:\~# snap start --enable nextcloud
Started.
root@syncloud:\~# sleep 10
root@syncloud:\~# echo --- services ---
--- services ---
root@syncloud:\~# snap services nextcloud
Service               Startup  Current  Notes
nextcloud.nats        enabled  active   -
nextcloud.nginx       enabled  active   -
nextcloud.php-fpm     enabled  active   -
nextcloud.postgresql  enabled  active   -
nextcloud.redis       enabled  active   -
nextcloud.signaling   enabled  active   -
root@syncloud:\~# echo --- postgres journal last 2m ---
--- postgres journal last 2m ---
root@syncloud:\~# journalctl -u snap.nextcloud.postgresql.service --since=-2m --no-pager | tail -30
-- Logs begin at Thu 2019-02-14 10:11:58 UTC, end at Mon 2026-05-04 12:29:27 UTC. --
May 04 12:28:46 syncloud systemd\[1\]: Starting Service for snap application nextcloud.postgresql...
May 04 12:29:01 syncloud nextcloud.postgres\[20271\]: \[1-1\] 2026-05-04 12:29:01.146 GMT \[20271\] LOG:  ending log
output to stderr
May 04 12:29:01 syncloud nextcloud.postgres\[20271\]: \[1-2\] 2026-05-04 12:29:01.146 GMT \[20271\] HINT:  Future lo
g output will go to log destination "syslog".
May 04 12:29:01 syncloud nextcloud.postgresql\[20182\]: 2026-05-04 12:29:01.146 GMT \[20271\] LOG:  ending log out
put to stderr
May 04 12:29:01 syncloud nextcloud.postgresql\[20182\]: 2026-05-04 12:29:01.146 GMT \[20271\] HINT:  Future log ou
tput will go to log destination "syslog".
May 04 12:29:01 syncloud nextcloud.postgres\[20271\]: \[2-1\] 2026-05-04 12:29:01.146 GMT \[20271\] LOG:  starting P
ostgreSQL 16.9 (Debian 16.9-1.pgdg110+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.
1 20210110, 64-bit
May 04 12:29:01 syncloud nextcloud.postgres\[20271\]: \[3-1\] 2026-05-04 12:29:01.373 GMT \[20271\] LOG:  listening
on Unix socket "/var/snap/nextcloud/current/database/.s.PGSQL.5436"
May 04 12:29:01 syncloud nextcloud.postgres\[20282\]: \[4-1\] 2026-05-04 12:29:01.887 GMT \[20282\] LOG:  database s
ystem was shut down at 2026-04-30 23:09:53 GMT
May 04 12:29:01 syncloud nextcloud.postgres\[20271\]: \[4-1\] 2026-05-04 12:29:01.990 GMT \[20271\] LOG:  database s
ystem is ready to accept connections
May 04 12:29:02 syncloud systemd\[1\]: Started Service for snap application nextcloud.postgresql.
root@syncloud:\~# echo --- can we connect ---
--- can we connect ---
root@syncloud:\~# snap run nextcloud.psql -d nextcloud -c "\\du" 2>&1 | head -20
List of roles
Role name   |                         Attributes
--------------+------------------------------------------------------------
nextcloud    | Superuser, Create role, Create DB, Replication, Bypass RLS
oc_installer | Create DB

Business Pi (rev 935)

It Works but still in maintenace

root@syncloud:\~# echo --- enable + start ---
--- enable + start ---
root@syncloud:\~# snap start --enable nextcloud
Started.
root@syncloud:\~# sleep 10
root@syncloud:\~# echo --- services ---
--- services ---
root@syncloud:\~# snap services nextcloud
Service                      Startup  Current   Notes
nextcloud.nats               enabled  active    -
nextcloud.nginx              enabled  active    -
nextcloud.php-fpm            enabled  active    -
nextcloud.post-start-repair  enabled  inactive  -
nextcloud.postgresql         enabled  active    -
nextcloud.redis              enabled  active    -
nextcloud.signaling          enabled  active    -
root@syncloud:\~# echo --- postgres journal last 2m ---
--- postgres journal last 2m ---
root@syncloud:\~# journalctl -u snap.nextcloud.postgresql.service --since=-2m --no-pager | tail -30
-- Logs begin at Thu 2019-02-14 11:11:59 CET, end at Mon 2026-05-04 14:50:16 CEST. --
May 04 14:49:55 syncloud systemd\[1\]: Starting Service for snap application nextcloud.postgresql...
May 04 14:49:56 syncloud nextcloud.postgres\[12069\]: \[1-1\] 2026-05-04 12:49:56.013 GMT \[12069\] LOG:  ending log
output to stderr
May 04 14:49:56 syncloud nextcloud.postgresql\[12013\]: 2026-05-04 12:49:56.013 GMT \[12069\] LOG:  ending log out
put to stderr
May 04 14:49:56 syncloud nextcloud.postgresql\[12013\]: 2026-05-04 12:49:56.013 GMT \[12069\] HINT:  Future log ou
tput will go to log destination "syslog".
May 04 14:49:56 syncloud nextcloud.postgres\[12069\]: \[1-2\] 2026-05-04 12:49:56.013 GMT \[12069\] HINT:  Future lo
g output will go to log destination "syslog".
May 04 14:49:56 syncloud nextcloud.postgres\[12069\]: \[2-1\] 2026-05-04 12:49:56.013 GMT \[12069\] LOG:  starting P
ostgreSQL 16.9 (Debian 16.9-1.pgdg110+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.
1 20210110, 64-bit
May 04 14:49:56 syncloud nextcloud.postgres\[12069\]: \[3-1\] 2026-05-04 12:49:56.024 GMT \[12069\] LOG:  listening
on Unix socket "/var/snap/nextcloud/current/database/.s.PGSQL.5436"
May 04 14:49:56 syncloud nextcloud.postgres\[12076\]: \[4-1\] 2026-05-04 12:49:56.070 GMT \[12076\] LOG:  database s
ystem was shut down at 2026-05-04 11:12:48 GMT
May 04 14:49:56 syncloud nextcloud.postgres\[12069\]: \[4-1\] 2026-05-04 12:49:56.109 GMT \[12069\] LOG:  database s
ystem is ready to accept connections
May 04 14:49:56 syncloud systemd\[1\]: Started Service for snap application nextcloud.postgresql.
root@syncloud:\~# echo --- config.php dbuser/installed ---
--- config.php dbuser/installed ---
root@syncloud:\~# grep -E "dbuser|dbname|installed" /var/snap/nextcloud/current/nextcloud/config/config.php 2>/
dev/null
'dbname' => 'nextcloud',
'dbuser' => 'oc_installer',
'installed' => true,
root@syncloud:\~# echo --- can we connect ---
--- can we connect ---
root@syncloud:\~# snap run nextcloud.psql -d nextcloud -c "\\du" 2>&1 | head -20
List of roles
Role name   |                         Attributes
--------------+------------------------------------------------------------
nextcloud    | Superuser, Create role, Create DB, Replication, Bypass RLS
oc_installer | Create DB

[raud3rs]

Hello Boris,

Private: It functions, but an update is not possible.

Business: I had the wrong idea regarding the refresh. I apologise (you may strike me for this). It upgraded to 940, but it did not function; the log has been sent.

[raud3rs]

Greetings, Boris. Miracles do indeed occur. This morning, updates were successfully applied to version 943 on both devices. While the private instance functions flawlessly, the business instance reports an error, though the synchronisation applications remain operational. The aforementioned error message appears within the browser. (Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.) I executed the command ‘snap run nextcloud.occ maintenance:repair’, as you previously advised when this odyssey commenced, yet regrettably, to no avail.

[raud3rs]

Update: I executed the commands ‘snap run nextcloud.occ maintenance:mode --on’ followed by ‘snap run nextcloud.occ maintenance:mode --off’, and everything is now functioning perfectly. Many thanks for your diligent efforts. Warm regards from Berlin, Rudy.