Problem with upgrading the latest version

installation
1

Hi, I am trying to update Discourse to the latest version.

FAILED
--------------------
Pups::ExecError: /root/upgrade_postgres failed with return #<Process::Status: pid 45 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params "/root/upgrade_postgres"
1cafe54cd6661316d8e9e393c54f73ab89bc3f5e70e104f6c5e4f8794053c09c
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.

Also

 Success. You can now start the database server using:

    pg_ctlcluster 10 main start

Warning: The selected stats_temp_directory /var/run/postgresql/10-main.pg_stat_tmp
is not writable for the cluster owner. Not adding this setting in
postgresql.conf.
Ver Cluster Port Status Owner    Data directory              Log file
10  main    5433 down   postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
update-alternatives: warning: forcing reinstallation of alternative /usr/share/postgresql/12/man/man1/postmaster.1.gz because link group postmaster.1.gz is broken
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Processing triggers for postgresql-common (213.pgdg100+1) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
Stopping PostgreSQL 10 database server: main.
Stopping PostgreSQL 12 database server: main.
Performing Consistency Checks
-----------------------------
Checking cluster versions                                   ok

The source cluster was not shut down cleanly.
Failure, exiting

Output of tail -f shared/standalone/log/var-log/postgres/current command:

2020-06-14 01:37:02.155 UTC [3508] FATAL:  data directory "/shared/postgres_data" has wrong ownership
2020-06-14 01:37:02.155 UTC [3508] HINT:  The server must be started by the user that owns the data directory.

Postponing the update

If you need to postpone the update during your next rebuild, you can swap the PostgreSQL template on your app.yml file by changing "templates/postgres.template.yml" to "templates/postgres.10.template.yml" .

This is not recommended, as some site admins will forget to revert the change afterwards.

I applied this and the Discourse forum is now online. What can we do next? Currently, I am using “templates/postgres.10.template.yml”

2

Any ideas? I am still using “templates/postgres.10.template.yml".

3

Try the following:

  1. Edit the app.yml and change "templates/postgres.10.template.yml" to "templates/postgres.template.yml" .

  2. Issue a stop: ./launcher stop app

  3. Try a rebuild ./launcher rebuild app

2 Likes
4 
Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
    ./analyze_new_cluster.sh

Running this script will delete the old cluster's data files:
    ./delete_old_cluster.sh
-------------------------------------------------------------------------------------
UPGRADE OF POSTGRES COMPLETE

Old 10 database is stored at /shared/postgres_data_old

To complete the upgrade, rebuild again using:

./launcher rebuild app

And Discourse forum offline at this time.

I am trying ./launcher rebuild app again as said above.

5

Yes that is expected.

Yeah, follow the instructions and it should be back soon.

1 Like
6

Interesting and awesome, now the update has been successfully completed. I have tried the same way many times before, but it never happened.

Do I need to use the following commands to clear the space?

Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
    ./analyze_new_cluster.sh

Running this script will delete the old cluster's data files:
    ./delete_old_cluster.sh

Thank you!

7

You can run the Post update optional tasks listed in our FAQ.

1 Like
8

Wonderful. Thanks again!

1 Like
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.