# Update from 2.9.0beta1 to beta4 failed

**URL:** <https://meta.discourse.org/t/update-from-2-9-0beta1-to-beta4-failed/224766>\
**Category:** Self-hosting\
**Created:** [April 19, 2022, 5:11pm UTC](https://meta.discourse.org/t/update-from-2-9-0beta1-to-beta4-failed/224766 "2022-04-19T17:11:46Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![sunjam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sunjam/32/175682_2.png) [@sunjam](https://meta.discourse.org/u/sunjam)\
**Post date:** [April 19, 2022, 5:11pm UTC](https://meta.discourse.org/t/update-from-2-9-0beta1-to-beta4-failed/224766/1 "2022-04-19T17:11:46Z")

</div>

```plaintext
I, [2022-04-19T19:46:59.893019 #1] INFO -- : Terminating async processes
I, [2022-04-19T19:46:59.893129 #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: 41
102:signal-handler (1650397619) Received SIGTERM scheduling shutdown...
2022-04-19 19:46:59.893 UTC [41] LOG: received fast shutdown request
I, [2022-04-19T19:46:59.894001 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 102
2022-04-19 19:46:59.907 UTC [41] LOG: aborting any active transactions
2022-04-19 19:46:59.923 UTC [41] LOG: background worker "logical replication launcher" (PID 50) exited with exit code 1
2022-04-19 19:46:59.925 UTC [45] LOG: shutting down
102:M 19 Apr 2022 19:46:59.929 # User requested shutdown...
102:M 19 Apr 2022 19:46:59.929 * Saving the final RDB snapshot before exiting.
102:M 19 Apr 2022 19:46:59.933 * DB saved on disk
102:M 19 Apr 2022 19:46:59.934 # Redis is now ready to exit, bye bye...
2022-04-19 19:47:00.190 UTC [41] LOG: database system is shut down

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 1122 exit 1>
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 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.
b6a24507cfb18de438ebaedbf731cf5fc6a2389de445e872995d58fc0af2fd1c

```

Also seeing:  
`WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.`

I’ve edited this value into /etc/sysctl.conf and restarted the server.

Still seeing  
`WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.`

> **Here is the earlier networking error. Resolved by rebuilding**
>
> ```plaintext
> I, [2022-04-19T17:02:14.450670 #1] INFO -- : > cd /var/www/discourse && [! -d 'node_modules'] || su discourse -c 'yarn install --production && yarn cache clean'
> error An unexpected error occurred: "https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.7.tgz: ESOCKETTIMEDOUT".
> error Command failed with exit code 1.
> I, [2022-04-19T17:08:24.165517 #1] INFO -- : yarn install v1.22.18
> [1/5] Validating package.json...
> [2/5] Resolving packages...
> success Already up-to-date.
> $ yarn --cwd app/assets/javascripts/discourse
> yarn install v1.22.18
> [1/4] Resolving packages...
> [2/4] Fetching packages...
> info There appears to be trouble with your network connection. Retrying...
> info There appears to be trouble with your network connection. Retrying...
> info There appears to be trouble with your network connection. Retrying...
> info There appears to be trouble with your network connection. Retrying...
> info There appears to be trouble with your network connection. Retrying...
> info There appears to be trouble with your network connection. Retrying...
> info There appears to be trouble with your network connection. Retrying...
> info There appears to be trouble with your network connection. Retrying...
> info There appears to be trouble with your network connection. Retrying...
> info If you think this is a bug, please open a bug report with the information provided in "/var/www/discourse/app/assets/javascripts/discourse/yarn-error.log".
> info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
> info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
> 
> I, [2022-04-19T17:08:24.231065 #1] INFO -- : Terminating async processes
> I, [2022-04-19T17:08:24.231265 #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-04-19T17:08:24.231439 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
> 2022-04-19 17:08:24.231 UTC [42] LOG: received fast shutdown request
> 103:signal-handler (1650388104) Received SIGTERM scheduling shutdown...
> 2022-04-19 17:08:24.251 UTC [42] LOG: aborting any active transactions
> 2022-04-19 17:08:24.259 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1
> 103:M 19 Apr 2022 17:08:24.261 # User requested shutdown...
> 103:M 19 Apr 2022 17:08:24.261 * Saving the final RDB snapshot before exiting.
> 2022-04-19 17:08:24.328 UTC [46] LOG: shutting down
> 103:M 19 Apr 2022 17:08:24.345 * DB saved on disk
> 103:M 19 Apr 2022 17:08:24.345 # Redis is now ready to exit, bye bye...
> 2022-04-19 17:08:24.837 UTC [42] LOG: database system is shut down
> 
> FAILED
> --------------------
> Pups::ExecError: cd /var/www/discourse && [! -d 'node_modules'] || su discourse -c 'yarn install --production && yarn cache clean' failed with return #<Process::Status: pid 1183 exit 1>
> 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", "cmd"=>["[! -d 'node_modules'] || su discourse -c 'yarn install --production && yarn cache clean'"]}
> 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.
> 9fdbbee859d86c2d16fa51af92a4383c29c2b55bbe77a12118a5d5cf1f8d37c5
> You have new mail in /var/mail/noisebridge
> 
> ```

---

_[View the full topic](https://meta.discourse.org/t/update-from-2-9-0beta1-to-beta4-failed/224766)._
