`
I did then mount the ISO as a loopback and set it up as a repo and then try to run the following but it says it’s not found from the ISO.
`apt install net-tools`
If I try to set the interface manually with network details during the install both versions would crash.
For the record I’m doing this on ESXi 7.0 and am using the following ISOs.
ubuntu-20.04-live-server-amd64.iso
ubuntu-19.10-live-server-amd64.iso
---
### Author:  [@titusc](https://meta.discourse.org/u/titusc)
#### Post date: [August 3, 2020, 3:43am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/10 "2020-08-03T03:43:23Z")
It’d show the Discourse container is running. Each time I do the following.
1. `./launcher start app`
2. Check on browser and see ‘Welcome to Nginx’ page but then not anymore after about half a minute.
3. `docker ps` to confirm the Discourse container is running.
4. `./launcher stop app` and `./launcher start app`
5. Check on browser and see ‘Welcome to Nginx’ page but then not anymore after about half a minute.
6. `docker ps` to confirm the Discourse container is running.
What I also notice is when I run the following commands I can’t see Nginx running but it could be due to it already having been stopped by the time I run it.
./launcher enter app
systemctl status nginx
---
### Author:  [@DBHacker](https://meta.discourse.org/u/DBHacker)
#### Post date: [August 3, 2020, 3:53am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/11 "2020-08-03T03:53:13Z")
@titusc
Have you tried rebuilding the app?
```plaintext
/var/discourse/launcher rebuild app
```
Normally, depending on when your container spins up completely, it can take time (based on your system specs) to be fully operational.
Even on our 64GB Linux box with 8 CPU cores, we wait around one solid minute before switching over to the new container.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [August 3, 2020, 4:20am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/12 "2020-08-03T04:20:02Z")
Did you try 18.04?
Sounds like an environmental issue, we can’t really offer support for hypervisors and Linux distributions here though. One of the reasons DigitalOcean is recommended is the consistency of the operating system being installed on top of. If you want to build a VM from scratch you’re going to need to figure that out beforehand.
Once you have a working OS we can help install the Discourse portion.
---
### Author:  [@titusc](https://meta.discourse.org/u/titusc)
#### Post date: [August 3, 2020, 4:23am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/13 "2020-08-03T04:23:10Z")
Hello @DBHacker yes I did do the following in sequence.
./launcher rebuild app
./launcher start app
This is after I realize the following all it does is up to the rebuild part of the launcher.
`./discourse-setup`
@Stephen yes I need to work out the issues with the Ubuntu install first. To be honest I’m not a big fan of Ubuntu and have been using CentOS / RH for the last 15 years. What I do want to ask though is are you expecting anything specific we have to setup for CentOS / RH?
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [August 3, 2020, 4:24am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/14 "2020-08-03T04:24:13Z")
The discourse-setup script is tested and proven on Ubuntu.
You may have to do some or all of the steps by hand on a different distribution. Take a look at the contents of the file to get an idea of what it’s doing.
---
### Author:  [@neounix](https://meta.discourse.org/u/neounix)
#### Post date: [August 3, 2020, 4:42am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/15 "2020-08-03T04:42:00Z")
> [@titusc](#):
>
> Hello @DBHacker yes I did do the following in sequence.
> ./launcher rebuild app
> ./launcher start app
Hi @titusc
Sorry you are having issues.
FWIW, you do not need to run:
```plaintext
./launcher start app
```
after you run:
```plaintext
./launcher rebuild app
```
because when you rebuild the app with the launcher script (see below), that script restarts the container before it exits.
Here is some relevant part of the code from launcher:
```plaintext
rebuild)
if ["$(git symbolic-ref --short HEAD)" == "master"]; then
echo "Ensuring launcher is up to date"
git remote update
LOCAL=$(git rev-parse HEAD)
REMOTE=$(git rev-parse @{u})
BASE=$(git merge-base HEAD @{u})
if [$LOCAL = $REMOTE]; then
echo "Launcher is up-to-date"
elif [$LOCAL = $BASE]; then
echo "Updating Launcher..."
git pull || (echo 'failed to update' && exit 1)
echo "Launcher updated, restarting..."
exec "$0" "${SAVED_ARGV[@]}"
elif [$REMOTE = $BASE]; then
echo "Your version of Launcher is ahead of origin"
else
echo "Launcher has diverged source, this is only expected in Dev mode"
fi
fi
set_existing_container
if [! -z $existing]
then
echo "Stopping old container"
(
set -x
$docker_path stop -t 60 $config
)
fi
run_bootstrap
if [! -z $existing]
then
echo "Removing old container"
(
set -x
$docker_path rm $config
)
fi
run_start
exit 0
;;
```
You can see from the script that the rebuild method attempts to start the container before it exits.
HTH
---
### Author:  [@titusc](https://meta.discourse.org/u/titusc)
#### Post date: [August 3, 2020, 6:25am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/16 "2020-08-03T06:25:11Z")
@neounix you are right. Will test again and check on this. Hopefully this was the cause. Not sure of what’s the behavior if it starts the container and I start it again by running `./launcher start app`
---
### Author:  [@neounix](https://meta.discourse.org/u/neounix)
#### Post date: [August 3, 2020, 7:01am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/17 "2020-08-03T07:01:54Z")
Dear @titusc
Sorry not to reply in more detail, but I have to run off on a long road trip.
Many people who make errors with building, rebuilding docker images and containers tend to get into trouble.
You might consider cleaning up (pruning) your “accumulated” docker images and unused containers at some point.
For example (off the top of my head quickly)
```plaintext
docker ps -a
```
```plaintext
docker images
```
```plaintext
docker system prune -a
```
You shoud stop all “rouge” containers, and remove them and delete all the old Docker images.
Gotta run…
HTH
---
### Author:  [@titusc](https://meta.discourse.org/u/titusc)
#### Post date: [August 3, 2020, 7:39am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/18 "2020-08-03T07:39:39Z")
@neounix agreed with checking the docker images. I actually have done that but let me show you this in detail. As you can see below Discourse was successfully built and started to run in a docker container. Towards the end you can see Nginx was running in container but quitted after only 5 seconds or so.
**Before Everything Starts**
```
[root@uat discourse]# pwd
/var/discourse
[root@uat discourse]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
[root@uat discourse]# docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
[root@uat discourse]# docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
discourse/base 2.0.20200724-1815 6ba1506bf822 9 days ago 2.38GB
centos latest 831691599b88 6 weeks ago 215MB
alpine latest a24bb4013296 2 months ago 5.57MB
```
**Confirm No HTTP Server Is Running On Host**
```
[root@uat discourse]# systemctl status nginx
Unit nginx.service could not be found.
[root@uat discourse]# lsof -i TCP
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 181u IPv4 19283 0t0 TCP *:sunrpc (LISTEN)
systemd 1 root 183u IPv6 19285 0t0 TCP *:sunrpc (LISTEN)
rpcbind 1070 rpc 4u IPv4 19283 0t0 TCP *:sunrpc (LISTEN)
rpcbind 1070 rpc 6u IPv6 19285 0t0 TCP *:sunrpc (LISTEN)
sshd 1234 root 5u IPv4 26444 0t0 TCP *:ssh (LISTEN)
sshd 1234 root 7u IPv6 26446 0t0 TCP *:ssh (LISTEN)
cupsd 1240 root 9u IPv6 27746 0t0 TCP localhost:ipp (LISTEN)
cupsd 1240 root 10u IPv4 27747 0t0 TCP localhost:ipp (LISTEN)
dnsmasq 2094 dnsmasq 6u IPv4 37419 0t0 TCP uat:domain (LISTEN)
sshd 7102 root 5u IPv4 2072827 0t0 TCP uat:ssh->10.1.136.4:52229 (ESTABLISHED)
sshd 7156 tech 5u IPv4 2072827 0t0 TCP uat:ssh->10.1.136.4:52229 (ESTABLISHED)
```
**Rebuild Discourse**
```
[root@uat discourse]# ./launcher rebuild app
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
cd /pups && git pull && /pups/bin/pups --stdin
Already up to date.
......................................................................
I, [2020-08-03T06:54:22.114365 #1] INFO -- : > echo "Beginning of custom commands"
I, [2020-08-03T06:54:22.116739 #1] INFO -- : Beginning of custom commands
I, [2020-08-03T06:54:22.116996 #1] INFO -- : > echo "End of custom commands"
I, [2020-08-03T06:54:22.119862 #1] INFO -- : End of custom commands
I, [2020-08-03T06:54:22.119983 #1] INFO -- : Terminating async processes
I, [2020-08-03T06:54:22.120021 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/12/bin/postmaster -D /etc/postgresql/12/main pid: 49
I, [2020-08-03T06:54:22.120086 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 166
166:signal-handler (1596437662) Received SIGTERM scheduling shutdown...
2020-08-03 06:54:22.120 UTC [49] LOG: received fast shutdown request
2020-08-03 06:54:22.121 UTC [49] LOG: aborting any active transactions
2020-08-03 06:54:22.128 UTC [49] LOG: background worker "logical replication launcher" (PID 58) exited with exit code 1
2020-08-03 06:54:22.128 UTC [53] LOG: shutting down
2020-08-03 06:54:22.154 UTC [49] LOG: database system is shut down
166:M 03 Aug 2020 06:54:22.176 # User requested shutdown...
166:M 03 Aug 2020 06:54:22.176 * Saving the final RDB snapshot before exiting.
166:M 03 Aug 2020 06:54:22.184 * DB saved on disk
166:M 03 Aug 2020 06:54:22.184 # Redis is now ready to exit, bye bye...
sha256:7b8e9281c49ba3dc37e0743a765cddc13ab73aae5486bd30722c696c2e1443b1
ce327c6e37246e63331f03b07d64f4882efa68e88cb1516c6343a9dddbbd59df
+ /usr/bin/docker run --shm-size=512m -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=4 -e UNICORN_SIDEKIQS=1 -e RUBY_GLOBAL_METHOD_CACHE_SIZE=131072 -e RUBY_GC_HEAP_GROWTH_MAX_SLOTS=40000 -e RUBY_GC_HEAP_INIT_SLOTS=400000 -e RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=1.5 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e LETSENCRYPT_DIR=/shared/letsencrypt -e DISCOURSE_HOSTNAME=uat.xxxxxx.com -e DISCOURSE_DEVELOPER_EMAILS=support@xxxxxx.com -e DISCOURSE_SMTP_ADDRESS=smtp-relay.xxxxxx.com -e DISCOURSE_SMTP_PORT=587 -e DISCOURSE_SMTP_USER_NAME=support@xxxxxx.com -e DISCOURSE_SMTP_PASSWORD=support@xxxxxx.com -e LETSENCRYPT_ACCOUNT_EMAIL=me@example.com -h uat-app -e DOCKER_HOST_IP=172.17.0.1 --name app -t -p 80:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:fe:39:ba:65:e1 local_discourse/app /sbin/boot
44c604ccbda4bfb4d48722e1cbbf70e3b067531acda41175f6bdaaa013cc6d18
```
**Confirm Image Is Built And Docker Is Running**
```
[root@uat discourse]# docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
44c604ccbda4 local_discourse/app "/sbin/boot" 7 minutes ago Up 7 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app
[root@uat discourse]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
44c604ccbda4 local_discourse/app "/sbin/boot" 7 minutes ago Up 7 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app
[root@uat discourse]# docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
local_discourse/app latest 7b8e9281c49b 8 minutes ago 2.66GB
discourse/base 2.0.20200724-1815 6ba1506bf822 9 days ago 2.38GB
centos latest 831691599b88 6 weeks ago 215MB
alpine latest a24bb4013296 2 months ago 5.57MB
```
**Confirm Nothing Is Still Running On Host And Docker Is Listening On Ports 80 and 443**
```
[root@uat discourse]# systemctl status nginx
Unit nginx.service could not be found.
[root@uat discourse]#
[root@uat discourse]# lsof -i TCP
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 181u IPv4 19283 0t0 TCP *:sunrpc (LISTEN)
systemd 1 root 183u IPv6 19285 0t0 TCP *:sunrpc (LISTEN)
rpcbind 1070 rpc 4u IPv4 19283 0t0 TCP *:sunrpc (LISTEN)
rpcbind 1070 rpc 6u IPv6 19285 0t0 TCP *:sunrpc (LISTEN)
sshd 1234 root 5u IPv4 26444 0t0 TCP *:ssh (LISTEN)
sshd 1234 root 7u IPv6 26446 0t0 TCP *:ssh (LISTEN)
cupsd 1240 root 9u IPv6 27746 0t0 TCP localhost:ipp (LISTEN)
cupsd 1240 root 10u IPv4 27747 0t0 TCP localhost:ipp (LISTEN)
dnsmasq 2094 dnsmasq 6u IPv4 37419 0t0 TCP uat:domain (LISTEN)
sshd 7102 root 5u IPv4 2072827 0t0 TCP uat:ssh->10.1.136.4:52229 (ESTABLISHED)
sshd 7156 tech 5u IPv4 2072827 0t0 TCP uat:ssh->10.1.136.4:52229 (ESTABLISHED)
docker-pr 12991 root 4u IPv6 2242261 0t0 TCP *:https (LISTEN)
docker-pr 13003 root 4u IPv6 2242288 0t0 TCP *:http (LISTEN)
```
**Restart Docker And Check Nginx After Nginx Has Stopped**
```
[root@uat discourse]# ./launcher stop app
+ /usr/bin/docker stop -t 10 app
app
[root@uat discourse]# ./launcher start app; ./launcher enter app
starting up existing container
+ /usr/bin/docker start app
app
root@uat-app:/var/www/discourse# date; ps -ef | grep nginx
Mon 03 Aug 2020 07:29:47 AM UTC
root 34 1 0 07:29 ? 00:00:00 nginx: master process /usr/sbin/nginx -c /etc/nginx/letsencrypt.conf
www-data 36 34 0 07:29 ? 00:00:00 nginx: worker process
www-data 37 34 0 07:29 ? 00:00:00 nginx: worker process
root 1091 398 0 07:29 pts/1 00:00:00 grep nginx
root@uat-app:/var/www/discourse# date; ps -ef | grep nginx
Mon 03 Aug 2020 07:29:50 AM UTC
root 34 1 0 07:29 ? 00:00:00 nginx: master process /usr/sbin/nginx -c /etc/nginx/letsencrypt.conf
www-data 36 34 0 07:29 ? 00:00:00 nginx: worker process
www-data 37 34 0 07:29 ? 00:00:00 nginx: worker process
root 1854 398 0 07:29 pts/1 00:00:00 grep nginx
root@uat-app:/var/www/discourse# date; ps -ef | grep nginx
Mon 03 Aug 2020 07:29:52 AM UTC
root 2043 2038 0 07:29 ? 00:00:00 runsv nginx
root 2080 398 0 07:29 pts/1 00:00:00 grep nginx
root@uat-app:/var/www/discourse#
```
---
### Author:  [@neounix](https://meta.discourse.org/u/neounix)
#### Post date: [August 3, 2020, 9:59am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/19 "2020-08-03T09:59:36Z")
Hi @titusc
Thanks for the great post and comprehensive troubleshooting info. Very well done.
Did you check the `nginx` log files in the app for clues?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 3, 2020, 11:00am UTC](https://meta.discourse.org/t/discourse-not-serving-pages/159578/20 "2020-08-03T11:00:41Z")
Something is broken in your setup. My guess is that whatever is broken that keeps ubuntu from installing is also interfering with Centos.
You need to fix that before you install discourse (or likely, anything else).
[Next page](https://meta.discourse.org/t/discourse-not-serving-pages/159578.md?page=2)