Release v1.2: duplicate location "/backups/"

Contribute Bug

AI-generated summary

A user, cfstras, reported an issue after updating to v1.2, where their instance wouldn’t start due to a duplicate location “/backups/” in the discourse.conf file. The issue was caused by a commit being merged twice.

A temporary fix was suggested, which involved switching to the “latest-release” branch. However, this introduced another error related to site customization. sam updated the stable branch with a fix and suggested running a migration to resolve the site customization issue.

cfstras shared a workaround, which involved manually running a migration, rebuilding the standalone app, and restarting the instance. However, sam noted that a simpler solution would have been to run ./launcher rebuild app.

1

Continuing the discussion from Discourse 1.2 released:

After updating (which also told me to update my docker container, since I was on 1.0 until now), my instance won’t come back up.
./launcher logs tells me:
nginx: [emerg] duplicate location "/backups/" in /etc/nginx/conf.d/discourse.conf:79 <message repeats ad infinitum>

Unfortunately, a commit seems to have sneaked in twice while merging:

nginx doesn’t like that. Is there any way to get that fixed on the stable branch?
Thanks in advance!

1개의 좋아요
2

Hmm @sam can you take a peek at this?

3

Looks like when we merged stuff into stable stuff got a bit weird, going to clean it up now

4

As a temporary fix, i switched to “latest-release”, but now I’m getting

undefined method `override_default_style' for #<SiteCustomization:0x007f428a47f788>`

when hitting /login. Is that part of the same problem or a different one?

5

I updated stable with a fix just now.

re site customization stuff sounds like a migration has not run yet.

1개의 좋아요
6

I fixed it, thanks.

For anyone having similar problems and really want to use my solution:

./launcher ssh nt
cd /var/www/discourse
rake db:migrate
# check website and panic because it's still 500ing
^D
mv shared/standalone shared/standalone_old
mkdir shared/standalone
./launcher rebuild standalone
# wait...
# check and see: it's working again, but with an empty db, as expected
./launcher stop standalone
mv shared/standalone_old shared/standalone
./launcher start standalone
# heyaa, it's back!
7

This sounds really odd to me, a ./launcher rebuild app should have done the trick.

8

Next time, i’ll know :slight_smile: