# Update from 3.0.0.beta16 to 3.1.0.beta2

**URL:** <https://meta.discourse.org/t/update-from-3-0-0-beta16-to-3-1-0-beta2/257663>\
**Category:** Self-hosting\
**Created:** [March 10, 2023, 3:45am UTC](https://meta.discourse.org/t/update-from-3-0-0-beta16-to-3-1-0-beta2/257663 "2023-03-10T03:45:55Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![vmsman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vmsman/32/215633_2.png) [@vmsman](https://meta.discourse.org/u/vmsman)\
**Post date:** [March 10, 2023, 3:45am UTC](https://meta.discourse.org/t/update-from-3-0-0-beta16-to-3-1-0-beta2/257663/1 "2023-03-10T03:45:56Z")

</div>

I tried to do a backup and the backup failed.

I tried to do an upgrade.

 ![upgrade screen](https://global.discourse-cdn.com/meta/original/4X/2/4/e/24e559111c7a16cd1adcd58a07b373c04fc2f7b0.png)

At first, the upgrade screen had everything disabled. I rebooted and then I was able to select the docker\_manager upgrade. That failed with:

```plaintext
rake aborted!
NoMethodError: undefined method `path' for nil:NilClass

```

So, then I opted to ssh into the server and tried a rebuild and here is what I got:

```plaintext
root@Discourse-1:/var/discourse# ./launcher rebuild app
x86_64 arch detected.
WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
............
Downloading MaxMindDB...
Compressing Javascript and Generating Source Maps

I, [2023-03-10T03:08:58.958320 #1] INFO -- : Terminating async processes
I, [2023-03-10T03:08:58.958649 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42
I, [2023-03-10T03:08:58.958745 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
103:signal-handler (1678417738) Received SIGTERM scheduling shutdown...
2023-03-10 03:08:58.959 UTC [42] LOG: received fast shutdown request
2023-03-10 03:08:58.966 UTC [42] LOG: aborting any active transactions
2023-03-10 03:08:58.969 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1
2023-03-10 03:08:58.971 UTC [46] LOG: shutting down
103:M 10 Mar 2023 03:08:59.047 # User requested shutdown...
103:M 10 Mar 2023 03:08:59.047 * Saving the final RDB snapshot before exiting.
2023-03-10 03:08:59.060 UTC [42] LOG: database system is shut down
103:M 10 Mar 2023 03:08:59.073 * DB saved on disk
103:M 10 Mar 2023 03:08:59.073 # Redis is now ready to exit, bye bye...

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' failed with return #<Process::Status: pid 1004 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"assets_precompile", "cmd"=>["su discourse -c 'bundle exec rake themes:update assets:precompile'"]}
bootstrap failed with exit code 1
**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.
e956a73644feb880e4b524bcbd4fa3c626fcfcc4edb3752f72e523194f663b4e
root@Discourse-1:/var/discourse# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
root@Discourse-1:/var/discourse# 

```

---

_[View the full topic](https://meta.discourse.org/t/update-from-3-0-0-beta16-to-3-1-0-beta2/257663)._