Trouble upgrading from 3.3.0.beta1 to 3.3.0.beta6

installation
1

Hi all - we’re having trouble upgrading our Discourse Forum from 3.3.0.beta1 to 3.3.0.beta6.

We followed the instructions in the admin panel:

    cd /var/discourse
    git pull
    ./launcher rebuild app

We also upgraded other packages that needed so. Things seemed to have been successful, but it’s still showing us 3.3.0.beta1 in our admin panel.

We have stopped and refreshed the docker container as well.

Also to note, we are running on Amazon Linux 2, not Ubuntu.

My initial thoughts are possibly around the git pull command? Perhaps we’re not grabbing the correct branch?

Any help or additional insight would be greatly appreciated, as we’d love to upgrade so that we no longer have the “A critical update is available” message.

Thank you.

2

What happens if you view source? Do you get the right version then?

3

You shouldn’t need to do a git pull, the rebuild usually does that itself doesn’t it?

1 Like
4

You don’t usually need the git pull, but what it does is make sure the launcher script is up to date. So it’s a good idea.

5

./launcher rebuild app does it everytime, first before anything else, doesn`t it?

6

In that case you’d be running the existing launcher script. Once or twice, this has made a difference. It’s not a script which changes often, I think.

1 Like
7

I’m running into a similar problem going from 3.2.0.beta1-dev to 3.3.0.beta6. It’s telling me there’s a new version, but when I click upgrade the console doesn’t show anything happening.

image
image877×391 9.63 KB

If I ssh into the box and perform a git pull it says Already up to date.

8

AFAIK pure git pull doesn`t do anything for that. It is for launcher.

1 Like
9

ok, well I’ve also performed a ./launcher rebuild app and still see the admin telling me that there’s a new version.

10

Yeah, but that is different thing than git pull.

Could it come from this somehow?

1 Like
11

I’m still on 3.2.0.beta1-dev though. Why am I not able to upgrade to 3.3.0?

12

Can you share your site url? If you view source on your site, what version do you see there?

13

hmm, maybe it’s due to this lets encrypt issue? I think I saw this on another app I’ve worked on that uses Ubuntu.

image
image1183×77 4.14 KB

14

<meta name="generator" content="Discourse 3.2.0.beta1-dev - https://github.com/discourse/discourse version 7ca5ee6cd2bcde191a192d9c3aa8bb6a6c3a4166">

15

It could be, but I doubt it. Unless. . .

You see no errors when you rebuild and it starts the new container? Or do you do a ./launcher start app after it fails (and you didn’t notice that it failed)?

What does

docker ps

show? When was the current container created and started?

16

Opening all ports during cmd line rebuild allowed the letsencrypt process to run.

If I view source it shows 3.2.0.beta1-dev

If I look at the Upgrade page it still shows that I’m not on the latest version.

image
image1118×219 6.83 KB

Should ./launcher rebuild app pull the latest version?

17

You have to keep ports 80 and 443 open.

Yes.

1 Like
18

image
image1352×49 3.75 KB

1 Like
19

Unless you changed the version: tests-passed to something else. I’m stumped.

20

I haven’t changed anything. I don’t know enough about how Discourse is built to do anything other than the default install steps. :slight_smile:

Not sure if this is what you’re talking about in the logs. I do see it showing new tag up till v3.3.0.beta6

image
image1172×412 11.9 KB