Hi all I keep up on updates pretty well, seen one was due and did it, the result was no UI except in admin SSH in and did server updates to be sure all were good, no help Tried to roll back and got this [image] Entered Safe Mode and got booted, but got a partial UI [image] Can’t log in, says my username is available and that my email does not exist I could use some help please and thank you edit, rebooted server and got [image] not swayed I went to register, figured a back up was due now [image] no joy there either edit, refreshing a different window I seemed to be able to register [image] then [image] still no joy SSH and things still appear as they were [image] edit [image] [image] [image] [image] DISCOURSE DOCTOR Sun Nov 12 01:54:06 UTC 2023 OS: Linux ip-10-0-159-37 6.2.0-1015-aws #15~22.04.1-Ubuntu SMP Fri Oct 6 21:37:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Found containers/app.yml ==================== YML SETTINGS ==================== DISCOURSE_HOSTNAME=forum.full30.com SMTP_ADDRESS=smtp.sendgrid.net DEVELOPER_EMAILS=REDACTED SMTP_PASSWORD=REDACTED SMTP_PORT=587 SMTP_USER_NAME=apikey LETSENCRYPT_ACCOUNT_EMAIL=REDACTED LETSENCRYPT_ACCOUNT_EMAIL ==================== DOCKER INFO ==================== DOCKER VERSION: Docker version 24.0.7, build afdd53b DOCKER PROCESSES (docker ps -a) CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 0be0150fecde local_discourse/app "/sbin/boot" 5 months ago Exited (5) 11 minutes ago app ==================== SERIOUS PROBLEM!!!! ==================== app not running! Attempting to rebuild ==================== REBUILD LOG ==================== x86_64 arch detected. Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 600 app app 2.0.20231023-1945: Pulling from discourse/base Digest: sha256:2b0eb484d20888cc2daadb690dcfa73522105650c1420212e99345a36a424d77 Status: Image is up to date for discourse/base:2.0.20231023-1945 docker.io/discourse/base:2.0.20231023-1945 /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups.rb /usr/local/bin/pups --stdin I, [2023-11-12T01:54:13.829288 #1] INFO -- : Reading from stdin I, [2023-11-12T01:54:13.834181 #1] INFO -- : > locale-gen $LANG && update-locale I, [2023-11-12T01:54:13.862453 #1] INFO -- : Generating locales (this might take a while)... Generation complete. I, [2023-11-12T01:54:13.862638 #1] INFO -- : > mkdir -p /shared/postgres_run I, [2023-11-12T01:54:13.865023 #1] INFO -- : I, [2023-11-12T01:54:13.865390 #1] INFO -- : > chown postgres:postgres /shared/postgres_run I, [2023-11-12T01:54:13.867489 #1] INFO -- : I, [2023-11-12T01:54:13.867791 #1] INFO -- : > chmod 775 /shared/postgres_run I, [2023-11-12T01:54:13.869643 #1] INFO -- : I, [2023-11-12T01:54:13.869925 #1] INFO -- : > rm -fr /var/run/postgresql I, [2023-11-12T01:54:13.871930 #1] INFO -- : I, [2023-11-12T01:54:13.872203 #1] INFO -- : > ln -s /shared/postgres_run /var/run/postgresql I, [2023-11-12T01:54:13.874058 #1] INFO -- : /tmp/discourse-debug.txt

A few things if someone else gets stuck this way. First, don’t run a ./launcher cleanup, instead run a ./launcher start app to restart your existing container. Then you’d be able to do something like ./launcher enter app su - postgres psql discourse drop table ... Without the container to enter and talk direclty to postgres, you have to do it during the container build by adding something like this to your app.yml: hooks: after_postgres: - exec: /bin/bash -c 'sudo -u postgres psql discourse <<< "drop table summary_sections;"' - exec: /bin/bash -c 'sudo -u postgres psql discourse <<< "drop table theme_settings_migrations;"' I don’t know how it was that those two tables got created such that the migrations were out of whack, but this was a fix. And it was stranger than that, because the database had somehow been wiped and once I fixed this it was a brand new database, so it must have somehow been stopped in the middle of a migration at some point.

[image] Robert: I see Nov 5th as most recent, With that being your most recent backup, and me not being an expert in this kind of thing, I’m not sure I should be giving advice here. As far as I can tell, the issue with Warning: Could not create server TCP listening socket *:6379 is probably unrelated to the errors you are getting for the migrations. For example: INFO -- cd /var/www/discourse and su discourse -c 'bundle exec rake db:migrate' ERROR: database "discourse" already exists Error: role "discourse" already exists Error: relation "summary_sections" already exists Those errors seem to suggest that your database is somehow corrupted. The bundle exec rake db:migrate command (that’s in the INFO section of the snippet of your logs that I posted above) should trigger Discourse to check the database’s schema_migrations table to see what migrations have been previously run. That prevents the same migration from being run multiple times. So my guess is that either your database’s schema_migrations table is corrupt, or that duplicate entries have somehow made there way into the db/migrations folder, or files in the db/migrations folder have somehow been renamed. I’m not sure what could trigger any of these things to happen. I’d be tempted to enter the app with ./launcher enter app and run the migration manually from there to see if that makes any difference. Hold off on doing that though. Hopefully someone with more knowledge of the launcher scripts will see this post and correct anything I’ve written that’s wrong.

Curious on your opinion, or anyone’s We’re planning another server move, would this be a good time as these problems seem to be centered around PG::DuplicateTable: ERROR: relation "summary_sections" already exists etc already exists items? Might a move help?

[image] Robert: Might a move help? I suspect that would solve the issue. It couldn’t hurt to try creating a new installation and importing your most recent backup file into it.

[image] simon: creating a new installation The site already seems to think it is a new installation, note some of my screencaps That occurred simply when I used safemode , its a pretty substantial crash just from an update, and the more odd if just my instance of discourse affectedly just toppled I’ve done git pulls etc no different I’d say form building new, if I’m wrong please tell me how

tried ./launcher start-cmd app ./launcher cleanup deleted 18mb of images , did a new pull/rebuild/fail/doctor and still no joy all my info is still present when I access my APP so there’s that at least

[image] Firepup Sixfifty: safe to ignore I ignored them but am still unable to get back online, [image] anon65426961: Lot of errors about incorrect/unmet peer dependency. what do you think of those errors?

Could you post a full log from a rebuild?

I had yesterday the same problem. I thought is was a server problem because in previous updates had similar behaviour, and decided to run to solve temporarily /launcher rebuild app Downloaded the latest backup and deploy a new server. Restores the backup was too easy and mysteriously all is aready updated.

[image] Elvis Inche Arzapalo: /launcher rebuild app 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/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132: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. adb2c505fd2f1289f44586496fea24ff31264f73c26eb524baf16602a189f root@ip-10-0-159-37:/var/discourse# [image] Elvis Inche Arzapalo: deploy a new server. meaning do what exactly?

Update = ☠

Product Support Self-hosting

Firepup650 (Firepup Sixfifty) November 13, 2023, 2:05pm 15

I’m 95% sure that the duplicate table errors are actually safe to ignore. (I remember seeing them every upgrade on our forum)

Topic		Replies	Views
Migration failed: relation "user_required_fields_versions" already exists Self-hosting unsupported-install	18	745	September 9, 2024
Latest site upgrade not working Self-hosting	10	2001	February 22, 2022
Unable to rebuild app Self-hosting	12	2193	January 20, 2022
Building bootstrap error Self-hosting	45	2958	November 20, 2022
Urgent, rebuild failed from old version Self-hosting	5	569	May 8, 2023

Update = ☠

Related topics