What type of hardware are you using: VPS bought online What YunoHost version are you running: 12.0.11 How are you able to access your server: The webadmin Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no
Describe your issue
After running the migration Yunohost 11 → 12 and the post-uprade migrations, migration 29 (Postgreqsl 13 → 15) fails and is never ending.
The log shows some localized messages concerning no disk space available, but I checked with df that 27.6GB free disk space is available.
Your database is 51G large. You need twice that of free space to migrate your database.
A workaround is to set the temporary folder on a larger disk export PGHOST=/path/to/larger/disk/tmp then rerun the migration
Edit : I have searched how to optimize postgresql database, there are some commands “VACUUM FULL” “ANALYZE” “REINDEX DATABASE”. I didn’t read the whole thing but it is possible to reduce the database size on disk by removing leftovers
Now I have additional disk storage at /mnt/plusdisk via nfs. df shows 104857280 free bytes, although I ordered 250GB. So it’s only almost double of 51G.
I am trying to undestand the logfile better. I improved it by replacing all \n with \n in gedit.
The first error message is:
Copying
user relation files
Fehler beim Kopieren von Relation
\xc2\xbbpublic.state_groups_state_type_idx\xc2\xab: konnte Datei \xc2\xbb/var/lib/postgresql/15/main/base/16401/17779.1\xc2\xab
nicht schreiben: Auf dem Ger\xc3\xa4t ist kein Speicherplatz mehr verf\xc3\xbcgbar
Fehlgeschlagen,
Programm wird beendet
Cluster is not running.
''
stderr:
b''Error: pg_upgrade run failed. Logfiles are in /var/log/postgresql/pg_upgradecluster-13-15-main.0YZD
Error
during cluster dumping, removing new cluster
Error: could not stop old cluster,
please do that manually
'
That means the first error says, it could not write the file \xc2\xbb/var/lib/postgresql/15/main/base/16401/17779.1\xc2\xab because there is no more memory/storage available on the device.
Could not stop the old cluster comes later.
This is all I can do. How can we get more debugging information?