I am facing the following error while updating the discourse. Please help to resolve. FAILED -------------------- Pups::ExecError: cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock) failed with return # Location of failure: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,\"\"); print $0 }' Gemfile.lock)", "find $home ! -user discourse -exec chown discourse {} \\+"]} 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. 536bd1f80226f1b8a1d434d4283f549ca181601d79ea9a786d2932047ad93a25

[图片] Ankur: OS: Linux ask 3.13.0-79-generic This kernel is too old, you need to update it.

after running do-release-update command, it is not accessible via ssh [image]

[图片] Ankur: ==================== SERIOUS PROBLEM!!!! ==================== app not running! Attempting to rebuild how to run the app, as shown in the error log app is not running.

cd /var/discourse ./launcher start app

New error occurred Discourse version at ask.pharmaguideline.com: NOT FOUND root@ask:/var/discourse# ./discourse-doctor DISCOURSE DOCTOR Sun 29 Jan 2023 07:24:05 AM EST OS: Linux ask 3.13.0-79-generic #123-Ubuntu SMP Fri Feb 19 14:27:58 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Found containers/app.yml ==================== YML SETTINGS ==================== DISCOURSE_HOSTNAME=****************** SMTP_ADDRESS=************ DEVELOPER_EMAILS=************ SMTP_PASSWORD=************** # required, WARNING the char '#' in pw can cause problems! SMTP_PORT=587 # (optional, default 587) SMTP_USER_NAME=****************** # required LETSENCRYPT_ACCOUNT_EMAIL=***************** ==================== DOCKER INFO ==================== DOCKER VERSION: Docker version 19.03.13, build 4484c46d9d DOCKER PROCESSES (docker ps -a) CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d8f0766fe33d local_discourse/app "/sbin/boot" 5 months ago Up 9 seconds 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app d8f0766fe33d local_discourse/app "/sbin/boot" 5 months ago Up 9 seconds 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app Discourse container app is running ==================== PLUGINS ==================== - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/discourse/discourse-topic-group-button.git - git clone https://github.com/discourse/discourse-solved.git - git clone https://github.com/discourse/discourse-cakeday.git - git clone https://github.com/discourse/discourse-push-notifications.git - git clone https://github.com/discourse/discourse-assign.git - git clone https://github.com/discourse/discourse-plugin-linkedin-auth.git - git clone https://github.com/discourse/discourse-adplugin.git - git clone https://github.com/discourse/discourse-data-explorer.git - git clone https://github.com/discourse/discourse-whos-online.git - git clone https://github.com/discourse/discourse-chat-integration.git - git clone https://github.com/discourse/discourse-translator.git No non-official plugins detected. See https://github.com/discourse/discourse/blob/main/lib/plugin/metadata.rb for the official list. ======================================== Discourse version at ask.pharmaguideline.com: NOT FOUND

