I was prompted to update my 2.6.0 beta 2 site to beta 3, but the update process reportedly failed for me both times I tried it (disconcerting because I don’t recall any previous updates thus far throwing errors) Weirdly, even part way through the update in progress, with the progress bar about hal…

Did you see this advice about vacuuming your database and rebuilding indexes after the recent postgresql update?

[image] Paul_King: What could possibly be filling 21GB with a 7 month old forum with 700 users, very sporadic usage, and minimal file uploading (the very occasional small image included in a post)? You can try to find out, for example at your root shell prompt: du -kx / | sort -n | tail -33 …

OK, du command (=disk usage?) reports root@nz:/var/discourse# du -kx / | sort -n | tail -33 747432 /var/lib/docker/overlay2/794d92242be8354a3ba468161d1d2ea416ab43a6f70ddd7ab060384bd5a9fcd5/diff/var/www/discourse/vendor/bundle 750792 /var/lib/docker/overlay2/794d92242be8354a3ba468161d1d2ea416ab43a…

[image] Paul_King: 2545304 Database is 2.5GB. Backups combined are 1.3GB. You’ve got several large Docker layers - are you sure that ./launcher cleanup actually completed?

./launcher cleanup gives following result for me, almost instantaneously - not sure what I am missing here… root@nz:/var/discourse# ./launcher cleanup WARNING! This will remove all stopped containers. Are you sure you want to continue? [y/N] y Total reclaimed space: 0B WARNING! This will remove all…

That large import area might be suspicious. But it’s only 640M. There are some tips here about seeing what docker is using, and trying to reduce it. (It’s possible some of the advice is wrong or dangerous.) I saw this in my rather small world: # docker volume ls -qf dangling=true # docker images …

Thanks Ed - both those things helped [image] Ed_S: There are some tips here about seeing what docker is using, and trying to reduce it. Most posts in that thread did not help, but one suggested docker system prune --all --volumes --force which cleaned more than 1GB [image] Ed_S: Did yo…

(That should be ./launcher not /launcher)

[image] Ed_S: (That should be ./launcher not /launcher) Ah - thanks Ed! That got back 2.6GB - just enough to let installation complete. Many thanks to everyone for the helpful suggestions. It still worries me a bit that I am apparently using so much space, at least as reported with Ubuntu …

if you go to yourdomain.com/admin/backups How many backups do you have there? maybe you can keep one and delete the rest.

[image] IAmGav: How many backups do you have there? Only 3 backups now @ 457 MB each - but looks like disk space headroom problem has resolved through the various clean ups… for now at least. I read in passing something about dockers accumulating ‘difference data’ and logs at a ferocious rat…

La mise à jour 2.6.0 beta 3 a échoué sur disque et/ou mémoire

Soutien Installation

Ed_S (Ed S) Septembre 26, 2020, 12:31 14

Avez-vous vu ce conseil concernant le vidage de votre base de données et la reconstruction des index après la récente mise à jour de PostgreSQL ?

4 « J'aime »

Sujet		Réponses	Vues
I keep getting errors when updating Support	26	363	Juillet 16, 2025
"Waiting for unicorn to reload", then update stops Support	30	4670	Juin 20, 2021
Problem with Upgrade [error 137] Self-hosting server-resources	32	1511	Février 11, 2024
Down after Docker Update Self-hosting server-resources	7	665	Décembre 6, 2020
Docker Manager: FAILED TO UPGRADE Self-hosting docker-manager , server-resources	7	1270	Décembre 4, 2020

La mise à jour 2.6.0 beta 3 a échoué sur disque et/ou mémoire

Sujets connexes