Hey All I’ve run through the installation process multiple times now. Unfortunately, each time the entire process comes to a complete halt at cd /var/www/discourse && chown -R discourse /var/www/discourse I’ve tried to create the folder myself, since it didn’t even exist, but it doesn’t seem to have any impact. I’ve rebooted multiple times as well. I’m at a loss here.

What installation instructions are you following? It doesn’t look like discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub. Are you installing a development environment?

That’s exactly the guide that I’ve been following. I practically copy and paste all the commands into my terminal. It’s when I get the ./discourse-setup running… I get past putting all the information in… and then it goes through all the lines of configuring and installing everything. Unfortunately, it installs some bundler-1.16.0, after doing a bunch of nginx stuff, and then gets stuck at the cd /var/www/discourse && chown -R discourse /var/www/discourse I was wondering why it got stuck… so I went to look for the folder myself to see if I could manually grant it the proper ownership/permissions… but the folder doesn’t even exist. Everything is being run as sudo. I’m on Ubuntu 17.1.

Oh dear! I am such a sillyhead. Apparently, on my machine at least, it takes over 10 minutes to get past that step. It seems to be flowing right through the rest of the setup now! So sorry, and thank you!

Yup, it cam take up to 30min for a fresh install and 20min for a rebuild. You probably should scale up to a high cpu vm for the install then scale back down afterwards.

A chown run is going to be disk-bound, not CPU-bound. I’m wondering what sort of archaic storage system you’ve got that it takes 10 minutes to chown the app tree.

Probably :sadpanda: I had been running the server off an SSD until recently. That ended up completely dying on me (it was a fairly old SSD, so I was kind of expecting it to happen eventually). The server’s currently running on some old laptop HDD that I had laying around. Thanks for the reply! Glad to know that the process will speed up once I can get my hands on another SSD for the server!

I realize that chown doesn’t always run slow. It is only when there has been a previous, unsuccessful attempt at rebuild. If it is a fresh rebuild, then chown seems to complete very quickly. If there has been a previous failed rebuild (e.g. a typo in app.yml), then it takes forever to chown. Perhaps the old files are still there?

Well, I have done it several times since then. All clean ./launcher rebuild app without prior failures. Run on multiple VM’s with the same sizes, RAM and CPU’s. Sometimes the chown complete within seconds. Sometimes the chown takes forever. And the larger installations may be the fast ones. I’ll experiment some more… BTW… it may have something to do with running ./launcher cleanup prior. It seems that chown runs very fast after a cleanup, but need more evidences. EDIT: My VM’s all have 2 CPU’s, 3GB RAM and HDD (not SSD). So this may magnify the impacts of chown a bit.

Stuck @ CHOWN for /var/www/discourse

Product Support Self-hosting

codinghorror (Jeff Atwood) 25 Novembro , 2017 06:53 9

Maybe you can time it, and test this hypothesis and get us some data?

Tópico		Respostas	Vistas
Rebuilds taking a long time with a large number of uploads (chown performance) Self-hosting	6	307	27 Agosto , 2026
Make rebuild with many uploads more efficient? Product Support	3	616	13 Março , 2020
Discourse build is broken due to removed file? Development	11	2135	16 Outubro , 2017
Bootstrap fails on CentOS 7 Self-hosting	25	7795	5 Novembro , 2017
Welcome to nginx! page before rebuild, site won't rebuild now Product Support	20	824	13 Junho , 2025

Stuck @ CHOWN for /var/www/discourse

Related topics