I have the symptoms described at Error Updating from 3.4.0.beta3-dev to 3.4.0.beta3
Only the error is different.
I can’t quote your picture.
But it looks like you need to delete your old postgres_data_old directory. If you have space and you’re paranoid, you can rename it.
I cant figure out how to copy the weblish screen output
1 Like
This is the salient part of my message.
Maybe first check that it’s old
ls -l /var/discourse/shared/standalone/
and make sure that that backup directory is not dated today.
If you have plenty of disk space you can do something like
cd /var/discourse
cd shared/standalone
mv postgres_data_old postgres_data_delete_me
and then try again
1 Like
No joy.
I think I am duplicating Upgrade failed spectacularily
Could you share contents of your app.yml file? Redact any sensitive information before posting.
from root@localhost: /var/discourse/containers
## this is the all-in-one, standalone Discourse Docker container template
##
## After making changes to this file, you MUST rebuild
## /var/discourse/launcher rebuild app
##
## BE *VERY* CAREFUL WHEN EDITING!
## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
## visit http://www.yamllint.com/ to validate this file as needed
templates:
- "templates/postgres.template.yml"
- "templates/redis.template.yml"
- "templates/web.template.yml"
- "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
- "templates/web.ssl.template.yml"
- "templates/web.letsencrypt.ssl.template.yml"
## which TCP/IP ports should this container expose?
## If you want Discourse to share a port with another webserver like Apache or nginx,
## see https://meta.discourse.org/t/17247 for details
expose:
- "80:80" # http
- "443:443" # https
params:
db_default_text_search_config: "pg_catalog.english"
## Set db_shared_buffers to a max of 25% of the total memory.
## will be set automatically by bootstrap based on detected RAM, or you can override
db_shared_buffers: "256MB"
## can improve sorting performance, but adds memory usage per-connection
#db_work_mem: "40MB"
## Which Git revision should this container use? (default: tests-passed)
#version: tests-passed
env:
LANG: en_US.UTF-8
# DISCOURSE_DEFAULT_LOCALE: en
## How many concurrent web requests are supported? Depends on memory and CPU cores.
## will be set automatically by bootstrap based on detected CPUs, or you can override
UNICORN_WORKERS: 4
## TODO: The domain name this Discourse instance will respond to
DISCOURSE_HOSTNAME: <mydomain>
## Uncomment if you want the container to be started with the same
## hostname (-h option) as specified above (default "$hostname-$config")
#DOCKER_USE_HOSTNAME: true
## TODO: List of comma delimited emails that will be made admin and developer
## on initial signup example 'user1@example.com,user2@example.com'
DISCOURSE_DEVELOPER_EMAILS: <myemail>
## TODO: The SMTP mail server used to validate new accounts and send notifications
DISCOURSE_SMTP_ADDRESS: <mymailorg>
DISCOURSE_SMTP_PORT: <myport>
DISCOURSE_SMTP_USER_NAME: <mysmpremail>
DISCOURSE_SMTP_PASSWORD: <mypassword>
#DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true)
## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
LETSENCRYPT_ACCOUNT_EMAIL: <myemail>
## The CDN address for this Discourse instance (configured to pull)
## see https://meta.discourse.org/t/14857 for details
#DISCOURSE_CDN_URL: //discourse-cdn.example.com
## The Docker container is stateless; all data is stored in /shared
volumes:
- volume:
host: /var/discourse/shared/standalone
guest: /shared
- volume:
host: /var/discourse/shared/standalone/log/var-log
guest: /var/log
## Plugins go here
## see https://meta.discourse.org/t/19157 for details
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-solved.git
- git clone https://github.com/discourse/discourse-math.git
## Any custom commands to run after building
run:
- exec: echo "Beginning of custom commands"
## If you want to set the 'From' email address for your first registration, uncomment and change:
## After getting the first signup email, re-comment the line. It only needs to run once.
#- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"
- exec: echo "End of custom commands"
Could you confirm your Docker version? If you’re on an older version than our recommended version 24.0.7, I would suggest that you update Docker then try again.
There were similar issues reported in a separate topic and it appears that updating Docker resolved the issue there.
Docker version 20.10.7, build f0df350
cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.7 LTS (Xenial Xerus)"
Seems like you may be experiencing a similar Docker issue to the one reported in that other topic.
I suggest that you update both Ubuntu and Docker to more recent versions then try rebuilding again.
If your old app container still exists, and you have not modified the existing data files in shared/standalone/postgres_data, you may try running ./launcher start app to start the site on the old container in the meantime.
2 Likes
I went through steps to update Ubuntu and finally pressed on this.
But the screen has locked up at
Re connecting I see I have Ubuntu 18.0.4.6 LTS (Bionic Beaver)
It’ll be much easier if you create a new VM with an up-to-date OS. 18.04 is beyond end of life and 20.04 runs out in April.
If you have an up-to-date backup, create a new server, and restore that backup, completely avoiding the postgres upgrade issues.
Discourse doesn’t need postgres installed on the OS. This is another reason to start with a fresh OS.
1 Like
Thanks Jay
I have been able to restore a backup linode to another linode (linode2)
Now I need to open Discourse on linode2 so that I can get Discourse to email me a backup.
I made a new DNS setting for linode2 but I get 502 Bad Gateway when I go there.
Perhaps I have to wait a while?
Strangely discbak.softwarebydesign.com.au (linode2) is currently re-routing to discourse.softwarebydesign.com.au (on the original linode)
You can copy the backup with scp/rsync. It’s easier and faster (unless you don’t know what that means).
You really want to create a new VM with a new OS (not a backup of a server with an out-of-date os) and move to it as described at Move a Discourse site to another VPS with rsync. The one that I just copied also had some ownership issues. You probably will too.
If discbak is running the same image as the other server, I’d expect it to give you a certificate error (unless you visited http://) and then redirect to whatever is in HOSTNAME.
It is fair to say that I don’t really know what I am doing.
I have created a new VPS running Ubunto 24.0.1 LTS and am up to the instruction to
rsync -rvz example.com:/var/discourse /var
Due to my failed upgrade, example.com gives 502 bad gateway.
I am on a learning curve trying to figure out how to grant access anyway.