Upgrade stalled, followed advice on forum, now forum not accessible

(Susan Spencer) #1

Hi, I love Discourse, it’s the best forum ever.
Unfortunately, I tried to upgrade Discourse, and during Docker upgrade kept showing ‘Kill’ during upgrade when removing temp files, similar to this post: Forum upgrade crashing at Upgrade `docker_manager`
So, I logged in at DigitalOcean & opened a console then upgraded Discourse from command line as per this post:
Upgrade “currently upgrading” forever
In console I issued:
shutdown -r now
then after system came up again:
cd /var/discourse
git pull
./launcher rebuild app
Then I added a swap file as per this post: Create a swapfile for your Linux server
Create swap file commands were:
sudo install -o root -g root -m 0600 /dev/null /swapfile
dd if=/dev/zero of=/swapfile bs=1k count=2048k
mkswap /swapfile
swapon /swapfile
echo “/swapfile swap swap auto 0 0” | sudo tee -a /etc/fstab
sudo sysctl -w vm.swappiness=10
echo vm.swappiness = 10 | sudo tee -a /etc/sysctl.conf
And I rebooted again with
shutdown -r now

Now I have no forum :frowning:, I get the Apache Ubuntu default page:

Does anyone have suggestions as to what I should do next?

(Matt Palmer) #2

Discourse doesn’t use Apache, so you’re doing something that is above and beyond the basic configuration that we recommend. Please describe exactly what your setup is, along with relevant config files and debug logs, and someone may be able to spot what’s going wrong.

(Susan Spencer) #3

I re-ran the ./launcher command
./launcher rebuild app
It ended with **bind: address already in use"
I rebooted the system with
shutdown -r now
System came up, but still I get the Apache screen instead of the forum.

(Susan Spencer) #4

sudo nginx -t returns
sudo: nginx: command not found
My nginx is missing…How???

I will gladly pay for someone to login to my DigitalOcean droplet and tell me if my data is still there, and how to install/config nginx.


(Susan Spencer) #5

@mpalmer, I will be glad to give you the data you need.
What are the commands to get this data for you? Which files do you need?

(Susan Spencer) #6

Thanks for the info about Apache.
I think that nagios & apache were installed during previous debugging attempts.
I removed apache2, then issued
./launcher rebuild app
Didn’t reboot, and accessed the forum.
It works, thanks very much.

(James North) #7

Just out of interest, Susan, this is because you have not installed nginx on your physical server … and you don’t need it.

Discrouse runs within Docker (virtual machine) and an nginx server is included in that setup and it attempts to bind to the physical server’s web port 80. Of course, this will fail if another web service (in this case Apache) has already grabbed port 80 during system boot up.

It took me a while to get my head around this whole Docker and what is real and not real world, but someone gave me this graphic that really helped.

Removing Apache was the best option. :+1:


service apache stop
sudo apt-get remove apache*

cd /var/discourse
sudo ./launcher restart app

Maybe this will help.

(Susan Spencer) #9

Yeah removing apache fixed the problem.
Thanks for the responses, everyone.