### Author:  [@L30110](https://meta.discourse.org/u/L30110)
#### Post date: [July 14, 2022, 4:22pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/1 "2022-07-14T16:22:49Z")
Hi all. I was prompted for a typical upgrade this morning, but the process failed midstream. I just tried to do a manual upgrade from the command line and it has failed as well. Everything was fine before this upgrade, and everything is down now. Here’s the error info, any suggestions would be greatly appreciated!
```plaintext
2022-07-14 16:14:44.668 UTC [42] LOG: aborting any active transactions
2022-07-14 16:14:44.673 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1
2022-07-14 16:14:44.680 UTC [46] LOG: shutting down
103:M 14 Jul 2022 16:14:44.830 * DB saved on disk
103:M 14 Jul 2022 16:14:44.830 # Redis is now ready to exit, bye bye...
2022-07-14 16:14:45.076 UTC [42] LOG: database system is shut down
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #
Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
bootstrap failed with exit code 134
**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.
bf24180e575747f40c769146cfc8c9557812cdabee1fb09b1aaed38e5d1f5220
```
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [July 14, 2022, 4:29pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/2 "2022-07-14T16:29:45Z")
You are going to have to share evidence of an earlier error, can you do as requested in the message and ‘scroll up’?
---
### Author:  [@L30110](https://meta.discourse.org/u/L30110)
#### Post date: [July 14, 2022, 5:10pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/3 "2022-07-14T17:10:25Z")
There is an abort just above. Included below. Thanks.
```plaintext
7fb718411000-7fb718412000 rw-p 0002a000 fd:00 57021659 /lib/x86_64-linux-gnu/ld-2.31.so
7fb718412000-7fb718413000 rw-p 00000000 00:00 0
7ffd7fe2f000-7ffd8062e000 rw-p 00000000 00:00 0 [stack]
7ffd80730000-7ffd80733000 r--p 00000000 00:00 0 [vvar]
7ffd80733000-7ffd80735000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
Aborted (core dumped)
I, [2022-07-14T16:51:29.748907 #1] INFO -- :
I, [2022-07-14T16:51:29.750246 #1] INFO -- : Terminating async processes
I, [2022-07-14T16:51:29.750362 #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, [2022-07-14T16:51:29.750493 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
2022-07-14 16:51:29.750 UTC [42] LOG: received fast shutdown request
103:signal-handler (1657817489) Received SIGTERM scheduling shutdown...
103:M 14 Jul 2022 16:51:29.761 # User requested shutdown...
103:M 14 Jul 2022 16:51:29.761 * Saving the final RDB snapshot before exiting.
2022-07-14 16:51:29.781 UTC [42] LOG: aborting any active transactions
2022-07-14 16:51:29.787 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1
2022-07-14 16:51:29.790 UTC [46] LOG: shutting down
103:M 14 Jul 2022 16:51:29.851 * DB saved on disk
103:M 14 Jul 2022 16:51:29.852 # Redis is now ready to exit, bye bye...
2022-07-14 16:51:31.563 UTC [42] LOG: database system is shut down
```
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [July 14, 2022, 5:33pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/4 "2022-07-14T17:33:17Z")
You still need to include more output. It looks like a core dump, which is lkely an OS error or hardware problem, but we’d need more info to get a better idea.
---
### Author:  [@L30110](https://meta.discourse.org/u/L30110)
#### Post date: [July 14, 2022, 5:50pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/5 "2022-07-14T17:50:12Z")
I’ll post the entire output. Ubuntu 18.04. Stable as a rock until this upgrade.
---
### Author:  [@L30110](https://meta.discourse.org/u/L30110)
#### Post date: [July 14, 2022, 5:56pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/6 "2022-07-14T17:56:42Z")
[disc.txt](https://meta.discourse.org/uploads/short-url/lyYKWrHMMVQrk5zAPW3vMH0kRim.txt) (405.8 KB)
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [July 14, 2022, 6:29pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/7 "2022-07-14T18:29:42Z")
Seems related to this: [Discourse update keeps failing - #31 by RGJ](https://meta.discourse.org/t/discourse-update-keeps-failing/231862/31)
What CPU do you have? (But the other topic might be a better place to discuss).
I’m not sure if there is a fix.
---
### Author:  [@L30110](https://meta.discourse.org/u/L30110)
#### Post date: [July 14, 2022, 7:03pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/8 "2022-07-14T19:03:52Z")
Switching over to the other thread …
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [July 14, 2022, 7:05pm UTC](https://meta.discourse.org/t/latest-upgrade-hard-fail-forum-down/232894/9 "2022-07-14T19:05:24Z")