Im not sure what I did, but I ended up attempting to upgrade via cli and did something to the forums. I tried first upgrading via the upgrade tool provided in the GUI but the site went down, so I did it through the CLI and im getting the same error
Did you perform
cd /var/discourse
./launcher rebuild app
from the command line?
If that doesn’t help, did you try ./discourse-doctor ?
Yes I did try rebuilding the app, I am rebuilding now with adplugin removed to see if that changes anything and attempt to see if safe-mode works. I did try the doctor but it just provides a lot of info that doesn’t seem any clear indication of what’s going on. Ill provide that in a few minutes once its fully rebuilt.
safe-mode does not work and here is the provided discourse-doctor:
DISCOURSE DOCTOR Sun Nov 20 08:02:54 CET 2022
OS: Linux discourse 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Found containers/app.yml
==================== YML SETTINGS ====================
DISCOURSE_HOSTNAME=forum.arcaneodyssey.dev
SMTP_ADDRESS=smtp.mailgun.org
DEVELOPER_EMAILS=REDACTED
SMTP_PASSWORD=REDACTED
SMTP_PORT=587
SMTP_USER_NAME=headless@mg.arcaneodyssey.dev
LETSENCRYPT_ACCOUNT_EMAIL=REDACTED
==================== DOCKER INFO ====================
DOCKER VERSION: Docker version 20.10.17, build 100c701
DOCKER PROCESSES (docker ps -a)
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3de708735f7f local_discourse/app "/sbin/boot" 2 minutes ago Up 2 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::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-chat-integration.git
- git clone https://github.com/discourse/discourse-whos-online.git
- git clone https://github.com/discourse/discourse-voting.git
- git clone https://github.com/discourse/discourse-checklist
- git clone https://github.com/gdpelican/retort.git
- git clone https://github.com/discourse/discourse-patreon.git
- git clone https://github.com/merefield/discourse-topic-previews.git -b "theme_sidecar"
- git clone https://github.com/discourse/discourse-calendar.git
- git clone https://github.com/discourse/discourse-spoiler-alert.git
- git clone https://github.com/discourse/discourse-solved.git
- git clone https://github.com/angusmcleod/discourse-ratings.git
- git clone https://github.com/paviliondev/discourse-follow.git
- git clone https://github.com/discourse/discourse-reactions.git
# - sudo -E -u discourse git clone https://github.com/discourse/docker_manager.git
# - git clone https://github.com/rimian/discourse-subscriptions.git
WARNING:
You have what appear to be non-official plugins.
If you are having trouble, you should disable them and try rebuilding again.
See https://github.com/discourse/discourse/blob/main/lib/plugin/metadata.rb for the official list.
========================================
Discourse version at forum.arcaneodyssey.dev: Discourse 2.9.0.beta12
Discourse version at localhost: Discourse 2.9.0.beta12
==================== MEMORY INFORMATION ====================
OS: Linux
RAM (MB): 16038
total used free shared buff/cache available
Mem: 15662 1363 3960 562 10337 13440
Swap: 2047 30 2017
==================== DISK SPACE CHECK ====================
---------- OS Disk Space ----------
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 19G 13G 5.1G 72% /
---------- Container Disk Space ----------
Filesystem Size Used Avail Use% Mounted on
overlay 19G 13G 5.1G 72% /
/dev/sdb 49G 35G 12G 75% /shared
/dev/sdb 49G 35G 12G 75% /var/log
==================== DISK INFORMATION ====================
Disk /dev/sda: 19.1 GiB, 20480786432 bytes, 40001536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: DA375F37-9B26-488D-A076-9130E80D2481
Device Start End Sectors Size Type
/dev/sda1 129024 40001502 39872479 19G Linux filesystem
/dev/sda14 2048 4095 2048 1M BIOS boot
/dev/sda15 4096 129023 124928 61M EFI System
Partition table entries are not in disk order.
Disk /dev/sdb: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sdc: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
==================== END DISK INFORMATION ====================
==================== MAIL TEST ====================
For a robust test, get an address from http://www.mail-tester.com/
Mail test skipped.
==================== DONE! ====================
The output of this program may be available at http://forum.arcaneodyssey.dev/N2EwNTllMmE1NTU2OGU5.txt
You should inspect that file carefully before sharing the URL.
You can examine the output of this script with
LESS=-Ri less /tmp/discourse-debug.txt
BUT FIRST, make sure that you know the first three commands below!!!
Commands to know when viewing the file with the above command (called 'less'):
q -- quit
/error<ENTER> -- search for the word 'error'
n -- search for the next occurrence
g -- go to the beginning of the file
f -- go forward a page
b -- go back a page
G -- go to the end of the file
Try removing the above two plugins, I think one of these two could be causing problems.
You can move from retort to reactions and from topic previews to https://github.com/paviliondev/discourse-tc-topic-list-previews and https://github.com/paviliondev/discourse-topic-previews-sidecar
2 Likes
Ill go ahead and try this, but either way should safe-mode still work? since thats not using plugins?
Safe mode won’t work if your container is throwing errors.
Gotcha, rebuilding the container now with the suggested changes, will post update once completed
There have been a couple of similar reports recently about the previews plugin being an old version, and updating that to its new repo fixes things:
2 Likes
I believe this fixed it! Thank you, I should prob check more often on the plugins I have that are no longer compatible with discourse newer versions.
I appreciate your help immensely!
1 Like
Topic Previews move to a Theme Component was initially experimental. When that experimentation ended and the theme component version matured the complimentary plugin branch was merged to the master branch and the plugin renamed to make its new purpose more obvious. The branch move meant that the old branch was no longer maintained. All you need to do is remove the branch option as the name changes are automatically mapped by GitHub. This happened some time ago. See: Topic List Previews Theme Component for up-to-date links. (Oh I see you posted them, thanks @itsbhanusharma )
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.