Hi there, I’m having the same problem on a brand new test installation. I also have the mysql-dep-template.yml enabled because it’s for a test forum import. This process has worked consistently for me many times over the past few months. But now It fails to ./launcher bootstrap app . Looking back through the bootstrap output I wonder if the additional repo https://dl.yarnpkg.com/debian for the Debian base Docker image that Discourse uses has changed its repo key and is preventing some package from being installed into the container? 2: actionmailer (7.0.4.1) from /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/actionmailer-7.0.4.1.gemspec Bundle complete! 135 Gemfile dependencies, 172 gems now installed. Gems in the groups 'test' and 'development' were not installed. Bundled gems are installed into `./vendor/bundle` I, [2023-01-29T13:08:02.394673 #1] INFO -- : > cd /var/www/discourse && echo "gem 'mysql2'" >> Gemfile I, [2023-01-29T13:08:02.396956 #1] INFO -- : I, [2023-01-29T13:08:02.397059 #1] INFO -- : > cd /var/www/discourse && apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed. I, [2023-01-29T13:08:04.131013 #1] INFO -- : Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB] Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Get:4 http://deb.debian.org/debian bullseye-backports InRelease [49.0 kB] Get:5 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB] Get:6 http://deb.debian.org/debian bullseye/main amd64 Packages [8,183 kB] Get:7 https://deb.nodesource.com/node_18.x bullseye InRelease [4,586 B] Get:8 http://apt.postgresql.org/pub/repos/apt bullseye-pgdg InRelease [91.7 kB] Get:9 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [216 kB] Get:10 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [14.6 kB] Get:11 http://deb.debian.org/debian bullseye-backports/main amd64 Packages [384 kB] Err:5 https://dl.yarnpkg.com/debian stable InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging Get:12 https://deb.nodesource.com/node_18.x bullseye/main amd64 Packages [774 B] Get:13 http://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 Packages [268 kB] Reading package lists... I, [2023-01-29T13:08:04.131367 #1] INFO -- : Terminating async processes I, [2023-01-29T13:08:04.131403 #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-01-29T13:08:04.131434 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103 103:signal-handler (1674997684) Received SIGTERM scheduling shutdown... 2023-01-29 13:08:04.131 UTC [42] LOG: received fast shutdown request 2023-01-29 13:08:04.133 UTC [42] LOG: aborting any active transactions 2023-01-29 13:08:04.134 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1 2023-01-29 13:08:04.134 UTC [46] LOG: shutting down 2023-01-29 13:08:04.154 UTC [42] LOG: database system is shut down 103:M 29 Jan 2023 13:08:04.205 # User requested shutdown... 103:M 29 Jan 2023 13:08:04.205 * Saving the final RDB snapshot before exiting. 103:M 29 Jan 2023 13:08:04.207 * DB saved on disk 103:M 29 Jan 2023 13:08:04.207 # Redis is now ready to exit, bye bye... FAILED -------------------- Pups::ExecError: cd /var/www/discourse && apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev failed with return # Location of failure: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn' exec failed with the params {"cd"=>"$home", "cmd"=>["echo \"gem 'mysql2'\" >> Gemfile", "apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev", "su discourse -c 'bundle config unset deployment'", "su discourse -c 'bundle install --no-deployment --path vendor/bundle --jobs 4 --without test development'"]} bootstrap failed with exit code 100 ** 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.

Upon closer inspection it looks like this is a different error. [图片] Discourse now stops loading at login dialog when viewed with any browser Self-hosting apt-get install -y libmariadb-dev This looks like it’s left over from an importer template. I would try removing this line from the top of app.yml - "templates/import/mysql-dep.template.yml" [图片] MySQL dep template for imports broken Migration Hi there, it looks like something has broken in templates/import/mysql-dep.template.yml . This process has worked consistently for me many times over the past few months. But now It fails to ./launcher bootstrap app when mysql-dep.template.yml is enabled, but it succeeds if it’s removed. This appears to be the same error too: Looking back through the bootstrap output I wonder if the additional repo https://dl.yarnpkg.com/debian for the Debian base Docker image that Discourse uses has changed…

That’s a different error. Would be best to post in a new thread. Thanks for including a good proportion of the log. Please in your new thread add the output of discourse-doctor whether you are running a standard install the version of OS you are running in every case, before upgrading, everyone should take a backup copy that backup to their local system or to another safe place

I do hope you took a backup and have a safe copy of it before you started the first upgrade. Your kernel is too old, because your OS version is very old. As pointed out upthread, you have limited options for updating your kernel. Upgrading your OS in place will probably be lengthy and difficult. The usual advice is to start up a fresh new OS, install discourse, and restore your backup. (Ideally, don’t delete anything existing until your new world is completely working. If you end up on a new instance with a new IP address, you’ll need to update your DNS)

I am unable to update the kernel and facing errors at different stages of the update. I don’t have a backup on my PC but I have a backup in the forum.

Having a safe copy of a backup is probably the top priority. (I take the backup in the usual way from the web page, then copy to my own machine, then take a safe copy of that copy onto another disk or offsite.)

Discourse 更新错误

产品支持安装

rahim123 2023 年1 月 29 日 13:51 20

仔细检查后，这似乎是另一个错误。

话题		回复	浏览量
Unable to boostrap Discourse since last upgrade Self-hosting	4	868	2023 年1 月 22 日
Latest site upgrade not working Self-hosting	10	1985	2022 年2 月 22 日
" undefined method `deprecated?' for nil:NilClass" on rebuild Self-hosting	22	2695	2023 年1 月 23 日
Update Not Completed and Discourse not opening Self-hosting	16	826	2024 年6 月 17 日
Bootstrap failure during most recent upgrade Self-hosting	6	699	2023 年2 月 3 日

Discourse 更新错误

相关话题