The discussion revolves around the duration of the Discourse rebuild process. RuxBux initially encountered an error while running ./launcher rebuild app, which was resolved by retrying the command. The rebuild process involves downloading the Discourse base image, which can take time depending on network speed. clay explains that the process may require multiple runs, especially when upgrading. Tom_Newsom estimates the rebuild takes 10–15 minutes, while codinghorror notes it can range from 3 to 8 minutes based on server performance. RuxBux confirms the rebuild completed in about 10 minutes and expresses gratitude for the support, highlighting the community’s helpfulness.
all i did was add a line to app.yml to add plugin, and after that i went with rebuild… i got this error!
help guys !!!
discourse@ubuntu:/var/discourse$ ./launcher rebuild app
WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed
Please be patient
Unable to find image 'discourse/discourse:1.3.5' locally
That’s a routine warning. You should try ./launcher rebuild app after changing app.yml. You may also need to run it twice, if it needs to pull down the base image again.
discourse@ubuntu:/var/discourse$ ./launcher rebuild app
WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed
Please be patient
Unable to find image 'discourse/discourse:1.3.5' locally
1.3.5: Pulling from discourse/discourse
6d28225f8d96: Pulling fs layer
980fbaeadfb6: Pulling fs layer
6b76e99b0a75: Pulling fs layer
a3ed95caeb02: Pulling fs layer
a3ed95caeb02: Waiting
… i hope it will finish it
EDIT:
now it stands here, should i just wait?
discourse@ubuntu:/var/discourse$ ./launcher rebuild app
WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed
Please be patient
Unable to find image 'discourse/discourse:1.3.5' locally
1.3.5: Pulling from discourse/discourse
6d28225f8d96: Pulling fs layer
980fbaeadfb6: Pulling fs layer
6b76e99b0a75: Pulling fs layer
a3ed95caeb02: Pulling fs layer
a3ed95caeb02: Waiting
6d28225f8d96: Verifying Checksum
6d28225f8d96: Download complete
a3ed95caeb02: Verifying Checksum
a3ed95caeb02: Download complete
6d28225f8d96: Pull complete
a3ed95caeb02: Verifying Checksum
a3ed95caeb02: Download complete
6d28225f8d96: Pull complete
6b76e99b0a75: Verifying Checksum
6b76e99b0a75: Download complete
980fbaeadfb6: Verifying Checksum
980fbaeadfb6: Download complete
980fbaeadfb6: Pull complete
a3ed95caeb02: Verifying Checksum
a3ed95caeb02: Download complete
6d28225f8d96: Pull complete
6b76e99b0a75: Verifying Checksum
6b76e99b0a75: Download complete
980fbaeadfb6: Verifying Checksum
980fbaeadfb6: Download complete
980fbaeadfb6: Pull complete
For me – for whatever reason – if I actually want to upgrade Discourse, I have to run that command again after it pulls down the new base image. You may need to do the same.
yea i had to do it again, but as i saw, and im afraid i just destroyed my discourse… it added new port or something like that, i hardly could see it on cmd
still not done, but i wish i didnt destroyed my forum it had much in it
i think its almost done…
2016-06-22 14:26:21 UTC [43-2] LOG: received fast shutdown request
2016-06-22 14:26:21 UTC [43-3] LOG: aborting any active transactions
2016-06-22 14:26:21 UTC [50-2] LOG: autovacuum launcher shutting down
I, [2016-06-22T14:26:21.409261 #14] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 156
2016-06-22 14:26:21 UTC [47-1] LOG: shutting down
156:signal-handler (1466605581) Received SIGTERM scheduling shutdown...
156:M 22 Jun 14:26:21.423 # User requested shutdown...
156:M 22 Jun 14:26:21.423 * Saving the final RDB snapshot before exiting.
156:M 22 Jun 14:26:21.508 * DB saved on disk
156:M 22 Jun 14:26:21.508 # Redis is now ready to exit, bye bye...
2016-06-22 14:26:21 UTC [47-2] LOG: database system is shut down
edit2: ALL DONE and its working :))) man im glad its done